Bug 1877426 - [16.1.0 -> 16.1.1] ceph update failing with "list object has no element 0\"
Summary: [16.1.0 -> 16.1.1] ceph update failing with "list object has no element 0\"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: z2
: 4.1
Assignee: Dimitri Savineau
QA Contact: Ameena Suhani S H
Aron Gunn
URL:
Whiteboard:
Depends On:
Blocks: 1760354 1816167
TreeView+ depends on / blocked
 
Reported: 2020-09-09 15:23 UTC by Khomesh Thakre
Modified: 2023-12-15 19:15 UTC (History)
18 users (show)

Fixed In Version: ceph-ansible-4.0.31-1.el8cp, ceph-ansible-4.0.31-1.el7cp
Doc Type: Bug Fix
Doc Text:
.Running the `rolling_update.yml` playbook does not retrieve the storage cluster `fsid` When running the `rolling_update.yml` playbook, and the Ceph Ansible inventory does not have Ceph Monitor nodes defined, for example, in an external scenario, the storage cluster `fsid` is not retrieved. This causes the `rolling_update.yml` playbook to fail. With this release, the `fsid` retrieval is skipped when there are no Ceph Monitors defined in the inventory, allowing the `rolling_update.yml` playbook to execute when no Ceph Monitors are present.
Clone Of:
Environment:
Last Closed: 2020-09-30 17:27:03 UTC
Embargoed:
yrabl: automate_bug-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 5755 0 None closed ceph-facts: only get fsid when monitor are present 2020-11-03 15:50:51 UTC
Github ceph ceph-ansible pull 5756 0 None closed ceph-facts: only get fsid when monitor are present (bp #5755) 2020-11-03 15:50:33 UTC
Github ceph ceph-ansible pull 5757 0 None closed ceph-facts: only get fsid when monitor are present (bp #5755) 2020-11-03 15:50:34 UTC
Red Hat Product Errata RHBA-2020:4144 0 None None None 2020-09-30 17:27:15 UTC

Comment 18 errata-xmlrpc 2020-09-30 17:27:03 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 (Red Hat Ceph Storage 4.1 Bug Fix 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/RHBA-2020:4144
Note You need to log in before you can comment on or make changes to this bug.