Bug 1122943
Summary: | host is up even if it's missing required network. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Mucha <mmucha> |
Component: | ovirt-engine | Assignee: | Nobody <nobody> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.0 | CC: | acathrow, ecohen, gklein, iheim, lpeer, lvernia, oourfali, Rhev-m-bugs, yeylon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | network | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-30 11:41:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Mucha
2014-07-24 12:57:00 UTC
This sounds like correct behavior - once the network is detached from the cluster and then re-attached, it is principally a new network. A new network, even if it's required, will not render hosts non-operational - instead the network itself will appear as non-operational (red down arrow) until it's configured on all active hosts. Only from that point on specific hosts will move to non-operational state if the network is missing on them. |