DescriptionKen Dreyer (Red Hat)
2017-12-21 20:05:24 UTC
+++ This bug was initially created as a clone of Bug #1525209 +++
Description of problem:
When upgrading from OSP11 to OSP12 container, ceph-ansible attempts to disable the RGW service provided by the overcloud image. The task attempts to stop/disable ceph-rgw@{{ ansible-hostname }} and ceph-radosgw@{{ ansible-hostname }}.service. The actual service name is ceph-radosgw@radosgw.$name
Version-Release number of selected component (if applicable):
ceph-ansible-3.0.14-1.el7cp.noarch
How reproducible:
Steps to Reproduce:
1. Install OSP11
2. Upgrade to OSP12
3.
Actual results:
radosgw system service remains enabled. this causes the radosgw container service to go into a failed state due to the port being bound.
Expected results:
radosgw system service disabled.
radosgw container service running
Additional info:
Working to replicate the reported issue.
--- Additional comment from leseb on 2017-12-15 03:52:59 MST ---
Just to be sure, is it when running rolling_update.yml?
--- Additional comment from Giulio Fidente on 2017-12-15 08:28:38 MST ---
(In reply to leseb from comment #1)
> Just to be sure, is it when running rolling_update.yml?
No, this is with switch-from-non-containerized-to-containerized-ceph-daemons.yml
Comment 4Ken Dreyer (Red Hat)
2018-01-18 23:39:45 UTC
From the RHCEPH 2.5 clone (bug 1525209), v3.0.16 FailedQA. We're going to try again with v3.0.18.
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-2018:0474