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:
subsription-manager facts report secondary IP as net.interface.eth0.ipv4_address instead of primary, if secondary address comes before primary in numerical order.
It seems, if there is primary and seconday address, addresses are reported in "numerical order". 27 comes before 227 for example.
Version-Release number of selected component (if applicable):
subscription-manager.x86_64 1.24.26-3.el7_8
How reproducible:
100%
Steps to Reproduce:
1.have host with primary and seconday ip on one interface
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:fe:ea:44 brd ff:ff:ff:ff:ff:ff
inet 192.168.140.227/24 brd 192.168.140.255 scope global noprefixroute dynamic eth0
valid_lft 43186sec preferred_lft 43186sec
inet 192.168.140.27/24 brd 192.168.140.255 scope global secondary noprefixroute eth0:1
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fefe:ea44/64 scope link
valid_lft forever preferred_lft forever
2. #subscription-manager facts
3.
Actual results:
net.interface.eth0.ipv4_address: 192.168.140.27
net.interface.eth0.ipv4_address_list: 192.168.140.227, 192.168.140.27
Expected results:
net.interface.eth0.ipv4_address: 192.168.140.227
net.interface.eth0.ipv4_address_list: 192.168.140.227, 192.168.140.27
Additional info:
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed.
From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."
If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook
Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product.
Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.
[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7
Description of problem: subsription-manager facts report secondary IP as net.interface.eth0.ipv4_address instead of primary, if secondary address comes before primary in numerical order. It seems, if there is primary and seconday address, addresses are reported in "numerical order". 27 comes before 227 for example. Version-Release number of selected component (if applicable): subscription-manager.x86_64 1.24.26-3.el7_8 How reproducible: 100% Steps to Reproduce: 1.have host with primary and seconday ip on one interface 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:fe:ea:44 brd ff:ff:ff:ff:ff:ff inet 192.168.140.227/24 brd 192.168.140.255 scope global noprefixroute dynamic eth0 valid_lft 43186sec preferred_lft 43186sec inet 192.168.140.27/24 brd 192.168.140.255 scope global secondary noprefixroute eth0:1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fefe:ea44/64 scope link valid_lft forever preferred_lft forever 2. #subscription-manager facts 3. Actual results: net.interface.eth0.ipv4_address: 192.168.140.27 net.interface.eth0.ipv4_address_list: 192.168.140.227, 192.168.140.27 Expected results: net.interface.eth0.ipv4_address: 192.168.140.227 net.interface.eth0.ipv4_address_list: 192.168.140.227, 192.168.140.27 Additional info: