Bug 1801794
Summary: | 'active_slave' attribute is not reported for a newly created bond in mode 1 | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | msheena |
Component: | BLL.Network | Assignee: | Dominik Holler <dholler> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | msheena |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4.0 | CC: | aoconnor, bugs, dholler, eraviv, lsvaty, mburman |
Target Milestone: | ovirt-4.4.1 | Keywords: | Automation, AutomationBlocker, Regression |
Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
aoconnor: blocker+ |
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.40.15 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-08 08:25: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: | 1671876 | ||
Bug Blocks: |
Description
msheena
2020-02-11 16:11:59 UTC
Does refreshing the host capabilities manually solve the problem? If not, can you please attach the vdsm.log and supervdsm.log? Refreshing capabilities manually does solve this both for UI and REST API, however this does not sort out until a manual refresh is called. This is a regression. Always worked for newly bond mode 1. Doesn't reproduced with NM. I think this bug caused of the 2 seconds we added per transaction. Doesn't reproduced on other env This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. Targeting to 4.4.0 due to Regression keyword. Verified on - rhvm-4.4.1.1-0.5.el8ev.noarch with vdsm-4.40.18-1.el8ev.x86_64 nmstate-0.2.6-13.el8_2.noarch NetworkManager-1.22.8-4.el8.x86_64 This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |