Draft
Conversation
Podman 5.x on Azure Linux 3 requires crun (OCI runtime), netavark (network stack), and aardvark-dns explicitly installed. Without these, az acr login fails with "could not find netavark" on RP and gateway VMSS. Made-with: Cursor
aardvark-dns is not a separate package in Azure Linux 3 repos. DNS functionality is bundled with netavark on this platform. Made-with: Cursor
On Azure Linux 3, nftables is the default and native firewall backend. Forcing iptables causes firewalld to crash with a DBus NoReply error because the iptables backend is not functional on this platform. Made-with: Cursor
|
Skipping CI for Draft Pull Request. |
Made-with: Cursor
273c839 to
d499bc1
Compare
|
Please rebase pull request. |
1 similar comment
|
Please rebase pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue this PR addresses:
Fixes ARO-22145 — Migrate Azure Red Hat OpenShift RP/Gateway VMSS from Azure Linux 2.0 (EOL July 31, 2025) to Azure Linux 3.0.
What this PR does / why we need it:
Test plan for issue:
Verify RP and Gateway VMSS boot and run successfully on Azure Linux 3 FIPS images
Is there any documentation that needs to be updated for this PR?
How do you know this will function as expected in production?
INT and Canary Testing