FS#47328 - [netcf] Missing ifup

Attached to Project: Community Packages
Opened by Nils Bars (noEntry) - Friday, 11 December 2015, 01:20 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 17:54 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Name libvirt
Version 1.3.0-1

If I am creating a bridge with virt-manager I get an error that the file "/etc/sysconfig/network-scripts/ifcfg-br1" does not exists.
If I create the directory "/etc/sysconfig/network-scripts" it work just fine. But if I try to start the bridge I get the following
error message:

###############################
error starting interface 'br1': internal error: failed to create (start) interface br1: failed to execute external program - Running 'ifup enp5s0' program not found

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 90, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 126, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/interface.py", line 68, in start
self._backend.create(0)
File "/usr/lib/python2.7/site-packages/libvirt.py", line 3060, in create
if ret == -1: raise libvirtError ('virInterfaceCreate() failed', net=self)
libvirtError: internal error: failed to create (start) interface br1: failed to execute external program - Running 'ifup enp5s0' program not found
###############################
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 10 March 2016, 17:54 GMT
Reason for closing:  Won't implement
Comment by Nils Bars (noEntry) - Friday, 11 December 2015, 10:36 GMT
Skip
Comment by Sergej Pupykin (sergej) - Thursday, 04 February 2016, 16:05 GMT
I think this is netcf issue. Probably you should manually configure the bridge by systemd-networkd/netctl/etc.
Comment by Sergej Pupykin (sergej) - Thursday, 04 February 2016, 16:10 GMT
netcf sources have just:
drv_debian.c
drv_mswindows.c
drv_redhat.c
drv_suse.c
Comment by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 17:54 GMT
As I understand in case of missing distro support you need to create bridge manually and point it to netcf

Loading...