Updates to azurelinux-release#8028
Conversation
ddstreetmicrosoft
force-pushed
the
ddstreet/azure-release
branch
from
066693e to
01cc4aa
Compare
ddstreetmicrosoft
force-pushed
the
ddstreet/azure-release
branch
4 times, most recently
from
06d2631 to
4c5bbdc
Compare
ddstreetmicrosoft
force-pushed
the
ddstreet/azure-release
branch
2 times, most recently
from
130f06c to
ad8792b
Compare
PawelWMS
left a comment
PawelWMS
left a comment
There was a problem hiding this comment.
I really like these changes. The only reason I haven't approved yet, is that we probably need to wait for #8013 to define the azl macro systemd.spec depends. For now, unfortunately, we can't deliver it from azurelinux-release for that spec. Once that's in and systemd builds, I think we'll be good to go.
ddstreetmicrosoft
force-pushed
the
ddstreet/azure-release
branch
8 times, most recently
from
860efe1 to
0524cc3
Compare
PawelWMS
left a comment
PawelWMS
left a comment
There was a problem hiding this comment.
Changes look good. The full build you linked a while earlier failed due to missing signatures, though. The signatures are definitely here in this version of the PR, so I hope that's not going to fail anymore. I just started another build. Before you merge, please make sure there are no regressions in the toolchain and package builds.
ddstreetmicrosoft
force-pushed
the
ddstreet/azure-release
branch
from
0524cc3 to
0721b5a
Compare
unfortunately that failed due to a mismatch in the nftables signatures, but it did get through the toolchain build. I rebased and added a commit to fix the nftables signatures also. |
|
started a new pipeline full build https://dev.azure.com/mariner-org/mariner/_build/results?buildId=516811&view=results |
The *-release files belong exclusively to this package, and are not config files; so we should not treat them as config(noreplace).
… make %_sysconfdir symlinks
ddstreetmicrosoft
force-pushed
the
ddstreet/azure-release
branch
from
0721b5a to
fad9ba6
Compare
Default presets were introduced in PR #8028. The default firewall was firewalld which is not fully supported for Azl3. Therefore, set as iptables. - For an image upgrade, this PR will cause the iptables.service to run by default and thus, will introduce firewall rules by default. - For a package upgrade to azurelinux-release-3.0-20, the iptables service will be recognized as being allowed by the preset but will NOT be enabled by default. That being said, if an iptables.rpm upgrade comes in afterwards, the rules WILL be turned on - For a package downgrade to an older package (< azurelinux-release-3.0-20), the preset will show that the iptables service is disabled by the preset but iptables WILL continue to run even after reboot
7 participants
Several updates to the azurelinux-release package: