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:
We have a customer installing his physical system configured with bonding+LACP and a kickstart specifying "rhsm" directive.
We can see "rhsm" is failing with "Name or service not known", which is due to not having the network fully operational even though NetworkManager task finished.
This seems due to LACP taking time to complete and dropping packets until it's really ready.
We are sure the issue is network-related since, by using the following %pre script, we could confirm no network resolution was happening (we could have tested with an IP address instead as well):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
%pre
systemd-run -u ping.service /bin/sh -c "while :; do ping -c 1 www.google.com; sleep 1; done"
%end
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
- ping service output:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Nov 21 09:55:03 system.hostname systemd[1]: Started /bin/sh -c while :; do ping -c 1 www.google.com; sleep 1; done.
Nov 21 09:55:03 system.hostname sh[2433]: ping: www.google.com: Name or service not known
Nov 21 09:55:04 system.hostname sh[2441]: ping: www.google.com: Name or service not known
Nov 21 09:55:10 system.hostname sh[2506]: ping: www.google.com: Name or service not known
Nov 21 09:55:11 system.hostname sh[2867]: ping: www.google.com: Name or service not known
Nov 21 09:55:12 system.hostname sh[2872]: ping: www.google.com: Name or service not known
Nov 21 09:55:18 system.hostname sh[2877]: PING www.google.com (216.58.215.228) 56(84) bytes of data.
Nov 21 09:55:18 system.hostname sh[2877]: --- www.google.com ping statistics ---
Nov 21 09:55:19 system.hostname sh[2887]: PING www.google.com (172.217.168.4) 56(84) bytes of data.
Nov 21 09:55:19 system.hostname sh[2887]: --- www.google.com ping statistics ---
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
- Network Manager configuring the bond:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Nov 21 09:55:05 system.hostname NetworkManager[2143]: <debug> [1669024505.4533] device[bf104700e7268d2a] (bond0): slave ens3f1 state change 90 (secondaries) -> 100 (activated)
[...]
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0]: start running ordered scripts...
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/04-iscsi": run script
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/04-iscsi": complete
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp": run script
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp": complete
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-onoffline": run script
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-onoffline": complete
Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0]: completed (3 scripts)
Nov 21 09:55:06 system.hostname anaconda[2234]: anaconda: network: Apply kickstart result: ['bond0']
Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:/etc/NetworkManager/system-connections/bond0.nmconnection:
Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:id=bond0
Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:interface-name=bond0
Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:{'connection': {'autoconnect-retries': <1>, 'id': <'bond0'>, 'interface-name': <'bond0'>, 'multi-connect': <1>, 'permissions': <@as []>, 'timestamp': <uint64 1669024478>, 'type': <'bond'>, 'uuid': <'0aed94b9-b30d-4366-b144-3d9b797fb2c3'>}, '802-3-ethernet': {'auto-negotiate': <false>, 'mac-address-blacklist': <@as []>, 'mtu': <uint32 1500>, 's390-options': <@a{ss} {}>}, 'bond': {'interface-name': <'bond0'>, 'options': <{'lacp_rate': '1', 'miimon': '100', 'mode': '802.3ad', 'xmit_hash_policy': 'layer2+3'}>}, 'ipv4': {'address-data': <[{'address': <'XXX'>, 'prefix': <uint32 xx>}]>, 'dns': <[uint32 xxx, xxx]>, 'dns-search': <@as []>, 'gateway': <'XXX'>, 'method': <'manual'>, 'route-data': <@aa{sv} []>}, 'ipv6': {'addr-gen-mode': <0>, 'address-data': <@aa{sv} []>, 'dns-search': <@as []>, 'method': <'ignore'>, 'route-data': <@aa{sv} []>}, 'proxy': {}, 'user': {'data': <{'org.freedesktop.NetworkManager.origin': 'nm-initrd-generator'}>}}
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
- RHSM executing
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Subscription/Task/2.
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: INFO:anaconda.threading:Running Thread: AnaTaskThread-RegisterAndSubscribeTask-1 (140092470896192)
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.runtime:registration attempt: provisioning system for Satellite
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.runtime:registration attempt: downloading Satellite provisioning script
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.runtime:subscription: downloading Satellite provisioning script
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.satellite:subscription: fetching Satellite provisioning script from: http://satellite.server/pub/katello-rhsm-consumer
:
Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.satellite:subscription: can't download Satellite provisioning script from http://satellite.server/pub/katello-rhsm-consumer with proxy: {}. Error: HTTPConnectionPool(host='satellite.server', port=80): Max retries exceeded with url: /pub/katello-rhsm-consumer (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f69d1f9b550>: Failed to establish a new connection: [Errno -2] Name or service not known'))
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Version-Release number of selected component (if applicable):
anaconda-34.25.0.29-1.el9_0
How reproducible:
Always on customer system. Don't have LACP to check.
Steps to Reproduce:
1. Have a bond with LACP and "slow negotiation"
2. Specify "rhsm" directive in kickstart
Actual results:
rhsm fails
Expected results:
rhsm succeeds
Hi Radku, could you please take a look on this if it is a NetworkManager issue or RHSM?
Comment 22RHEL Program Management
2023-09-18 15:58:44 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 23RHEL Program Management
2023-09-18 16:00:02 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 24Red Hat Bugzilla
2024-01-17 04:25:24 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Description of problem: We have a customer installing his physical system configured with bonding+LACP and a kickstart specifying "rhsm" directive. We can see "rhsm" is failing with "Name or service not known", which is due to not having the network fully operational even though NetworkManager task finished. This seems due to LACP taking time to complete and dropping packets until it's really ready. We are sure the issue is network-related since, by using the following %pre script, we could confirm no network resolution was happening (we could have tested with an IP address instead as well): -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- %pre systemd-run -u ping.service /bin/sh -c "while :; do ping -c 1 www.google.com; sleep 1; done" %end -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- - ping service output: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Nov 21 09:55:03 system.hostname systemd[1]: Started /bin/sh -c while :; do ping -c 1 www.google.com; sleep 1; done. Nov 21 09:55:03 system.hostname sh[2433]: ping: www.google.com: Name or service not known Nov 21 09:55:04 system.hostname sh[2441]: ping: www.google.com: Name or service not known Nov 21 09:55:10 system.hostname sh[2506]: ping: www.google.com: Name or service not known Nov 21 09:55:11 system.hostname sh[2867]: ping: www.google.com: Name or service not known Nov 21 09:55:12 system.hostname sh[2872]: ping: www.google.com: Name or service not known Nov 21 09:55:18 system.hostname sh[2877]: PING www.google.com (216.58.215.228) 56(84) bytes of data. Nov 21 09:55:18 system.hostname sh[2877]: --- www.google.com ping statistics --- Nov 21 09:55:19 system.hostname sh[2887]: PING www.google.com (172.217.168.4) 56(84) bytes of data. Nov 21 09:55:19 system.hostname sh[2887]: --- www.google.com ping statistics --- -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- - Network Manager configuring the bond: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Nov 21 09:55:05 system.hostname NetworkManager[2143]: <debug> [1669024505.4533] device[bf104700e7268d2a] (bond0): slave ens3f1 state change 90 (secondaries) -> 100 (activated) [...] Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0]: start running ordered scripts... Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/04-iscsi": run script Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/04-iscsi": complete Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp": run script Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp": complete Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-onoffline": run script Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0], "/usr/lib/NetworkManager/dispatcher.d/20-chrony-onoffline": complete Nov 21 09:55:05 system.hostname nm-dispatcher[2444]: req:14 'up' [bond0]: completed (3 scripts) Nov 21 09:55:06 system.hostname anaconda[2234]: anaconda: network: Apply kickstart result: ['bond0'] Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:/etc/NetworkManager/system-connections/bond0.nmconnection: Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:id=bond0 Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:interface-name=bond0 Nov 21 09:55:06 system.hostname org.fedoraproject.Anaconda.Modules.Network[2311]: DEBUG:anaconda.modules.network.network:{'connection': {'autoconnect-retries': <1>, 'id': <'bond0'>, 'interface-name': <'bond0'>, 'multi-connect': <1>, 'permissions': <@as []>, 'timestamp': <uint64 1669024478>, 'type': <'bond'>, 'uuid': <'0aed94b9-b30d-4366-b144-3d9b797fb2c3'>}, '802-3-ethernet': {'auto-negotiate': <false>, 'mac-address-blacklist': <@as []>, 'mtu': <uint32 1500>, 's390-options': <@a{ss} {}>}, 'bond': {'interface-name': <'bond0'>, 'options': <{'lacp_rate': '1', 'miimon': '100', 'mode': '802.3ad', 'xmit_hash_policy': 'layer2+3'}>}, 'ipv4': {'address-data': <[{'address': <'XXX'>, 'prefix': <uint32 xx>}]>, 'dns': <[uint32 xxx, xxx]>, 'dns-search': <@as []>, 'gateway': <'XXX'>, 'method': <'manual'>, 'route-data': <@aa{sv} []>}, 'ipv6': {'addr-gen-mode': <0>, 'address-data': <@aa{sv} []>, 'dns-search': <@as []>, 'method': <'ignore'>, 'route-data': <@aa{sv} []>}, 'proxy': {}, 'user': {'data': <{'org.freedesktop.NetworkManager.origin': 'nm-initrd-generator'}>}} -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- - RHSM executing -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Subscription/Task/2. Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: INFO:anaconda.threading:Running Thread: AnaTaskThread-RegisterAndSubscribeTask-1 (140092470896192) Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.runtime:registration attempt: provisioning system for Satellite Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.runtime:registration attempt: downloading Satellite provisioning script Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.runtime:subscription: downloading Satellite provisioning script Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.satellite:subscription: fetching Satellite provisioning script from: http://satellite.server/pub/katello-rhsm-consumer : Nov 21 09:55:08 system.hostname org.fedoraproject.Anaconda.Modules.Subscription[2305]: DEBUG:anaconda.modules.subscription.satellite:subscription: can't download Satellite provisioning script from http://satellite.server/pub/katello-rhsm-consumer with proxy: {}. Error: HTTPConnectionPool(host='satellite.server', port=80): Max retries exceeded with url: /pub/katello-rhsm-consumer (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f69d1f9b550>: Failed to establish a new connection: [Errno -2] Name or service not known')) -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Version-Release number of selected component (if applicable): anaconda-34.25.0.29-1.el9_0 How reproducible: Always on customer system. Don't have LACP to check. Steps to Reproduce: 1. Have a bond with LACP and "slow negotiation" 2. Specify "rhsm" directive in kickstart Actual results: rhsm fails Expected results: rhsm succeeds