This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2153208 - Install fails with "Started cancel waiting for multipath siblings of nvme1n1"
Summary: Install fails with "Started cancel waiting for multipath siblings of nvme1n1"
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.7
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-14 09:50 UTC by Marta Vila Fernandes
Modified: 2024-01-17 04:25 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 16:08:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4757 0 None Migrated None 2023-09-18 16:08:06 UTC
Red Hat Issue Tracker RHELPLAN-142123 0 None None None 2022-12-14 09:53:49 UTC

Description Marta Vila Fernandes 2022-12-14 09:50:30 UTC 
Description of problem:

Hello,

While trying to perform a kickstart install with an image which includes device-mapper-multipath-0.8.4-32.el8, all 24 of the nodes stopped at the same message:

[OK] Started cancel waiting for multipath siblings of nvme1n1
[OK] Started cancel waiting for multipath siblings of nvme0n1

There is a private bug #1916168 reporting this error, but looking into the changelog it should be already solved on device-mapper-multipath-0.8.4-28:

2022-08-24 - Benjamin Marzinski <bmarzins> 0.8.4-28
- Add 0110-multipath-fix-systemd-timers-in-the-initramfs.patch
- Resolves: bz #1916168

Could you please take a look and helping me trying to understand why I'm still getting these error messages?

Thanks in advance!


Version-Release number of selected component (if applicable):

device-mapper-multipath-0.8.4-32.el8


Actual results:

[OK] Started cancel waiting for multipath siblings of nvme1n1
[OK] Started cancel waiting for multipath siblings of nvme0n1
Comment 1 Ben Marzinski 2022-12-14 16:31:38 UTC 
Does this install need multipath? If not, can you try booting with "nompath" added to the kernel commandline. This will completely disable multipath.  These messages should go away. If the install works with multipath disabled, then this is likely a multipath problem, and I'll look into it further. If the install still fails, then multipath shouldn't be at fault here, and these messages just happened to be the last thing printed.  In that case, I'll move the bug over to the anaconda team.
Comment 5 Jeff Bastian 2022-12-14 22:00:33 UTC 
Marta, please also try booting with rd.debug on the command line (*).  I hit this same issue today and the serial console logs on my system showed the DHCP client was failing to get an IP address.  I'm curious if your system is having the same issue.  If so, this is likely a bug in NetworkManager instead of multipath.

(*) rd.debug turns on verbose output from dracut, the tool that builds the initial RAM-disk used when booting:
    https://fedoraproject.org/wiki/How_to_debug_Dracut_problems#Summary_of_dracut_kernel_command_line_options
Comment 6 Jeff Bastian 2022-12-14 22:54:44 UTC 
Marta, also, can you open a customer support ticket at https://access.redhat.com/ ?  Bugzilla is our software engineering tool, and access.redhat.com is our customer support tool.  I want to make sure your issue does not get lost, and customer support will help with that.
Comment 7 jukka.tuunanen 2022-12-22 14:09:42 UTC 
We have been facing this issue when kickstart installing Supermicro storage servers and hypervisors.

It seems the installer does not reach the kickstart ks file before the issue occurs.
I think the problem is the initrd.img file, that was updated last time 2022-11-25.

When using frozen private repository which offers older version of initrd.img, the 8-stream installation succeeds.
Comment 8 Ben Marzinski 2023-01-12 17:36:18 UTC 
Since the hang still occurs with nompath set, it doesn't appear to be a multipath issue. Reassigning to anaconda, to see if they know what's going on here.
Comment 9 Marta Vila Fernandes 2023-01-13 11:00:52 UTC 
The problem was related with the network interfaces. Thanks for your support.
Comment 10 Jan Stodola 2023-01-19 16:37:51 UTC 
Marta, if you are still able to reproduce the problem, could you please boot the installer with "rd.debug" on the kernel command line and provide the console output?
Thank you, Jan
Comment 11 RHEL Program Management 2023-09-18 16:03:45 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 12 RHEL Program Management 2023-09-18 16:08:50 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 13 Red Hat Bugzilla 2024-01-17 04:25:25 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.