Bug 1485927
| Summary: | Default vNIC profile not created if new network dialog is confirmed with keyboard Enter(works via Ok button click) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||
| Component: | BLL.Network | Assignee: | Ales Musil <amusil> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.2.0 | CC: | bugs, danken, lgoldber, vszocs | ||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | http://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ovirt-engine-4.2.0-0.0.master.20171019181349.gite12eda4.el7.centos.noarch.rpm | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-20 11:29:39 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: |
|
||||||
Per our test today, this bug manifests itself on ovirt-4.1.3, too. Hence, it should not block long names. The bug should be fixed for 4.1 as well. As far as I understand, this is a very old bug. Lacking customer complaint and a solution for 4.2, it is unlikely that we backport to 4.1. The patch [1] fixes the problem for all dialogs, not only the New Network one. [1] https://gerrit.ovirt.org/#/c/82944/ Verified on - 4.2.0-0.0.master.20171022103432.gitaf9d8b6.el7.centos Note that i'm verifying only the new network scenario. If additional verification is needed(for all dialogs) please move to the appropriate team. 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. |
Created attachment 1319073 [details] engine log Description of problem: Sometimes vNIC profile doesn't created on new network creation. When creating new network, sometimes the vNIC profile doesn't created. Possible caused by changes done for the long name. There is no call for create vNIC profile in the logs. Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170827084901.git3fdb878.el7.centos How reproducible: 80% Steps to Reproduce: 1. Create network called - net-1 , net-2 Actual results: No vNIC profile Expected results: Should work as expected