Bug 580803 - Can not bring network interfaces up after it was down
Summary: Can not bring network interfaces up after it was down
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-09 05:41 UTC by Liam Li
Modified: 2010-08-21 21:33 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-21 21:33:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Liam Li 2010-04-09 05:41:27 UTC
Description of problem:
Interface management with virt-manager is mostly exposed via: Edit->Host Details->Network Interfaces. We will call this the 'interface viewer' ,Starting and stopping an existing interface: Select an interface from the interface viewer, use the start and stop button on the bottom list to bring interfaces up and down. but after the interface down, can not use "start poll" icon to bring it up. and when use ifup to bring network, the out put is:
[root@localhost ~]# ifup eth0
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.ifcfgrh1 was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.ifcfgrh1 was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.ifcfgrh1 was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.ifcfgrh1 was not provided by any .service files

but the network still did not been activated.

Version-Release number of selected component (if applicable):
    * kernel-2.6.33.1-19.fc13
    * libvirt-0.7.7-1.fc13
    * python-virtinst-0.500.2-3.fc13
    * qemu-0.12.3-6.fc13
    * seabios-0.5.1-1.fc13
    * virt-manager-0.8.3-2.fc13 

How reproducible:

always
  
Actual results:
the network should be start

Expected results:


Additional info:

Comment 1 Cole Robinson 2010-08-21 21:33:07 UTC
I think this is just fallout from doing network management with NetworkManager running. If you can reproduce with NetworkManager turned off, please reopen.


Note You need to log in before you can comment on or make changes to this bug.