Bug 1002849

Summary:	Connection to server with virtual machines created by virt-manager refused from time to time
Product:	[Fedora] Fedora	Reporter:	Milovidov Mikhail <milovidovwork>
Component:	bridge-utils	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	19	CC:	dwmw2, twoerner
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 16:59:09 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 Milovidov Mikhail 2013-08-30 06:19:05 UTC

Description of problem:
I have a bridge device for my network with virtual machines and I use network.service. From time to time the connection to my server where virtual machine located is refuse.

Version-Release number of selected component (if applicable):
kernel 3.10.9-200
avahi 0.6.31-11
bridge-utils 1.5-7
dhclient 12:4.2.5-15

How reproducible:
From time to time

Steps to Reproduce:
1. systemctl disable NetworkManager
systemctl stop NetworkManager

2. Create files.
/etc/sysconfig/network-scripts/ifcfg-eno1:

HWADDR=94:DE:80:60:98:F1
TYPE=Ethernet
DEVICE=eno1
ONBOOT=yes
BRIDGE=br0

/etc/sysconfig/network-scripts/ifcfg-br0:

TYPE=Bridge
BOOTPROTO=dhcp
DEVICE=br0
ONBOOT=yes

3. systemctl start network
systemctl enable netwrok
4. Add several virtuals with br0 network device in virt-manager.

Actual results:
br0 device from time to time not return ip4 address. See log:
"Aug 29 23:13:50 server avahi-daemon[514]: Withdrawing address record for 192.168.1.42 on br0.
Aug 29 23:13:50 server avahi-daemon[514]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.42.
Aug 29 23:13:50 server avahi-daemon[514]: Interface br0.IPv4 no longer relevant for mDNS."
Connection to server in this case where virtual machines located is refused.

Expected results:
Coneection to server with virtual machines must be normally.

Additional info:
After restart netwrok.service the connection to server normally again.
This bug very simular such as https://bugzilla.redhat.com/show_bug.cgi?id=755800

Comment 1 Fedora End Of Life 2015-01-09 19:39:10 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 16:59:09 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.