| Summary: | New 'VM' network created without a vNIC profile | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||
| Component: | BLL.Network | Assignee: | Dominik Holler <dholler> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Meni Yakove <myakove> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.1.0 | CC: | bugs, mburman | ||||
| Target Milestone: | ovirt-4.1.0-alpha | Keywords: | Regression | ||||
| Target Release: | --- | Flags: | danken:
ovirt-4.1?
rule-engine: blocker? mburman: planning_ack? mburman: devel_ack? mburman: testing_ack? |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-07 08:26:30 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: | |||||
| Attachments: |
|
||||||
AddVnicProfileCommand isn't sent 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. Is the problems with the current master version of ovirt reproducible or already fixed? This report isn't reproducible any more on latest master - 4.1.0-0.0.master.20161105231320.git54b483a.el7.centos |
Created attachment 1208476 [details] engine log Description of problem: New 'VM' network created without a vNIC profile Version-Release number of selected component (if applicable): 4.1.0-0.0.master.20161008231308.git39b2133.el7.centos How reproducible: 100% if not pressing the 'vNIC Profiles' sub tab before approving operation Steps to Reproduce: 1. Create new network via 'Networks' main tab > give it a name and press 'OK' Actual results: VM network created without the vNIC profile. Expected results: Should work as expected. Additional info: Note that when creating the new network, giving it a name, pressing the 'vNIC Profiles' sub tab just before approving the operation, the vNIC profile is created.