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.
With the RFE bug 1642461 fixed, there is a new pkg named NetworkManager-cloud-setup imported. The RHEL can configure the 2nd ip inside instance automatically now. I am suggesting to add this pkg into ec2 images for taking advantage of this feature.
After installed NetworkManager-cloud-setup, pls enable nm-cloud-setup and nm-cloud-setup.timer services.
Below is an example, there are 2 internal ips under eth0.
[ec2-user]# ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP group default qlen 1000
link/ether 0a:c0:2c:f1:25:04 brd ff:ff:ff:ff:ff:ff
inet 10.116.2.105/24 brd 10.116.2.255 scope global dynamic eth0
valid_lft 3318sec preferred_lft 3318sec
inet 10.116.2.236/24 brd 10.116.2.255 scope global secondary eth0
valid_lft forever preferred_lft forever
inet6 fe80::8c0:2cff:fef1:2504/64 scope link
valid_lft forever preferred_lft foreve
Version-Release number of selected components (if applicable):
RHEL Version:
RHEL8.2(4.18.0-193.el8)
How reproducible:
100%
Steps to Reproduce:
1. Start a RHEL8.2 AMI in aws.
2. Add another ip to instance and check whether eth0 has 2 ips appears.
Actual results:
The 2nd ip does not appear automatically without this pkg installed
Expected results:
eth0 has 2 ips appears
Additional info:
- This is a new added feature in RHEL-8.2
Vitaly, do you have any thoughts about this change? I've CC'd Eduardo in case there is any integration needed in cloud-init (or maybe this is independent of cloud-init?).
(In reply to Rick Barry from comment #2)
> Vitaly, do you have any thoughts about this change? I've CC'd Eduardo in
> case there is any integration needed in cloud-init (or maybe this is
> independent of cloud-init?).
I've created https://projects.engineering.redhat.com/browse/RHELCMP-1988
This shouldn't require any changes to cloud-init but some additional
testing of the AMIs will definitely be needed.