Bug 1497959 - RHCS upgrade 2.4 - 3.0: Ceph-mgr daemons are not active after upgrade.
Summary: RHCS upgrade 2.4 - 3.0: Ceph-mgr daemons are not active after upgrade.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 3.0
Assignee: Sébastien Han
QA Contact: Parikshith
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-03 08:44 UTC by Parikshith
Modified: 2017-12-05 23:46 UTC (History)
9 users (show)

Fixed In Version: RHEL: ceph-ansible-3.0.0-0.1.rc15.el7cp Ubuntu: ceph-ansible_3.0.0~rc15-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-05 23:46:42 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 1974 0 None closed upgrade: a support for mgrs 2020-08-30 23:30:46 UTC
Red Hat Product Errata RHBA-2017:3387 0 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix and enhancement update 2017-12-06 03:03:45 UTC

Description Parikshith 2017-10-03 08:44:04 UTC 
Description of problem:
After the the upgrade to  the latest 3.0 build ceph-mgr daemons are not active.

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


How reproducible:


Steps to Reproduce:
1. Install 2.4 cluster.
2. Before upgrading add ceph-mgr nodes in /etc/ansible/hosts.
3. Upgrade to 3.0.

Actual results:
ceph-mgr is not active
$sudo ceph -s --cluster slave
  cluster:
    id:     90d9b741-589c-490f-a4a2-a25ad83153f8
    health: HEALTH_WARN
            no active mgr

Expected results:
ceph-mgr service should be active

Additional info:
After upgrade ceph-mgr packages are installed
rpm -qa | grep ceph-mgr
ceph-mgr-12.2.1-9.el7cp.x86_64
Comment 3 Sébastien Han 2017-10-03 17:57:45 UTC 
fix in rc15
Comment 12 errata-xmlrpc 2017-12-05 23:46:42 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:3387
Note You need to log in before you can comment on or make changes to this bug.