Open filipeferreira89 opened 6 months ago
Thanks for opening this issue @filipeferreira89. We recently became aware of this and have a fix for redhat 7.* in our new release that we are just starting. We'll continue addressing in other fedora distros in subsequent releases. We will prioritize endorsed distros, so alma 8 may take us longer.
Could you please share the exact version of alma 8 you're seeing this on?
Hi @maddieford, We are seeing it on AlmaLinux 8.7 and 8.9, but I believe that the bug is there for any previous "minors". When the release is done for redhat 7, we can test it out to see if it works also on AlmaLinux 8. Since you talked about rhel 7, I believe we were having the same issue (with less occurrences) on CentOS 7, but we never did a proper investigation like this one.
@filipeferreira89 The fix in the next release includes CentOS 7. Could you please also share the full waagent.log? Or at least 10 minutes of logs after this failure:
2024-02-07T18:00:42.974630Z ERROR ExtHandler ExtHandler Error fetching the goal state: [ProtocolError] [Wireserver Exception] [HttpError] [HTTP Failed] GET http://168.63.129.16/machine/ -- IOError [Errno 101] Network is unreachable -- 6 attempts made
waagent.log This might not be by the same vm as the other logs, but the issue is the same and they both were configured through the same process and commands
Thanks. Also, what regions are you in for CentOS 7? As we progress our release with the fix for fedora 7.* versions, are you able to confirm you're no longer seeing the issue? I can update here when we've promoted the release to the regions you're in.
We use West Europe, North Europe and China East 2. Yes, as soon you have a new version I can test to see if I can replicate the issue.
@filipeferreira89 We just published 2.10.0.8 with the fix for centos 7 hostname publishing to North Europe. Would you be able to validate you're no longer seeing this issue there for CentOs 7? Thank you
Describe the bug: A clear and concise description of what the bug is.
Even though RHEL 8 and AlmaLinux are almost identical twins, there is no official support yet for AlmaLinux 8, whoever it's already supporting AlmaLinux 9.
We identified a bug with the WALinuxAgent 2.9.1.1 version on AlmaLinux 8 VMs. Sometimes, when we trigger a change on the hostname of the virtual machine with the following command
hostnamectl set-hostname testvm000008a
, WALinuxAgent triggers a restart of the NetworkManager Service and the eth0 can enter in a failed state and the vm loses any routes.waagent.log
Note: Please add some context which would help us understand the problem better
Distro and WALinuxAgent details (please complete the following information):