Bug 988453
| Summary: | can't add host to engine when all hosts in cluster are in Install Failed state | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Mike Burns <mburns> | ||||||
| Component: | ovirt-engine-core | Assignee: | Aravinda VK <avishwan> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 3.3 | CC: | acathrow, alonbl, bazulay, dougsland, iheim, mburns, sabose, yeylon | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.3 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | gluster | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-09-23 07:34:19 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Mike Burns
2013-07-25 15:53:04 UTC
Yair? mburns, engine log would be great. Created attachment 778355 [details]
engine log
disregard that log... Created attachment 778370 [details]
engine log
last error in this log should be the relevant error.
Situation:
1 host in Default cluster in non-operational state
add second host to the Default cluster
UI error: Error while executing action: Cannot add Host. There is no available server in the cluster to probe the new server.
this is a gluster error: ACTION_TYPE_FAILED_NO_GLUSTER_HOST_TO_PEER_PROBE mike - is it a gluster cluster? (In reply to Itamar Heim from comment #6) > this is a gluster error: ACTION_TYPE_FAILED_NO_GLUSTER_HOST_TO_PEER_PROBE > mike - is it a gluster cluster? It's the default cluster, which happens to have both gluster and virt checked by default, so yes. sahina - should the default cluster have gluster enabled by default? (in any case, sounds like the check if host is first in cluster is tricky if there are hosts in the cluster by they are not working properly...) It's enabled by default when Application mode is Both. Probably not required to be enabled by default. When we add a host to a cluster, and there are already hosts in the cluster, we need to add the new host as a peer in the underlying storage cluster. So any one UP server is required to do this. If all hosts are in failed state, and we allow the host to be added to the cluster, it means the newly added host is not really part of the underlying storage cluster. We could possibly try to add as gluster peer whenever the other hosts in the cluster come up. But then, there are other validations - If the host that comes up is part of another cluster, we do not support merging of clusters. - This becomes a problem when there are multiple hosts that are not working properly in the cluster and we try to add a new host. I agree caution may be prudent when you know it is a gluster cluster (and if there are old, non operational hosts in the cluster, you may want to ask the user if this is about initializing a new gluster cluster or joining the existing one...) but i think the default cluster should be virt only for application mode which isn't gluster only? Yes. We can change the default cluster to virt only unless application mode is gluster only. Aravinda, can you change the installer to do this? as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this) closing as this should be in 3.3 (doing so in bulk, so may be incorrect) |