Bug 1444967

Summary: [backport] puppet-ceph isn't handling dev by id so ceph-disk parepare runs multiple times and fails
Product: Red Hat OpenStack Reporter: John Fulton <johfulto>
Component: puppet-cephAssignee: John Fulton <johfulto>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: bengland, dcadzow, jjoyce, jomurphy, jschluet, jtaleric, slinaber, tvignaud, twilkins, yrabl
Target Milestone: z3Keywords: FeatureBackport, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-ceph-2.3.0-5.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1444909 Environment:
Last Closed: 2017-06-28 14:48:28 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:
Bug Depends On: 1444909    
Bug Blocks:    

Comment 1 John Fulton 2017-04-24 15:51:23 UTC
This is a request to backport the fix to the following bug to OSP 10: 

puppet-ceph isn't handling dev by id so ceph-disk parepare runs multiple times and fails.

puppet-ceph works fine if you pass it paths to block devices like /dev/sdb. It _should_ also handle paths like /dev/disk/by-path/pci-0000:03:00.0-scsi-0:2:16:0. However when dev by id is passed it attempts to try to ceph-disk prepare multiple times because it cannot tell that the disk is already prepared because its clause to determine this fails.

It is necessary to pass dev by id sometimes if a system doesn't have consitent assignment of block devices between boots. So this is a scenario puppet-ceph should support.

Comment 2 Red Hat Bugzilla Rules Engine 2017-04-24 15:51:31 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 7 Yogev Rabl 2017-05-30 12:23:55 UTC
verified on puppet-ceph-2.3.0-5.el7ost.noarch

Comment 9 errata-xmlrpc 2017-06-28 14:48:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1585