Red Hat Bugzilla – Bug 1596820
alerts "volume <volume name> is unknown" reported during unmanage of cluster which failed to import
Last modified: 2018-09-04 03:09:31 EDT
Description of problem ====================== During verifying BZ 1516135, I noticed that WA reports alerts "volume <volume name> is unknown" during unmanage of cluster which failed to import recently. Version-Release number of selected components ============================================= [root@mbukatov-usm1-server ~]# rpm -qa | grep tendrl | sort 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 How reproducible ================ 100% Steps to Reproduce ================== 1. prepare Gluster trusted storage pool and server for WA 2. install RHGS WA with tendrl-ansible 3. create a problem which makes import fail (break url of WA repo in /etc/yum.repos.d repofile) 4. run import (with profiling enabled) 5. wait for the import to fail 6. resolve the problem (introduced in the 1st step) 7. run unmanage Actual results ============== WA shows alert "warning: volume <volume name> is unknown" for each volume in the cluster (for which the import failed recently). See screenshot 1, the alerts are: * Volume:volume_gama_disperse_4_plus_2x2 is unknown * Volume:volume_beta_arbiter_2_plus_1x2 is unknown Expected results ================ There are no such alerts, or it's clear what such alerts mean and what to do about them. Additional Details ================== It could be related to the fact that right now, the unmanage fails.
Created attachment 1455549 [details] screenshot 1: alerts "volume is unknown" as shown in WA
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