Description of problem: If Cluster import fails or an existing cluster need to be expanded with additional hosts, current procedure results in removal of all the managed clusters. Expected results: This procedure should remove only the affected cluster
This is basically RFE BZ for unmanage feature, as described in upstream here: https://github.com/Tendrl/specifications/pull/255 Correct?
yes
BZ 1564107 already verified
Basic workflow for unmanaging cluster works. It works for positive testcases and also for unmanage after failure of import (BZ 1570048, BZ 1564107). When the cluster is unmanaged, all other clusters remain as managed if they are already managed. --> VERIFIED Tested with: tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-7.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-5.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-5.el7rhgs.noarch tendrl-node-agent-1.6.3-7.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-4.el7rhgs.noarch
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://access.redhat.com/errata/RHSA-2018:2616