Bug 2227529 - node deploying fails with ironic-conductor error mount: /tmp/tmp63ht2umu: /dev/sdr3 already mounted on /tmp/tmp63ht2umu
Summary: node deploying fails with ironic-conductor error mount: /tmp/tmp63ht2umu: /de...
Keywords:
Status: CLOSED DUPLICATE of bug 2134529
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-python-agent
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Steve Baker
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-30 13:41 UTC by alisci
Modified: 2023-08-22 12:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-21 19:42:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-27029 0 None None None 2023-07-30 13:42:06 UTC

Description alisci 2023-07-30 13:41:48 UTC
Description of problem:
failure doing a scaling out of ceph node.
the deployment show the following error on ironic-conductor logs:

ERROR ironic.conductor.utils [req-ce122274-9557-446c-bf1a-0e08cf8e436c - - - - -] Failed to install a bootloader when deploying node xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Error: {'type': 'CommandExecutionError', 'code': 500, 'message': "Command execution failed: Installing GRUB2 boot loader to device /dev/sdr failed with Unexpected error while running command.\nCommand: mount /dev/sdr3 /tmp/tmp63ht2umu\nExit code: 32\nStdout: ''\nStderr: 'mount: /tmp/tmp63ht2umu: /dev/sdr3 already mounted on /tmp/tmp63ht2umu.\\n'.", 'details': "Installing GRUB2 boot loader to device /dev/sdr failed with Unexpected error while running command.\nCommand: mount /dev/sdr3 /tmp/tmp63ht2umu\nExit code: 32\nStdout: ''\nStderr: 'mount: /tmp/tmp63ht2umu: /dev/sdr3 already mounted on /tmp/tmp63ht2umu.\\n'."}


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


futher details on private attachments

Comment 11 Steve Baker 2023-08-21 19:42:18 UTC
Closing for now on the assumption that this issue will go away after the cluster is updated to z4, it can be reopened if necessary.

*** This bug has been marked as a duplicate of bug 2134529 ***


Note You need to log in before you can comment on or make changes to this bug.