Created attachment 982676[details]
log collector
Description of problem:
RHEV-H host, which is added and approved, removed and re-added without approval, is counted as part of cluster, for power management test.
Version-Release number of selected component (if applicable):
3.5.0-0.30.el6ev
How reproducible:
100%
Steps to Reproduce:
1. Add 1st rhev-h to rhevm, approve it
2. Remove it
3. Add 1st and any 2nd host to rhevm, do not approve
4. Approve 2nd host, setup power management, confirm it
5. 1st host is used as proxy host for fencing test of 2nd host, even if it is not approved itself.
Actual results:
Re-added not re-approved rhev-h node is token as known for PM result
Expected results:
Removed rhev-h node, should be fully removed from all config, it should be not known during re-adding on any level of rhevm.
Additional info: 1st host = slot-6c.rhev.lab.eng.brq.redhat.com; 2nd = dell-r210ii-16.rhev.lab.eng.brq.redhat.com
Part of engine log:
2015-01-22 10:36:10,691 INFO [org.ovirt.engine.core.bll.FenceExecutor] (DefaultQuartzScheduler_Worker-96) [641c7bab] Executing <Status> Power Management command, Proxy Host:slot-6c.rhev.lab.eng.brq.redhat.com, Agent:ipmilan, Target Host:dell-r210ii-16.rhev.lab.eng.brq.redhat.com, Management IP:10.34.62.158, User:root, Options:, Fencing policy:null
2015-01-22 10:36:10,692 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (DefaultQuartzScheduler_Worker-96) [641c7bab] START, FenceVdsVDSCommand(HostName = slot-6c.rhev.lab.eng.brq.redhat.com, HostId = fa86d73e-2e67-45ce-9b43-d8c3cd199d55, targetVdsId = fc007758-364c-4024-8554-e6ef61ce364e, action = Status, ip = 10.34.62.158, port = , type = ipmilan, user = root, password = ******, options = '', policy = 'null'), log id: 735f214d
IMO , this is a duplicate of 1184781
the host used here is not a removed one , since you had re-added it again , so , I see no diff between this BZ and 1184781
Please give a reason why this should not be closed as DUPLICATE
Thanks
Created attachment 982676 [details] log collector Description of problem: RHEV-H host, which is added and approved, removed and re-added without approval, is counted as part of cluster, for power management test. Version-Release number of selected component (if applicable): 3.5.0-0.30.el6ev How reproducible: 100% Steps to Reproduce: 1. Add 1st rhev-h to rhevm, approve it 2. Remove it 3. Add 1st and any 2nd host to rhevm, do not approve 4. Approve 2nd host, setup power management, confirm it 5. 1st host is used as proxy host for fencing test of 2nd host, even if it is not approved itself. Actual results: Re-added not re-approved rhev-h node is token as known for PM result Expected results: Removed rhev-h node, should be fully removed from all config, it should be not known during re-adding on any level of rhevm. Additional info: 1st host = slot-6c.rhev.lab.eng.brq.redhat.com; 2nd = dell-r210ii-16.rhev.lab.eng.brq.redhat.com Part of engine log: 2015-01-22 10:36:10,691 INFO [org.ovirt.engine.core.bll.FenceExecutor] (DefaultQuartzScheduler_Worker-96) [641c7bab] Executing <Status> Power Management command, Proxy Host:slot-6c.rhev.lab.eng.brq.redhat.com, Agent:ipmilan, Target Host:dell-r210ii-16.rhev.lab.eng.brq.redhat.com, Management IP:10.34.62.158, User:root, Options:, Fencing policy:null 2015-01-22 10:36:10,692 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (DefaultQuartzScheduler_Worker-96) [641c7bab] START, FenceVdsVDSCommand(HostName = slot-6c.rhev.lab.eng.brq.redhat.com, HostId = fa86d73e-2e67-45ce-9b43-d8c3cd199d55, targetVdsId = fc007758-364c-4024-8554-e6ef61ce364e, action = Status, ip = 10.34.62.158, port = , type = ipmilan, user = root, password = ******, options = '', policy = 'null'), log id: 735f214d