Bug 1573216
Summary: | non-VM network appears in the new vNIC profile drop down | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||
Component: | BLL.Network | Assignee: | Ales Musil <amusil> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.2.3.2 | CC: | bugs, danken, ylavi | ||||
Target Milestone: | ovirt-4.2.4 | Keywords: | Regression | ||||
Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
ylavi: blocker+ |
||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | ovirt-engine-4.2.4 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-06-26 08:44:25 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: | |||||||
Attachments: |
|
Description
Michael Burman
2018-04-30 14:02:11 UTC
Created attachment 1428837 [details]
record
Michael, can you tell which Engine version introduced this regression? Ales, could this be a very recent regression due removing OvS networks from this list? (In reply to Dan Kenigsberg from comment #2) > Michael, can you tell which Engine version introduced this regression? > > Ales, could this be a very recent regression due removing OvS networks from > this list? I think this bug is exist from the very beginning of the new UI re-design. Because on 4.1 and older versions we didn't had such option or flow. In the new UI in 4.2 we have a new vNIC profile tab and such flow is possible and it's why i think it don't a regression bug. I have missed this flow in 4.2 until now. BTW, what do you mean removing ovs networks from this list?(i'm not aware of this), how can you know if it's an ovs network?(because it's in an ovs cluster?) This is not affected by the auto-define. The auto-define is not yet in d/s build as well as auto-define did not touch this part of flow. I agree with Micheal that this is caused by the redesign. Verified on - 4.2.4-0.1.el7 This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 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. |