Upgrade failure and KeyVault: Invalid secret reference found ...

Harshavardhan123-ux commented 3 weeks ago

Does this bug already exist in our backlog?

[X] I have checked and confirm this is a new bug.

Describe the issue

Flow status in the COE Dashboard is not Syncing correctly, as recommended by the Microsoft support team we try to patch the latest patch, but we are ending up with error. Reference ticket number:2408050030008066,2405150030002191

Expected Behavior

First, we expect correct sync of flow status second, we expect successful completion of COE latest Patch

What solution are you experiencing the issue with?

Core

What solution version are you using?

1.70

What app or flow are you having the issue with?

All flows

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

Jenefer-Monroe commented 3 weeks ago

Hello we will need to just deal with your upgrade issue for now. I'm sorry that support pointed you to us. This is definitely an issue with the product's upgrade code and key vault.

I've seen this happen before but have never experienced it myself. I've heard its due to the product not dealing with the env vars correctly.

If you go to the Default Solution > Environment Variables > filter to env vars of type secret Note that Env Vars have both "Current Values" and "Default Values" Yours should always be in the "Current Values" as Default Values are things that are overwritten when you upgrade. Can you please go see, do you have values in either Current or Default?

Jenefer-Monroe commented 3 weeks ago

Also please let me know if you are installing via a tool (Pac CLI / ALM Accelerator / etc) or by hand. I see a few references online to this failure for PAC CLI (although we do succeed with it). So you may also try to do it by hand if needed.

Jenefer-Monroe commented 2 weeks ago

closing out as no further action from starter kit team

Harshavardhan123-ux commented 2 weeks ago

Hello can you please help to setup call with us to check on this?

Jenefer-Monroe commented 2 weeks ago

Hello please note that we do not normally see comments in closed bugs I just happened to see this. Unfortunately we are a very small team, with only 1 person doing GitHub assistance for all 12k installs, and the kit is not a supported product, so we are just not staffed to have calls with our users.

Jenefer-Monroe commented 2 weeks ago

Please take a look at the requests above and we'll see if we can get you unblocked here

Harshavardhan123-ux commented 2 weeks ago

we dont find Audit logs-Client Azure Secret

Jenefer-Monroe commented 2 weeks ago

Thats fine, the product bug referenced can repro for any azure secret. So for you it will be Command Center - Client Azure Secret.

Harshavardhan123-ux commented 1 week ago

Hi , i have checked for me both current and default is blank only .

Jenefer-Monroe commented 1 week ago

Ok I'm afraid I can't help then. This is a product bug with upgrade and key vault, they should not have pointed you to us. I suggest you reach out to them again and if they try to push back again, have then reach out to the CoE PM (Grant Archibald) to converge.

Harshavardhan123-ux commented 5 days ago

can you please guide me how to reach out to CoE Team

Harshavardhan123-ux commented 5 days ago

can you please guide me how to reach out to CoE Team

Harshavardhan123-ux commented 5 days ago

can you please guide me how to reach out to CoE Team

Jenefer-Monroe commented 4 days ago

Sorry you misunderstood my suggestion. The CoE Team is Grant and myself. You will need to reach back out to support that pointed you here and tell them to contact Grant if they still think this is an issue with our solution file as it is not. This is a bug with secret type env vars and the product itself.

So please reach back out to support and give them Grant's name if they have questions: (Grant Archibald)

microsoft / coe-starter-kit