Back to bug 1943471

Who When What Removed Added
Guillaume Abrioux 2021-03-26 09:20:31 UTC Status NEW ASSIGNED
Target Release 5.1 4.2z1
Guillaume Abrioux 2021-03-26 09:38:01 UTC Link ID Github ceph/ceph-ansible/pull/6392
Sunil Angadi 2021-03-26 10:55:47 UTC QA Contact amsyedha sangadi
Guillaume Abrioux 2021-03-29 08:32:15 UTC CC tserlin
Status ASSIGNED POST
Veera Raghava Reddy 2021-03-29 09:01:00 UTC CC vereddy
errata-xmlrpc 2021-03-30 04:44:49 UTC Status POST MODIFIED
Fixed In Version ceph-ansible-4.0.49.2-1.el8cp, ceph-ansible-4.0.49.2-1.el7cp
Status MODIFIED ON_QA
Sunil Angadi 2021-03-30 07:07:21 UTC Status ON_QA VERIFIED
CC gabrioux
Flags needinfo?(gabrioux)
Vasishta 2021-04-06 11:54:58 UTC CC vashastr
Doc Type If docs needed, set a value Known Issue
Guillaume Abrioux 2021-04-07 06:54:49 UTC Doc Text Cause: ceph-crash container daemons are not stopped before they are upgraded.

Consequence: the call to the role ceph-crash during the upgrade process only ensures the service is started, it means if the container wasn't stopped, the container isn't restarted.

Workaround (if any): Restart manually the ceph-crash containers.

Result: ceph-crash containers are well upgraded.
Flags needinfo?(gabrioux)
Karen Norteman 2021-04-07 13:24:01 UTC CC knortema
Doc Text Cause: ceph-crash container daemons are not stopped before they are upgraded.

Consequence: the call to the role ceph-crash during the upgrade process only ensures the service is started, it means if the container wasn't stopped, the container isn't restarted.

Workaround (if any): Restart manually the ceph-crash containers.

Result: ceph-crash containers are well upgraded.
. 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.
Flags needinfo?(gabrioux)
Karen Norteman 2021-04-07 13:24:47 UTC Flags needinfo?(sangadi)
Guillaume Abrioux 2021-04-07 15:46:15 UTC Flags needinfo?(gabrioux)
Karen Norteman 2021-04-07 15:54:45 UTC Flags needinfo?(sangadi)
Karen Norteman 2021-04-07 16:05:26 UTC 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.
.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.
Karen Norteman 2021-04-14 14:35:04 UTC Blocks 1890121
errata-xmlrpc 2021-04-28 16:44:19 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2021-04-28 20:13:55 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2021-04-28 20:13:55 UTC
errata-xmlrpc 2021-04-28 20:14:17 UTC Link ID Red Hat Product Errata RHSA-2021:1452
Francesco Pantano 2021-04-30 11:53:34 UTC CC fpantano
Flags needinfo?(gabrioux)
Edu Alcaniz 2021-05-05 19:46:36 UTC CC ealcaniz
Guillaume Abrioux 2021-05-27 07:00:32 UTC Flags needinfo?(gabrioux)
Amrita 2021-06-04 11:46:09 UTC Blocks 1890121
Aron Gunn 2021-06-09 16:16:59 UTC Blocks 1890121

Back to bug 1943471