Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1959023

Summary: 16.1 Baremetal overcloud Update failing: "Failure prepping block device., Code: 500"
Product: Red Hat OpenStack Reporter: myadla
Component: openstack-tripleoAssignee: James Slagle <jslagle>
Status: CLOSED NOTABUG QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16.1 (Train)CC: dpeacock, elicohen, jkreger, mburns, myadla, nweinber, ramishra, sbaker
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 20:38:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description myadla 2021-05-10 15:17:49 UTC
Description of problem:

16.1 Overcloud Update failing: "Failure prepping block device., Code: 500"

2021-05-04 07:40:37Z [overcloud.Compute.1.NovaCompute]: CREATE_FAILED  ResourceInError: resources.NovaCompute: Went to status ERROR due to "Message: Build of instance 960e5232-a074-46d6-8fc7-7c60461a8a04 aborted: Failure prepping block device., Code: 500"

2021-05-04 07:40:53Z [overcloud.Controller.0.Controller]: CREATE_FAILED  ResourceInError: resources.Controller: Went to status ERROR due to "Message: Build of instance 2f2ced61-756c-4b34-a118-12888939ba72 aborted: Failure prepping block device., Code: 500"

 Stack overcloud/c393cb52-ecfb-4604-a1f8-328ee0a730e6 CREATE_FAILED 

overcloud.Controller.0.Controller:
  resource_type: OS::TripleO::ControllerServer
  physical_resource_id: 2f2ced61-756c-4b34-a118-12888939ba72
  status: CREATE_FAILED
  status_reason: |
    ResourceInError: resources.Controller: Went to status ERROR due to "Message: Build of instance 2f2ced61-756c-4b34-a118-12888939ba72 aborted: Failure prepping block device., Code: 500"
overcloud.Controller.2.Controller:
  resource_type: OS::TripleO::ControllerServer
  physical_resource_id: cca23aaa-3d37-46b2-bea2-ca58ddc073d0
  status: CREATE_FAILED
  status_reason: |
    ResourceInError: resources.Controller: Went to status ERROR due to "Message: Build of instance cca23aaa-3d37-46b2-bea2-ca58ddc073d0 aborted: Failure prepping block device., Code: 500"
overcloud.Controller.1.Controller:
  resource_type: OS::TripleO::ControllerServer
  physical_resource_id: 56a57c86-e854-4d80-bc1b-e2424ee50626
  status: CREATE_FAILED
  status_reason: |
    ResourceInError: resources.Controller: Went to status ERROR due to "Message: Build of instance 56a57c86-e854-4d80-bc1b-e2424ee50626 aborted: Failure prepping block device., Code: 500"
overcloud.Compute.0.NovaCompute:
  resource_type: OS::TripleO::ComputeServer
  physical_resource_id: 508fd413-0638-4a5b-8158-c2fde70434e7
  status: CREATE_FAILED
  status_reason: |
    ResourceInError: resources.NovaCompute: Went to status ERROR due to "Message: Build of instance 508fd413-0638-4a5b-8158-c2fde70434e7 aborted: Failure prepping block device., Code: 500"
overcloud.Compute.1.NovaCompute:
  resource_type: OS::TripleO::ComputeServer
  physical_resource_id: 960e5232-a074-46d6-8fc7-7c60461a8a04
  status: CREATE_FAILED
  status_reason: |
    ResourceInError: resources.NovaCompute: Went to status ERROR due to "Message: Build of instance 960e5232-a074-46d6-8fc7-7c60461a8a04 aborted: Failure prepping block device., Code: 500"

Log: http://rhos-ci-logs.lab.eng.tlv2.redhat.com/logs/rcj/DFG-enterprise-baremetal-update-16.1-passed_phase2_from_latest_cdn-3control_2compute_externalceph-regression/6/titan101.lab.eng.tlv2.redhat.com/home/stack/overcloud_install.log.gz

Version-Release number of selected component (if applicable):
RHOS-16.1-RHEL-8-20210323.n.0

How reproducible: 100%


Steps to Reproduce:
1.Run enterprise baremetal 16.1 update job


Actual results:


Expected results:


Additional info:

Comment 1 Rabi Mishra 2021-05-10 16:31:41 UTC

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

Comment 2 Julia Kreger 2021-05-18 19:51:43 UTC
The issue here is that instackenv file does not define a port mac address, and an uses a redfish_address FQDN that cannot be used to match to the baremetal node BMC address which is identified in inspection. Because of this disparity, the mac address needs to be defined in the instackenv configuration file.

Comment 3 Steve Baker 2021-05-25 20:38:47 UTC
We believe the job environment was fixed and this is working now

Comment 4 Red Hat Bugzilla 2023-09-15 01:33:59 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days