Bug 1216991
Summary: | Let external providers' VIF driver affect the state of a host | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> |
Component: | Frontend.WebAdmin | Assignee: | Marcin Mirecki <mmirecki> |
Status: | CLOSED WONTFIX | QA Contact: | Michael Burman <mburman> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | --- | CC: | bugs, danken, lsurette, mgoldboi, mmirecki, myakove, srevivo, ykaul, ylavi |
Target Milestone: | --- | Flags: | sbonazzo:
ovirt-4.3-
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-08-01 07:49:04 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: | |||
Bug Depends On: | 1061611, 1593804 | ||
Bug Blocks: | 1063716, 1314375 |
Description
Michael Burman
2015-04-29 11:26:57 UTC
Thank you Lior . Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. It would be best if Vdsm could issue Errors to Engine. Each error should have a UUID and textual explanation. With such a feature, Vdsm could report that the required packages are not installed. Engine would take the host to non-operations, and report the reason prominently in the event log. Engine would not attempt to use this host for starting VMs. Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. oVirt 4.0 beta has been released, moving to RC milestone. oVirt 4.0 beta has been released, moving to RC milestone. This specific error is not a vdsm, but a libvirt error, which vdsm just forwards. What we could do in this case, is to warn the user (before engine sends vm run request) that he is about to add an openstack neutron managed nic to a vm which runs on a host not provisioned with openstack. Would this be ok? host not provisioned with openstack mean that the host was added without 'External Network Provider' configuration? Now we add external network provider and run packstack installer to configure the hosts and not via add host > external network provider so how can you tell if my hosts have neutron installed or not? We can only tell is the host was installed with neutron during host installation. When this was not done, we could assume that there is no neutron on the host. If the user installs openstack on the host manually (or does not configure it properly), we have no way of telling this. ok by us. Our current focus for external network providers is *not* to be involved in the host installation. Vdsm nor Engine can tell whether a specific 3rd-party VIF driver is properly installed on the host. IF the VIF driver is properly installed, it could sense whether it is properly configured, and if it is not - make sure that the host is considered non-operational by Engine. Closing old issues, please reopen if still needed. In any case patches are welcome. |