Bug 1401906
Summary: | Calamari saltstack dependency to be avoided | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Nishanth Thomas <nthomas> |
Component: | Calamari | Assignee: | Christina Meno <gmeno> |
Calamari sub component: | Back-end | QA Contact: | Harish NV Rao <hnallurv> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | ceph-eng-bugs, gmeno, hnallurv, vsarmila, vumrao |
Version: | 2.1 | ||
Target Milestone: | rc | ||
Target Release: | 2.2 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | RHEL: calamari-server-1.5.0-1.el7cp Ubuntu: calamari_1.5.0-2redhat1xenial | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-14 15:47:12 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: | 1406357 |
Description
Nishanth Thomas
2016-12-06 11:39:24 UTC
This should be pretty easy to revert given that it was a small changeset in 2.0 I'm testing the upstream packages now Harish 1. Salt should not be installed on fresh install of 2.2 2. Salt will not be removed during an update from 2.X to 2.2 3. Salt will not be removed during an upgrade from 1.3.x to 2.2 (In reply to Gregory Meno from comment #10) > Harish > > 1. Salt should not be installed on fresh install of 2.2 > 2. Salt will not be removed during an update from 2.X to 2.2 > 3. Salt will not be removed during an upgrade from 1.3.x to 2.2 @Gregory, in cases 2 and 3, how do i make sure that 2.2 is still not using salt? Please let me know. on every node in the cluster this command should return no results: sudo salt-call --local pillar.items | grep ceph.heartbeat # verify it is gone *** Bug 1416923 has been marked as a duplicate of this bug. *** 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, 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://rhn.redhat.com/errata/RHBA-2017-0514.html |