+++ This bug was initially created as a clone of Bug #1055226 +++ I've edited out the selinux parts of the above problem report since they didn't seem to effect the observed failures. The selinux problem have been fixed, but the ipv6 problems remain, hence the cloned bug report. Description of problem: There appears to be an older dhclient6 started at boot time and dhclient6 can't get access to the port it needs leading to a failure to get an ipv6 address assigned. Version-Release number of selected component (if applicable): NetworkManager.x86_64 1:0.9.9.0-25.git20131003.fc20 @updates-testing dhclient.x86_64 12:4.2.5-26.fc20 @koji-override-0/$releasever How reproducible: always Steps to Reproduce: 1. reboot a machine that uses dhclient6 and networkmanager to get an ipv6 address 2. ifconfig 3. notice no ipv6 address Actual results: no ipv6 address Expected results: an ipv6 address Additional info: Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: Internet Systems Consortium DHCP Client 4.2.5 Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: Copyright 2004-2013 Internet Systems Consortium. Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: All rights reserved. Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: For info, please visit https://www.isc.org/software/dhcp/ Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: <info> (p32p1): DHCPv4 state changed nbi -> preinit Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: Internet Systems Consortium DHCP Client 4.2.5 Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: Copyright 2004-2013 Internet Systems Consortium. Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: All rights reserved. Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: For info, please visit https://www.isc.org/software/dhcp/ Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: <info> (p32p1): DHCPv6 state changed nbi -> preinit6 Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: Can't bind to dhcp address: Cannot assign requested address Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: Please make sure there is no other dhcp server Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: running and that there's no entry for dhcp or Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: bootp in /etc/inetd.conf. Also make sure you Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: are not running HP JetAdmin software, which Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: includes a bootp server. Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: This version of ISC DHCP is based on the relea se available Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: on ftp.isc.org. Features have been added and other changes Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: have been made to the base software release in order to make Jan 19 02:22:43 arbol.wsrcc.com dhclient[998]: it work better with this distribution. Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: <info> (p32p1): DHCPv6 client pid 998 exited with status 1 Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: <info> Activation (p32p1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: <info> Activation (p32p1) Stage 4 of 5 (IPv6 Configure Timeout) started... Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: <info> Activation (p32p1) Stage 4 of 5 (IPv6 Configure Timeout) complete. Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: Can't bind to dhcp address: Cannot assign requested address Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: Please make sure there is no other dhcp server Jan 19 02:22:43 arbol.wsrcc.com NetworkManager[495]: running and that there's no entry for dhcp or --- Additional comment from Wolfgang Rupprecht on 2014-01-19 11:56:22 EST --- for some reason running "systemctl restart NetworkManager" from root allows everything to work correctly. that is also my workaround.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.