Bug 2062147
| Summary: | Under disconnected network env, upgrading RHCS4 to RHCS5 failed due to ceph-ansible-6.0.20-2.1 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Hideshi Fukumoto <hfukumot> |
| Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> |
| Status: | CLOSED ERRATA | QA Contact: | Ameena Suhani S H <amsyedha> |
| Severity: | high | Docs Contact: | Mary Frances Hull <mhull> |
| Priority: | unspecified | ||
| Version: | 5.0 | CC: | aschoen, ceph-eng-bugs, ceph-qe-bugs, gabrioux, gjose, gmeno, gsitlani, mhull, mmuench, mobisht, msaini, nthomas, rmandyam, tsaito, tserlin, vereddy, ykaul |
| Target Milestone: | --- | ||
| Target Release: | 5.1z1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-6.0.25.5-1.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.The `ceph-ansible` playbook does not fail during the upgrade in a disconnected environment
Previously, with the removal of ISO installation method, `ceph-ansible` would not detect if the user deployed the cluster in a disconnected environment resulting in failure of the upgrade from {storage-product} 4 to {storage-product} 5.
With this fix, the check is dropped and the playbook does not fail anymore.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-18 10:38:15 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: | 2085458 | ||
|
Comment 4
Yaniv Kaul
2022-03-22 07:50:02 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 5.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-2022:4622 |