Bug 1508476 - TripleO needs to format SwiftRawDisks before attempting to mount
Summary: TripleO needs to format SwiftRawDisks before attempting to mount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 12.0 (Pike)
Assignee: Thiago da Silva
QA Contact: Mike Abrams
URL:
Whiteboard: scale_lab
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-01 14:01 UTC by Thiago da Silva
Modified: 2018-02-05 19:15 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.3-11.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 22:19:18 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1732670 0 None None None 2017-11-16 11:34:29 UTC
OpenStack gerrit 521505 0 None MERGED Format SwiftRawDisks before attempting to mount 2020-07-15 08:24:01 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Thiago da Silva 2017-11-01 14:01:17 UTC 
Alex Krzos ran into a problem where when providing a list of disks that were not formatted as the value for SwiftRawDisks, TripleO did not format those disks before attempting to mount them.

Alex already proposed a patch upstream for this bug: https://review.openstack.org/#/c/516436/
Comment 1 Christian Schwede (cschwede) 2017-11-15 12:38:48 UTC 
This happens only in containerized environments when using the SwiftRawDisk parameter.
Comment 2 Christian Schwede (cschwede) 2017-11-21 06:15:31 UTC 
Backported patch merged, moving to POST.
Comment 3 Jon Schlueter 2017-11-21 21:25:44 UTC 
openstack-tripleo-heat-templates-7.0.3-11.el7ost
Comment 9 errata-xmlrpc 2017-12-13 22:19:18 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/RHEA-2017:3462
Note You need to log in before you can comment on or make changes to this bug.