Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1722002

Summary: Rolling updates fails on mds depdency when excluding mdss from ansible hosts file
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: James Biao <jbiao>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED WONTFIX QA Contact: Vasishta <vashastr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3CC: aschoen, assingh, ceph-eng-bugs, dsavinea, gmeno, mmuench, nthomas, tserlin
Target Milestone: z2   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 14:07:23 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 James Biao 2019-06-19 11:02:47 UTC
Description of problem:

Per installation guide, when upgrading RHCS 3.x minor versions, an environment with CephFS should not upgrade mons and mds at the same time. And the recommend way is updating mon first. [1]

----------
When using the rolling_update.yml playbook to upgrade to any Red Hat Ceph Storage 3.x version, users who use the Ceph File System (CephFS) must manually update the Metadata Server (MDS) cluster. This is due to a known issue. 
----------

This causes dependency issue when MDS and mon are collocated.

Errors:
------------
 "msg": "Error: Package: 2:ceph-mds-12.2.5-42.el7cp.x86_64 (@rh_storage_tools)\n           Requires: ceph-base = 2:12.2.5-42.el7cp\n           Removing: 2:ceph-base-12.2.5-42.el7cp.x86_64 (@rh_storage_mon)\n               ceph-base = 2:12.2.5-42.el7cp\n           Updated By: 2:ceph-base-12.2.8-128.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.8-128.el7cp\n           Available: 2:ceph-base-12.2.1-40.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.1-40.el7cp\n           Available: 2:ceph-base-12.2.1-45.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.1-45.el7cp\n           Available: 2:ceph-base-12.2.1-46.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.1-46.el7cp\n           Available: 2:ceph-base-12.2.4-6.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.4-6.el7cp\n           Available: 2:ceph-base-12.2.4-10.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.4-10.el7cp\n           Available: 2:ceph-base-12.2.4-30.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.4-30.el7cp\n           Available: 2:ceph-base-12.2.4-42.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.4-42.el7cp\n           Available: 2:ceph-base-12.2.5-59.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.5-59.el7cp\n           Available: 2:ceph-base-12.2.8-52.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.8-52.el7cp\n           Available: 2:ceph-base-12.2.8-89.el7cp.x86_64 (rhel-7-server-rhceph-3-mon-rpms)\n               ceph-base = 2:12.2.8-89.el7cp\n", 
    "rc": 1, 

--------------

[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/installation_guide_for_red_hat_enterprise_linux/index#upgrading-a-red-hat-ceph-storage-cluster    

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


How reproducible:
100%

Steps to Reproduce:


1. mon and mdss co-location

2. Follow the config of upgrade guide [1] chapter 4.1

3. As the note of the guide, do not update mdss together with mon. comment mdss out from the /etc/ansible/hosts

4. run ansible-playbook rolling_update.yml 


Actual results:

mons upgrade requires mds dependency and failed

Expected results:
upgrade successful

Additional info:
Reproducer info at comment 1

Comment 3 Giridhar Ramaraju 2019-08-05 13:09:05 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 4 Giridhar Ramaraju 2019-08-05 13:10:25 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 5 Giridhar Ramaraju 2019-08-20 07:17:19 UTC
Level setting the severity of this defect to "High" with a bulk update. Pls
refine it to a more closure value, as defined by the severity definition in
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity