Description of problem:
If a SD in a cluster is marked inactive, and a new hypervisor tries to activate, the hypervisor will fall into an "unassigned" state and then timeout to non-operational. From the attached case, we could see that the host initiated an attempt to connect to the SD, but would never have a FINISH log entry nor fail out as it would if the IP for the SD was up but the LUN was missing.
Version-Release number of selected component (if applicable):
Was 100% for us
Steps to Reproduce:
1. Bring down a SD and mark inactive
2. Take the IP for said SD offline
3. Try to activate a hypervisor
Hypervisor will go into an "Unassigned" state and then take ~10 minutes to fall into non-operational.
Since the hypervisor will come Up if the IP is reachable but the LUN is missing, so to should the hypervisor come Up if the IP is unreachable for an INactive SD
Tal please check if it should be still the case for 3.3
this should be currently resolved. failing to connect to one of the sds shouldn't fail host activation.
Got the Expected results
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.