Bug 1381752

Summary:	libvirt-daemon-config-network isn't installed by default or a dependency in F24
Product:	[Fedora] Fedora	Reporter:	daniel-wtd <daniel>
Component:	gnome-boxes	Assignee:	Christophe Fergeau <cfergeau>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	cfergeau, fidencio, gnome-sig, marcandre.lureau, mbriza, virt-maint, zeeshanak
Target Milestone:	---
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-11-08 11:44:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description daniel-wtd 2016-10-04 22:23:15 UTC

Description of problem:
Since F24, I am facing the situation, that gnome-boxes is installed without libvirt-daemon-config-network as dependency. For me it was quite troublesome to find out, how to enable the NAT-behaviour from F23.

In F23 I was used to have NAT enabled by default. Since F24 it seems to be user interface type, only. This hinders ssh and other connections into the VM.

Version-Release number of selected component (if applicable): 
gnome-boxes-3.20.2-4.fc24.x86_64
libvirt-daemon-config-network-1.3.3.2-1.fc24.x86_64

How reproducible:

Steps to Reproduce:
1. Install a fresh F24
2. Buildup a new VM (maybe centOS).
3. Try to connect to the machine via ssh (some 10.x.y.z ip).
--> does not work
3a. Try to ping outside the vm to maybe redhat.com
--> does not work
4. Install libvirt-daemon-config-network
5. Build a new VM (maybe centOS again)
6. Connect to the VM with its IP (some 192.168.122.z ip)
--> works
6a. Ping outside the VM (maybe redhat.com again)
-> works

Actual results:
-see reproduce Step 3 and 3a-

Expected results:
-see reproduce Step 6 and 6a-

Additional info:

Comment 1 Martin Bříza 2016-11-08 11:44:40 UTC

This is actually fixed now in recent builds, #1081762 is mentioned in the comment in the spec file.