Bug 1943471

Summary: [Ceph-Ansible] [Container] ceph-crash container services not getting upgraded to newer version
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Sunil Angadi <sangadi>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Sunil Angadi <sangadi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2CC: aschoen, ceph-eng-bugs, ealcaniz, fpantano, gabrioux, gmeno, knortema, nthomas, tserlin, vashastr, vereddy, ykaul
Target Milestone: ---   
Target Release: 4.2z1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.49.2-1.el8cp, ceph-ansible-4.0.49.2-1.el7cp Doc Type: Known Issue
Doc Text:
.The upgrade process does not automatically stop the `ceph-crash` container daemons. The upgrade process issues a call to the role `ceph-crash`, but the call only starts the `ceph-crash` service. If the `ceph-crash` container daemons are still running during the upgrade process, they will not be restarted when upgrade is complete. To work around this issue, manually restart the `ceph-crash` containers after upgrading.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-28 20:13:55 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: 1890121    

Comment 11 errata-xmlrpc 2021-04-28 20:13:55 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 (Important: Red Hat Ceph Storage security, bug fix, and enhancement Update), 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/RHSA-2021:1452