Bug 1045682
| Summary: | SELinux preventing dhclient from reading libk5crypto.so.3 resulting in no addresses received/assigned | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Mossor [danofsatx] <danofsatx> | ||||||
| Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | rawhide | CC: | amigadave, awilliam, bruno, danofsatx, jpopelka, mgrepl, robatino, satellitgo, thozza | ||||||
| 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: | 2014-01-02 21:53:26 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: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1043119 | ||||||||
| Attachments: |
|
||||||||
This is an SELinux issue; check the journal for errors from auditctl. If you do 'setenforce Permissive' it works. Created attachment 840912 [details]
journal output showing execstack and execmem denials for dhclient
setting selinux to permissive fixes the KDE networking problem (with sddm) in f21 (rawhide) a live install of latest koji see also BZ 1045937 Same base issue as bz 1045699 - marking as duplicate. *** This bug has been marked as a duplicate of bug 1045699 *** |
Created attachment 839925 [details] messages log containing error on restart of NetworkManager Description of problem: No IPv4 addresses are being assigned via DHCP to the network interfaces. Version-Release number of selected component (if applicable): dhclient-4.2.5-28.fc21.x86_64 NetworkManager-0.9.9.0-19.git20131003.fc21.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Activate a network interface configured to receive an address via DHCP. 2. Wait patiently. 3. Discover that no IPv4 address was assigned. Actual results: No IPv4 address assigned to interface, effectively blocking all network access (IPv6 was not tested due to other issues with IPv6 registration). Expected results: IPv4 address assigned by the DHCP server, allowing system to communicate on the network.