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

Bug 1243037

Summary: [ironic-conductor] disk-partition issue
Product: Red Hat OpenStack Reporter: Joe Talerico <jtaleric>
Component: openstack-ironicAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Toure Dunnon <tdunnon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: DirectorCC: dtantsur, srevivo
Target Milestone: ---Keywords: ZStream
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-06 14:40:26 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:
Attachments:
Description Flags
ironic-conductor none

Description Joe Talerico 2015-07-14 15:25:34 UTC
Created attachment 1051917 [details]
ironic-conductor

Description of problem:
One of my nodes is reporting the below :
ironic-conductor.log:2015-07-14 07:33:24.953 24472 ERROR ironic.drivers.modules.deploy_utils [-] Command: sudo ironic-rootwrap /etc/ironic/rootwrap.conf parted -a optimal -s /dev/disk/by-path/ip-192.0.2.23:3260-iscsi-iqn-ee4db5c0-985b-4a1e-a74b-8210ce9e2673-lun-1 -- unit MiB mklabel msdos mkpart primary  1 2 mkpart primary  2 40962 set 2 boot on

When attempting to deploy any overcloud, the node that experienced the ERROR above never is utilized.

Comment 4 Dmitry Tantsur 2015-07-15 13:19:05 UTC
What caught my eye is *dozens* of the following errors every 2 seconds:
NodeAssociated: Node 0a9965c0-d483-49f7-ae93-22a09de7e4dd is associated with instance 6027bafb-d1bc-46c3-9646-2abdd93134a0.
Looks like nova tries to schedule on the same occupied node... and partitioning failures appear only in the beginning, not sure they're actually root cause of the problem.

Comment 5 Lucas Alvares Gomes 2016-07-01 15:48:26 UTC
Hi Joe,

Strange error indeed, it's like the disk was being accessed by another process at the moment Ironic was trying to create the partitions.

Is this bug reproducible somehow?

Comment 6 Joe Talerico 2016-07-01 16:59:16 UTC
Hey Lucas - I haven't seen this error in awhile. If it reproduces I will be sure to update this bz. Do the logs not provide enough insight?

Comment 7 Lucas Alvares Gomes 2016-09-06 14:40:26 UTC
(In reply to Joe Talerico from comment #6)
> Hey Lucas - I haven't seen this error in awhile. If it reproduces I will be
> sure to update this bz. Do the logs not provide enough insight?

Yeah I can't figure out the reason just by looking at that error. I will mark this as closed but feel free to re-open in case you hit this problem again.

Thanks for reporting