Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1362353

Summary: Add bond+vlan network failed via cockpit
Product: [oVirt] ovirt-node Reporter: Huijuan Zhao <huzhao>
Component: UIAssignee: Anatoly Litovsky <tlitovsk>
Status: CLOSED DUPLICATE QA Contact: Huijuan Zhao <huzhao>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.0CC: bugs, cshao, dguo, dperpeet, fdeutsch, gklein, leiwang, rbarry, tlitovsk, weiwang, yaniwang, ycui, ykaul, yzhao
Target Milestone: ovirt-4.0.4Flags: fdeutsch: ovirt-4.0.z?
rule-engine: planning_ack?
fdeutsch: devel_ack+
cshao: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-19 10:24:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of error report in cockpit
none
All logs
none
All ifcfg files in /etc/sysconfig/network-scripts/
none
kickstart file none

Description Huijuan Zhao 2016-08-02 03:24:38 UTC
Created attachment 1186637 [details]
screenshot of error report in cockpit

Description of problem:
Report "Unexpected error" when create bond.vlan network in cockpit

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160727.1.x86_64
imgbased-0.7.3-0.1.el7ev.noarch
cockpit-0.114-2.el7.x86_64
cockpit-ovirt-dashboard-0.10.6-1.3.3.el7ev.noarch
libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64
glib-networking-2.42.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install redhat-virtualization-host-4.0-20160727.1.x86_64 with kickstart file in attachment
2. Login RHVH via cockpit, change to Networking page
3. Add bond1 (Active-backup mode) on two NICs
4. Add vlan on bond1 -> bond1.20
5. Enter bond1.20, click "on"


Actual results:
1. After step5, there is error report:
Unexpected error
failed to determine virtual interface name

Expected results:
1. After step5, should enable bond1.20 successful without error.


Additional info:
No such issue with NIC.vlan

Comment 1 Huijuan Zhao 2016-08-02 03:26:24 UTC
Created attachment 1186640 [details]
All logs

Comment 2 Huijuan Zhao 2016-08-02 03:27:29 UTC
Created attachment 1186641 [details]
All ifcfg files in /etc/sysconfig/network-scripts/

Comment 3 Huijuan Zhao 2016-08-02 03:27:57 UTC
Created attachment 1186642 [details]
kickstart file

Comment 4 Fabian Deutsch 2016-08-11 19:16:02 UTC
Is this teh same issue as in the other bug?

Comment 5 Fabian Deutsch 2016-08-19 10:24:02 UTC

*** This bug has been marked as a duplicate of bug 1367378 ***

Comment 7 Red Hat Bugzilla 2023-09-14 03:29:03 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days