Bug 1431593
Summary: | OSP10 -> OSP11 upgrade fails on environment with radosgw service enabled | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> | ||||
Component: | openstack-tripleo-heat-templates | Assignee: | Keith Schincke <kschinck> | ||||
Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> | ||||
Severity: | urgent | Docs Contact: | Derek <dcadzow> | ||||
Priority: | unspecified | ||||||
Version: | 11.0 (Ocata) | CC: | dbecker, gfidente, jomurphy, jschluet, mburns, mcornea, morazi, rhel-osp-director-maint, scohen | ||||
Target Milestone: | rc | ||||||
Target Release: | 11.0 (Ocata) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | openstack-tripleo-heat-templates-6.0.0-7.el7ost | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-05-17 20:07:24 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: |
|
I was able to reproduce this issue on an environment where the radosgw service is running on monolithic controllers(3 controllers, 2 computes and 3 ceph osd nodes). Marius, Which set of documentation are you using for your upgrade? Keith (In reply to Keith Schincke from comment #2) > Marius, > > Which set of documentation are you using for your upgrade? > The upgrade procedure: https://gitlab.cee.redhat.com/mandreou/OSP10-OSP11-Upgrade/blob/master/README.md I have found the where the error is occurring. ceph::rgw:keystone:auth has a call to create the needed roles (1). The keystone provider checks for the role existing(2) before attempting to add (3). OpenStack 10/Newton adds a role named "Member". OpenStack 11/Ocata adds a role named 'member'. The check does not match "Member" is not the same as "member" but the add fails in keystone because "Member" already exists. I am working with the stream people to get a fix. 1: https://github.com/openstack/puppet-ceph/blob/master/manifests/rgw/keystone/auth.pp#L81 2: https://github.com/openstack/puppet-keystone/blob/master/lib/puppet/provider/keystone_role/openstack.rb#L66 3: https://github.com/openstack/puppet-keystone/blob/master/lib/puppet/provider/keystone_role/openstack.rb#L29 verified on openstack-tripleo-heat-templates-6.0.0-7.el7ost.noarch 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:1245 |
Created attachment 1262401 [details] os-collect-config log Description of problem: OSP10 -> OSP11 upgrade fails on environment with radosgw deployed on a custom role: Error: Execution of '/usr/bin/openstack role create --format shell member' returned 1: Conflict occurred attempting to store role - Duplicate entry found with name member. (HTTP 409) (Request-ID: req-7a0ec0ae-bcb2-4574-bcaf-c8921f55ca5f) Error: /Stage[main]/Ceph::Rgw::Keystone::Auth/Keystone_role[member]/ensure: change from absent to present failed: Execution of '/usr/bin/openstack role create --format shell member' returned 1: Conflict occurred attempting to store role - Duplicate entry found with name member. (HTTP 409) (Request-ID: req-7a0ec0ae-bcb2-4574-bcaf-c8921f55ca5f) Warning: /Stage[main]/Ceph::Rgw::Keystone::Auth/Keystone_user_role[swift@service]: Skipping because of failed dependencies Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-6.0.0-0.20170303152752.0rc1.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy OSP10 with radosgw service enabled on a custom role running systemd managed services 2. Run upgrade OSP10->OSP11 procedure on top of it Actual results: Upgrade fails during major-upgrade-composable-steps.yaml Expected results: Upgrade succeeds. Additional info: Attaching the os-collect-config log.