+++ This bug was initially created as a clone of Bug #2115565 +++
Description of problem:
With the upgrade to cloud-init 22.1, CentOS/RHEL images have reverted back to "branded" users for the cloud-init user rather than the generic "cloud-user" that was being used before.
This change breaks automation and makes things particularly difficult for consumers to leverage RHEL/CentOS images.
Version-Release number of selected component (if applicable):
22.1-4.el8
How reproducible:
Always
Steps to Reproduce:
1. Boot the latest CentOS Stream cloud image
2. Attempt to log in with the "cloud-user"
3. Attempt to log in with the "centos" user
Actual results:
Login fails with "cloud-user" and succeeds with "centos"
Expected results:
Login succeeds with "cloud-user" and fails with "centos"
Additional info:
Originally, RHEL/CentOS used "cloud-user" with the custom cloud-init configuration files. Too much configuration was removed in the rebase to cloud-init v22.1.
@Eduardo @Emanuele,
In the patch "Align rhel custom files with upstream (#1431)", rhel and centos are treated differently, could you help to check it please? Should they use same configuration?
{% if variant in ["almalinux", "alpine", "amazon", "centos", "cloudlinux", "eurolinux",
"fedora", "miraclelinux", "openEuler", "rhel", "rocky", "virtuozzo"] %}
{% if variant == "rhel" %}
...
Comment 2Emanuele Giuseppe Esposito
2022-08-08 07:52:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (cloud-init bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2777