Support for Rocky Linux and/or Alma Linux?
pmdci opened this issue · comments
Due to CentOS changing to Stream, alternatives like Rocky Linux and Alma Linux have been introduced. Any chance we can get the WA Linux Agent to work with Rocky Linux and/or Alma Linux?
@pmdci We already have internal work items to add Rocky Linux and Alma, but presently we are working on another features, so we do not have an ETA. I'll post any updates here.
Just as a general comment, Rocky and AlmaLinux should have the same functionality and bugs as CentOS; I know there's the risk of over-trivilialising the work, and I do see it will need a bit of familiarity when it's a 6000+ line Python script doing the heavy lifting, but there shouldn't be any functional reason for it not to work. So isn't this essentially just a case of handling those as aliases?
Not having this and the general gatekeeping of versions (i.e. inability to use RHEL/CentOS Stream/AlmaLinux 9 currently as far as we can tell) makes it quite difficult to support Azure as a secure platform conforming to security requirements of keeping on updated OS versions. Perhaps it's worth considering a general approach here to just bypass these checks when we can be pretty well assured in most cases for these Fedora/CentOS Stream downstream distribituions that it would work out of the box were it not for these allow-list checks?
I note the recent comments in #2618 so perhaps this is already under consideration but I just wanted to point out that the work should essentially only have to do with these soft checks.
+1 for the AlmaLinux and Rocky Linux support.
Are there any updates on this?
AlmaLinux and Rocky Linux have packages for the agent, but I assume this remains unsupported to date?
We'll get to this work item within a few weeks. In the meanwhile, have you tried to execute any VM extensions on AlmaLinux or Rocky? If you do, please post any errors you may get here, it will help to scope the work that needs to be done.
We had issue mounting disk created by Azure CSI driver to the node. We eventually rebuilt the latest rpm and installed it manually on the node.
However after installing and reloading udevd, it still fail to create symlinks at /dev/disks/azure directory since the base image was already had incorrect link.
It would be great if there is a way to remove existing invalid udev configuration for /dev/disk/azure before reapplying it. This would make it easy to upgrade rpm without manually removing existing links to /dev/disk/azure
@narrieta would you have any idea when WALinuxAgent rpm version 2.9.0.4 will be available from yum repositories (Centos 9 appstream)?
We'll get to this work item within a few weeks. In the meanwhile, have you tried to execute any VM extensions on AlmaLinux or Rocky? If you do, please post any errors you may get here, it will help to scope the work that needs to be done.
Is there an update on this work after 2 months?
Rocky Linux and AlmaLinux are both very popular and important distributions, so the lack of focus here is a bit confusing.
@jameswmcnab @supershal I'm closing this issue since the WaLinuxAgent now supports both Alma and Rocky and they have been added to the test automation (fixed by #2796)
@supershal I'll try to investigate who is responsible for the rpm packages and post here. The WALinuxAgent team does not create those packages,