Bug 1877426
Summary: | [16.1.0 -> 16.1.1] ceph update failing with "list object has no element 0\" | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Khomesh Thakre <kthakre> |
Component: | Ceph-Ansible | Assignee: | Dimitri Savineau <dsavinea> |
Status: | CLOSED ERRATA | QA Contact: | Ameena Suhani S H <amsyedha> |
Severity: | urgent | Docs Contact: | Aron Gunn <agunn> |
Priority: | unspecified | ||
Version: | 4.1 | CC: | agunn, aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, fpantano, gabrioux, gfidente, gmeno, johfulto, nchandek, nthomas, pasik, tchandra, tlapierr, tserlin, ykaul, yrabl |
Target Milestone: | z2 | Flags: | yrabl:
automate_bug-
|
Target Release: | 4.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-09-30 17:27:03 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: | 1760354, 1816167 |
Comment 18
errata-xmlrpc
2020-09-30 17:27:03 UTC
|