microsoft
Missing azcmagent-1.56.03167-593.x86_64 from https://packages.microsoft.com/rhel/9.0/prod/Packages
Describe the issue Hello, We do a sync of repo from https://packages.microsoft.com/rhel/9.0/prod/Packages on a weekly basis. Noticed this package azcmagent-1.56.03167-593.x86_64 was available from above repo during the week of 10 Sept and 17 Sept. But from late last/this week, we noticed azcmagent-1.56.03167-593.x86_64 was no longer available in https://packages.microsoft.com/rhel/9.0/prod/Packages
And from https://learn.microsoft.com/en-us/azure/azure-arc/servers/agent-release-notes, azcmagent-1.56.03167-593 should be available for download
Is there a reason of it ?
When did the issue occur? Happening possibly late last week.
If applicable, what package did you attempt to install, and from which repo? azcmagent from https://packages.microsoft.com/rhel/9.0/prod/Packages/a/
Steps to Reproduce
Actual Result
Expected Result
Screenshots
Additional context
Looks like there was an update to the repository on the 27 Sept and the package is now back in the repository in https://packages.microsoft.com/rhel/9/prod/Packages/a/azcmagent-1.56.03167-593.x86_64.rpm
The issue i believe is now resolved.
May i ask the cause of it ? According to the documentation the prod repositories are designated for packages intended to be used in production. Thus if the new package appear on first release for 2 weeks, then disappear for 2 weeks and then reappear, it makes it challenging to roll out updates.
@junmingsg the PMC team maintains the infrastructure for packages.microsoft.com but we don't publish packages to it. The Azure Arc team would have to answer that question. We've forwarded this issue to them but I would recommend also trying to reach out to them yourself. AFAIK, they don't have a public presence so I would suggest contacting customer support.
@daviddavis I am guessing it would be a good idea to establish a policy to never delete a package from the repositories though, if a team messes up they should revert the changes in source and publish a new version. Otherwise people will have to manually downgrade instead of doing a properly automated $packagemanger update
@Klaas- that's exactly what we strongly advise to publishers: never to delete packages. The functionality to delete packages predates me but we've talked about possibly removing or restricting it.
@junmingsg https://learn.microsoft.com/en-us/answers/questions/5558004/arc-service-fail-after-upgrade-to-v1-56 I think that's why they pulled it, not sure why they put it back the same way instead of rolling back the changes and putting out a new version :D