RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 984026 - lxc container with networking hangs udevadm settle on the host
Summary: lxc container with networking hangs udevadm settle on the host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-12 14:47 UTC by Daniel Berrangé
Modified: 2016-04-26 16:27 UTC (History)
23 users (show)

Fixed In Version: systemd-219-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 983685
Environment:
Last Closed: 2015-11-19 14:54:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2092 0 normal SHIPPED_LIVE systemd bug fix and enhancement update 2015-11-19 12:13:57 UTC

Description Daniel Berrangé 2013-07-12 14:47:15 UTC 
+++ This bug was initially created as a clone of Bug #983685 +++

If I start a simple bash container with networking, udevadm settle proceeds to hang on the host. This affects other libvirt functions like storage pool listing. If I remove the <interface> XML, settle doesn't hang.

Any recommendations on getting more info is appreciated.


I have this container:

<domain type='lxc'>
  <name>bash</name>
  <uuid>f1a972fc-eefd-4ca2-cc4b-b769cd25cadc</uuid>
  <memory unit='KiB'>65536</memory>
  <currentMemory unit='KiB'>61440</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64'>exe</type>
    <init>/bin/sh</init>
  </os>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/libexec/libvirt_lxc</emulator>
    <interface type='network'>
      <mac address='00:16:3e:ab:9a:cd'/>
      <source network='default'/>
    </interface>
    <console type='pty'>
      <target type='lxc' port='0'/>
    </console>
  </devices>
</domain>


Default network XML is:

<network>
  <name>default</name>
  <uuid>ff473bff-797f-41dd-b3df-f5a67b0a5f20</uuid>
  <forward mode='nat'>
    <nat>
      <port start='1024' end='65535'/>
    </nat>
  </forward>
  <bridge name='virbr0' stp='on' delay='0' />
  <mac address='52:54:00:d1:52:aa'/>
  <ip address='192.168.123.1' netmask='255.255.255.0'>
    <tftp root='/var/lib/tftpboot' />
    <dhcp>
      <range start='192.168.123.2' end='192.168.123.254' />
      <bootp file='pxelinux.0' />
    </dhcp>
  </ip>
</network>



To test, dump the first XML to file, sudo virsh --connect lxc:/// define <vmxml>, sudo virsh --connect lxc:/// start bash, udevadm settle on host.udev

--- Additional comment from Daniel Berrange on 2013-07-12 10:17:20 BST ---

I've seen this before too, but never managed to get to the bottom of it. Will look again & ask systemd folks for opinions.

--- Additional comment from Daniel Berrange on 2013-07-12 14:52:04 BST ---

http://lists.freedesktop.org/archives/systemd-devel/2013-July/011826.html
Comment 2 Kay Sievers 2013-11-19 15:55:08 UTC 
It's a pretty nasty kernel issue with network namespaces, or a non-trivial
problem to work around in userspace:
  http://lists.freedesktop.org/archives/systemd-devel/2013-July/011836.html
Comment 3 RHEL Program Management 2014-03-24 05:51:18 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 Lukáš Nykrýn 2015-05-29 11:18:33 UTC 
Fixed in 212, see the fedora bug.
Comment 8 errata-xmlrpc 2015-11-19 14:54:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2092.html
Note You need to log in before you can comment on or make changes to this bug.