Re: network not coming up on 20161011 FAH
On Fri, Oct 14, 2016, at 05:21 PM, Colin Walters wrote: > On Tue, Oct 11, 2016, at 06:00 PM, Dusty Mabe wrote: > > > running dhclient on ens2 gives me an IP address.. race condition? > > This was debugged to be: > https://bugzilla.redhat.com/show_bug.cgi?id=1385172 > and should be fixed by: > https://bodhi.fedoraproject.org/updates/FEDORA-2016-e96b704c39 ...which is waiting for 1 more karma. ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: network not coming up on 20161011 FAH
On Tue, Oct 11, 2016, at 06:00 PM, Dusty Mabe wrote: > running dhclient on ens2 gives me an IP address.. race condition? This was debugged to be: https://bugzilla.redhat.com/show_bug.cgi?id=1385172 and should be fixed by: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e96b704c39 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: network not coming up on 20161011 FAH
On Tue, Oct 11, 2016, at 06:12 PM, Jason Brooks wrote: > Also, this "Warning: NetworkManager.service changed on disk. Run > 'systemctl daemon-reload'" message when I check the status of > NetworkManager. Let's track this one as https://bugzilla.redhat.com/show_bug.cgi?id=1384150 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: network not coming up on 20161011 FAH
On Tue, Oct 11, 2016, at 06:12 PM, Jason Brooks wrote: > I'm seeing an selinux denial preventing resolv.conf from being updated: > > Oct 11 22:05:46 atomic01.example.org audit[1304]: AVC avc: denied { > write } for pid=1304 comm="dhclient-script" name="NetworkManager" > dev="tmpfs" ino=22077 > scontext=unconfined_u:system_r:dhcpc_t:s0-s0:c0.c1023 > tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=dir > permissive=0 There's an upstream discussion related to this: https://mail.gnome.org/archives/networkmanager-list/2016-September/msg00039.html Which, if you see my reply, I think his patch is wrong, but the fix should likely live in NM. Also, way back in the past... http://www.spinics.net/linux/fedora/fedora-cloud/msg06264.html which again seems to have been lost because I didn't commit it to the master branch =( Also: https://bugzilla.redhat.com/show_bug.cgi?id=1204226 But hey, let's make another try at this, and we actually want this to apply on bare metal too, so: https://pagure.io/fedora-atomic/pull-request/23 That said...I'm not reproducing this here, /run/NetworkManager/resolv.conf seems to be correctly labeled net_conf_t here. > Also, this "Warning: NetworkManager.service changed on disk. Run > 'systemctl daemon-reload'" message when I check the status of > NetworkManager. I suspect systemd needs the same "handle zero mtime" fix as I did for gnutls. ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Re: network not coming up on 20161011 FAH
On Tue, Oct 11, 2016 at 3:00 PM, Dusty Mabe wrote: > > > https://kojipkgs.fedoraproject.org//work/tasks/3677/16053677/Fedora-Cloud-Base-25-20161011.n.0.x86_64.qcow2 > > > seen on local kvm as well as on openstack newton: > > Cloud-init v. 0.7.7 running 'init' at Tue, 11 Oct 2016 21:45:39 +. Up > 7.01 s > ci-info: +++Net device > info > ci-info: > ++---+---+---+---+---+ > ci-info: | Device | Up | Address |Mask | Scope | Hw-Address > | > ci-info: > ++---+---+---+---+---+ > ci-info: | ens2: | False | . | . | . | 52:54:00:3e:f7:e3 > | > ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | . > | > ci-info: | lo: | True | . | . | d | . > | > ci-info: > ++---+---+---+---+---+ > > > running dhclient on ens2 gives me an IP address.. race condition? I'm seeing an selinux denial preventing resolv.conf from being updated: Oct 11 22:05:46 atomic01.example.org audit[1304]: AVC avc: denied { write } for pid=1304 comm="dhclient-script" name="NetworkManager" dev="tmpfs" ino=22077 scontext=unconfined_u:system_r:dhcpc_t:s0-s0:c0.c1023 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=dir permissive=0 Also, this "Warning: NetworkManager.service changed on disk. Run 'systemctl daemon-reload'" message when I check the status of NetworkManager. > > Dusty > ___ > cloud mailing list -- cloud@lists.fedoraproject.org > To unsubscribe send an email to cloud-le...@lists.fedoraproject.org ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
network not coming up on 20161011 FAH
https://kojipkgs.fedoraproject.org//work/tasks/3677/16053677/Fedora-Cloud-Base-25-20161011.n.0.x86_64.qcow2 seen on local kvm as well as on openstack newton: Cloud-init v. 0.7.7 running 'init' at Tue, 11 Oct 2016 21:45:39 +. Up 7.01 s ci-info: +++Net device info ci-info: ++---+---+---+---+---+ ci-info: | Device | Up | Address |Mask | Scope | Hw-Address| ci-info: ++---+---+---+---+---+ ci-info: | ens2: | False | . | . | . | 52:54:00:3e:f7:e3 | ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | . | ci-info: | lo: | True | . | . | d | . | ci-info: ++---+---+---+---+---+ running dhclient on ens2 gives me an IP address.. race condition? Dusty ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org