Bug 818089
Summary: | VMs fail to start in case ovirtmgmt bridge doesn't have a link | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Rami Vaknin <rvaknin> | ||||||||||||
Component: | ovirt-engine-core | Assignee: | Nobody's working on this, feel free to take it <nobody> | ||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Meni Yakove <myakove> | ||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | unspecified | CC: | abaron, acathrow, bazulay, iheim, jkt, mgoldboi, mlipchuk, mpavlik, 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: | 2013-12-01 09:10:22 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
Rami Vaknin
2012-05-02 08:12:53 UTC
the main issue here is that the host will move in to non-op state once the link is down. when working with all in one setup local host + local storage we do not have the obligation to have an active link in the host. (In reply to comment #0) > VDSM logs will be attached later on (in case they won't be override until I > get them). They haven't been... (In reply to comment #1) > the main issue here is that the host will move in to non-op state once the > link is down. > > when working with all in one setup local host + local storage we do not have > the obligation to have an active link in the host. If this is the case, it is not a Vdsm bug, but an Engine one. As a workaround, in current upstream Engine, you can define the network as non-required, and set the news OnlyRequiredNetworksMandatoryForVdsSelection=True Is this still an issue? I see the reporter did not replied since May. Any idea how we can get this issue forward or close it? myakove, could you please help with the needinfo? It seems that this bug requires some attention at least in AIO setup I installed AIO setup via yum install ovirt-engine-setup-plugin-allinone version: oVirt Engine Version: 3.3.0-0.2.master.20130401204125.gita95f899.fc18 I did ifdown ovirtmgmt && ifdown em1 (underlying interface for ovirtmgmt) than I connected via another IP to engine GUI (via em2) shutting down ovirtmgmt resulted in Non Responsive status of local_host (see screenshot 1) which put data-center in non-responsive status so no VM can be started it seems that there was a problem with connecting to API ERROR: _get_hypervisors_from_api: [ERROR]::oVirt API connection failure, [Errno 110] Connection timed out attahced: engine.log vdsm.log partial log_collector Created attachment 730789 [details]
screenshot 1
Created attachment 730793 [details]
engine.log
Created attachment 730794 [details]
engine.log
Created attachment 730798 [details]
vdsm.log
Created attachment 730806 [details]
log_collector
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. |