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

Bug 1443652

Summary: Swift ringbuilding logic coupled to Controller/ObjectStorage roles
Product: Red Hat OpenStack Reporter: Christian Schwede (cschwede) <cschwede>
Component: openstack-tripleo-heat-templatesAssignee: Christian Schwede (cschwede) <cschwede>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: cschwede, jliberma, mburns, pgrist, rhel-osp-director-maint, slinaber
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 11.0 (Ocata)Flags: jliberma: needinfo?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-6.2.0-2.el7ost puppet-tripleo-6.5.0-7.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-13 21:43:17 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 Christian Schwede (cschwede) 2017-04-19 15:52:05 UTC 
Description of problem:

When using a composable role that is not named "Controller" or "ObjectStorage", existing rings will not be fetched from the undercloud. This might lead to consistency issues.

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

11

How reproducible:

Always

Steps to Reproduce:
1. Create a new role, name it "Example" and include the Swift proxy and/or storage service
2. Deploy an overcloud without that role
3. Update the overcloud, adding the above role

Actual results:

md5sums of /etc/swift/*.ring.gz mismatch between nodes

Expected results:

md5sums of /etc/swift/*.ring.gz must be identical

Additional info:
Comment 1 Christian Schwede (cschwede) 2017-04-25 16:00:54 UTC 
There is a simple workaround in case one uses a custom role and needs Swift rings on it. In that case you can use an extra template like this:

 resource_registry:
  OS::TripleO::NodeExtraConfigPost: /usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/swift-ring-deploy.yaml

And - assuming it's named swiftrings.yaml - deploy with sth like this:

overcloud deploy --templates -e swiftrings.yaml.

Nodes will fetch the rings from the undercloud after step5, when other nodes already sent their updated rings to the undercloud, so afterwards all nodes will be using the same rings.

This is just and intermediate workaround until this fix is packaged.
Comment 8 errata-xmlrpc 2017-09-13 21:43:17 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:2721