-
Bug
-
Resolution: Done-Errata
-
Minor
-
None
-
premerge
-
None
-
False
-
Description of problem:
issue is found when testing PR: https://github.com/openshift/cluster-monitoring-operator/pull/1879, launched cluster-bot cluster
launch openshift/cluster-monitoring-operator#1879
nodes
$ oc get node NAME STATUS ROLES AGE VERSION ip-10-0-145-183.us-west-1.compute.internal Ready control-plane,master 113m v1.26.0+9eb81c2 ip-10-0-149-39.us-west-1.compute.internal Ready control-plane,master 113m v1.26.0+9eb81c2 ip-10-0-208-83.us-west-1.compute.internal Ready control-plane,master 113m v1.26.0+9eb81c2 ip-10-0-141-10.us-west-1.compute.internal Ready worker 20m v1.26.0+9eb81c2 ip-10-0-153-46.us-west-1.compute.internal Ready worker 20m v1.26.0+9eb81c2 ip-10-0-219-5.us-west-1.compute.internal Ready worker 106m v1.26.0+9eb81c2
admin console, go to "Node Exporter / USE Method / Node" dashboard, choose "master" from "Role" drop-down list, the Instance filed selects only the master nodes
ip-10-0-145-183.us-west-1.compute.internal ip-10-0-149-39.us-west-1.compute.internal ip-10-0-208-83.us-west-1.compute.internal
choose "worker" from "Role" drop-down list, Instance filed still select the master nodes at the first, if we click the Instance drop-down list again, it changes to the worker nodes, see from the attached .gif picture
ip-10-0-141-10.us-west-1.compute.internal ip-10-0-153-46.us-west-1.compute.internal ip-10-0-219-5.us-west-1.compute.internal
this is a low priority bug, same issue with "Kubernetes / Compute Resources / Node (Pods) " dashboard
Version-Release number of selected component (if applicable):
launch openshift/cluster-monitoring-operator#1879
How reproducible:
always
Steps to Reproduce:
1. see the description 2. 3.
Actual results:
Instance/Node values are not changed timely when Role value changed
Expected results:
Instance/Node values should be changed timely when Role value changed
Additional info:
