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.
Description of problem:
cloud-init configures IPv6 related parameters incorrectly.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Configure IPv6 address, subnet prefix, gateway with cloud-init ( I was using oVirt VM for this)
2. Start instance
Actual results: IPv6 related parameters are configured like IPv4 in the ifcfg scripts. E.g. IPADDR instead of IPv6ADDR
Expected results: IPv6 parameters are configured in a correct way
Additional info:
cloud-init: cloud-init-0.7.2-3.el7.noarch
Screenshots, meta_data.json and logs are available here: https://drive.google.com/drive/folders/0B6guVkGtE_8RNGk3NlNhX0VSR2M?usp=sharing
(In reply to Vladimir from comment #6)
> I cannot check with latest cloud_init version since whole network
> configuration is broken in the 4.2 RHEV at the moment
This is an unhelpful statement. Could you please explain what is broken? Please sync with myakove and mburman (network qe), who have not reported total breakage.