- ci-fix-add-schema-rules-for-baseurl-and-metalink-in-yum.patch [RHEL-46874]
- Resolves: RHEL-46874
(Suggest to update schema to support metalink [rhel-10])
- ci-Support-metalink-in-yum-repository-config-5444.patch [RHEL-44918]
- ci-fix-vmware-Set-IPv6-to-dhcp-when-there-is-no-IPv6-ad.patch [RHEL-35562]
- Resolves: RHEL-44918
([RFE] Support metalink in yum repository config [rhel-10])
- Resolves: RHEL-35562
([RHEL-10] It leaves the ipv6 networking config as blank in NM keyfile when config dhcp ipv6 with customization spec)
- ci-feat-Set-RH-ssh-key-permissions-when-no-ssh_keys-gro.patch [RHEL-36456]
- Resolves: RHEL-36456
([RHEL-10] Group ssh_keys is missing and ssh host key permission is changed in rhel-10)
- ci-Report-full-specific-version-with-cloud-init-version.patch [RHEL-34764]
- Resolves: RHEL-34764
([RHEL-10] cloud-init should report full version with "cloud-init --version" )
- ci-Remove-dependency-on-dhcp-client-ISC-DHCP-and-use-dh.patch [RHEL-26304]
- ci-fix-Fall-back-to-cached-local-ds-if-no-valid-ds-foun.patch [RHEL-32854]
- Resolves: RHEL-26304
([RFE][rhel-10] Suggest to remove dependency on dhcp-client in cloud-init)
- Resolves: RHEL-32854
([cloud-init][ESXi]VMware datasource resets on every boot causing it to lose network configuration [rhel-10.0])
udhcpc does work, but it doesn't exist in ELN right now. Let's revert
back to dhcp-client until the upstream cloud-init support for dhcpcd is
ready.
Signed-off-by: Major Hayden <major@redhat.com>
The dhclient binary from the dhcp-client package is no longer
maintained, but it can be replaced by udhcpc which comes from busybox.
Cloud-init already supports both utilities for the early dhcp request.
Fixes rhbz#2247055
Signed-off-by: Major Hayden <major@redhat.com>
Enabling DHCPv6 by default on EC2 leads to instance with broken IPv6
connectivity. AWS provides the IP address via DHCPv6 and SLAAC, but
router advertisements are not accepted if the instance has DHCPv6
configured. The accept_ra value is set to 0.
Removing the `dhcp` option from `ipv6.method` and simply using `auto`
(the default) allows the instance to pick up its IPv6 address and accept
router advertisements from the AWS network.
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=2092459
Pagure: https://pagure.io/cloud-sig/issue/382
Upstream: https://bugs.launchpad.net/cloud-init/+bug/1976526?comments=all
Signed-off-by: Major Hayden <major@redhat.com>
Canonical switched to GitHub as their "canonical" source for cloud-init
and the forge macros make RPM maintenance a little simpler.
Signed-off-by: Major Hayden <major@redhat.com>
This lays down a file that sets `no-auto-default=*`, which
tells NetworkManager to not bring up any interfaces by default
without explicit configuration. This causes networking to not
be brought up at all if somehow no NM connection file got created.
This is the first step for rebasing cloud-init to 21.3. All patches are
rebased, old patches that are already on the release were deleted.
Signed-off-by: Eduardo Otubo <otubo@redhat.com>
