Cluster job is in "Queued" state even after discovery of the node
pradvara opened this issue · 1 comments
The below node is discovered
vm15-VMware-56: Inventory State
vm15-VMware-56: name: vm15-VMware-56
vm15-VMware-56: prev_state: Unknown
vm15-VMware-56: prev_status: Incomplete
vm15-VMware-56: state: Discovered
vm15-VMware-56: status: Unallocated
vm15-VMware-56: Monitoring State
vm15-VMware-56: label: vm15
vm15-VMware-56: management_address: 10.106.240.67
vm15-VMware-56: serial_number: VMware-56
vm15-VMware-56: Configuration State
vm15-VMware-56: host_group: service-master
vm15-VMware-56: inventory_name: vm15-VMware-56
vm15-VMware-56: inventory_vars:
vm15-VMware-56: node_addr: 10.106.240.67
vm15-VMware-56: node_name: vm15-VMware-56
vm15-VMware-56: ssh_address: 10.106.240.67
But i see a active job running for this node
and due to this we are not able to create further jobs
[root@vm11 ~]# clusterctl job get active
Description: discoverEvent: addr: [10.106.240.67] extra-vars: {}
Status: Queued
Error:
Logs: