Bug 1445171
Summary: | MultiHost command is not sent when updating network with default route role | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> |
Component: | BLL.Network | Assignee: | Martin Mucha <mmucha> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | future | CC: | bugs, danken |
Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: when using UI to alter defaultroute network role it only passes request to update network gaining role, but does not pass request to update network losing role.
Consequence: engine does not pass request to vdsm to remove role from network, which to this moment had defaultrote role passing only new netwrok acquiring this role, and vdsm fails, because only one network can have this role.
Fix: issue was fixed in HostSetupNetworksCommand by examining current host setting. If role removal is missing among commands, given request is added.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-20 11:41:44 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: | 1443292 | ||
Bug Blocks: | 1200963 |
Description
Michael Burman
2017-04-25 07:45:22 UTC
FailedQA. Tested on 4.2.0-0.0.master.20170721095131.git9f5e90c.el7.centos and vdsm-4.20.1-218.git1b7671f.el7.centos.x86_64 Can't attach non-mgmt network to host with default route role. This bug depends on BZ 1443292, with out it this can't be tested at all. Verified on - 4.2.0-0.0.master.20170917124606.gita804ef7.el7.centos This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |