Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1333559[details]
all inputs to cloud-init; ifcfg; cloud-init logs
Description of problem:
when cloud-init is handed a network_data.json containing an ipv6 static configuration:
1. it fails to create the expected ifcfg-XX file
2. the VM which it instantiated is not accessible via ssh: a login attempt with the configured user (which appears in the user_data file handed to cloud-init) returns 'permission denied'
Version-Release number of selected component (if applicable):
cloud-init-0.7.9-9.el7.centos.2.x86_64
centos 7.2.1511 (Core)
How reproducible:
100%
Steps to Reproduce:
1. Create Ovirt setup with engine, and a host
2. Create a VM instance from a CentOS 7.2.1511 template (CentOS 7 Generic Cloud Image v1608 for x86_64 (2162b33))
3. Instantiate the VM with cloud-init and only set user and password
4. verify that the VM starts and is accessible with set creds
5. stop the VM
6. from engine - run the VM once with same creds, and add network on eth0
7. insert IPv4 and IPv6 details for eth0
8. submit to start the VM
9. open the spice console from engine and login with above creds to get the ip of the VM.
10. try to connect to the VM with ssh from a regular terminal --> permission denied
10. check /etc/sysconfig/network-scripts/ifcfg-eth0 --> it is not as expected
Actual results:
1. permission denied on ssh access
2. ipv4 + ipv6 static config is missing. ifcfg-eth0 is:
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=00:1a:4a:16:01:00
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
Expected results:
1. VM accessible via ssh
2. ipv4 + ipv6 static config in ifcfg-eth0
Additional info:
* following configurations to cloud-init work as expected:
1. ipv4 static
2. ipv4 dhcp
3. ipv4 dhcp + ipv6 dhcp
* I set cloud-init services to provide debug info - see logs in attached
I'm providing qa_ack based on communication that took place in an email thread. The subject matter expert team, RHEVM QE in this case, will verify this particular bugzilla.
My team will do verification and regression testing in EC2, and will ask other stakeholders who make use of cloud-init in their projects to do verification on their side, too.
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, 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/RHEA-2018:0806
Created attachment 1333559 [details] all inputs to cloud-init; ifcfg; cloud-init logs Description of problem: when cloud-init is handed a network_data.json containing an ipv6 static configuration: 1. it fails to create the expected ifcfg-XX file 2. the VM which it instantiated is not accessible via ssh: a login attempt with the configured user (which appears in the user_data file handed to cloud-init) returns 'permission denied' Version-Release number of selected component (if applicable): cloud-init-0.7.9-9.el7.centos.2.x86_64 centos 7.2.1511 (Core) How reproducible: 100% Steps to Reproduce: 1. Create Ovirt setup with engine, and a host 2. Create a VM instance from a CentOS 7.2.1511 template (CentOS 7 Generic Cloud Image v1608 for x86_64 (2162b33)) 3. Instantiate the VM with cloud-init and only set user and password 4. verify that the VM starts and is accessible with set creds 5. stop the VM 6. from engine - run the VM once with same creds, and add network on eth0 7. insert IPv4 and IPv6 details for eth0 8. submit to start the VM 9. open the spice console from engine and login with above creds to get the ip of the VM. 10. try to connect to the VM with ssh from a regular terminal --> permission denied 10. check /etc/sysconfig/network-scripts/ifcfg-eth0 --> it is not as expected Actual results: 1. permission denied on ssh access 2. ipv4 + ipv6 static config is missing. ifcfg-eth0 is: # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=dhcp DEVICE=eth0 HWADDR=00:1a:4a:16:01:00 ONBOOT=yes TYPE=Ethernet USERCTL=no Expected results: 1. VM accessible via ssh 2. ipv4 + ipv6 static config in ifcfg-eth0 Additional info: * following configurations to cloud-init work as expected: 1. ipv4 static 2. ipv4 dhcp 3. ipv4 dhcp + ipv6 dhcp * I set cloud-init services to provide debug info - see logs in attached