Bug 1480534

Summary: OSP11 -> OSP12 upgrade: major-upgrade-composable-steps-docker fails during gnocchi_db_sync with: stderr: su: unrecognized option '--sacks-number=128'
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: openstack-tripleo-heat-templatesAssignee: Jose Luis Franco <jfrancoa>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 12.0 (Pike)CC: apannu, dbecker, jschluet, mburns, morazi, rhel-osp-director-maint, sathlang
Target Milestone: betaKeywords: AutomationBlocker, Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170805163047.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:52:15 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:    
Bug Blocks: 1399762    

Description Marius Cornea 2017-08-11 10:32:19 UTC
Description of problem:
OSP11 -> OSP12 upgrade: major-upgrade-composable-steps-docker fails during gnocchi_db_sync with: stderr: su: unrecognized option '--sacks-number=128'

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-7.0.0-0.20170805163045.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP11
2. Upgrade to OSP12

Actual results:
Upgrade fails during major-upgrade-composable-steps-docker 

Expected results:
Upgrade completes ok.

Additional info:

Comment 1 Jon Schlueter 2017-08-11 13:00:15 UTC
Upstream work on this bug is in progress

https://review.openstack.org/#/c/491826/6 has Review +2 and awaiting CI checks.

Comment 7 errata-xmlrpc 2017-12-13 21:52:15 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