Bug 1394860 - Overcloud deployment fails due to selinux in enforcing mode
Summary: Overcloud deployment fails due to selinux in enforcing mode
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks: 1335596 1356451
TreeView+ depends on / blocked
 
Reported: 2016-11-14 15:24 UTC by Chris Dearborn
Modified: 2016-12-08 22:01 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-16 18:19:08 UTC
Target Upstream Version:


Attachments (Terms of Use)
Overcloud node console, failed PXE boot (213.39 KB, image/png)
2016-11-14 15:24 UTC, Chris Dearborn
no flags Details

Description Chris Dearborn 2016-11-14 15:24:29 UTC
Created attachment 1220468 [details]
Overcloud node console, failed PXE boot

Description of problem:
In OSP 10, the overcloud deployment fails where every overcloud node fails to PXE boot with an error like:

pxelinux.cfg/24-6e-96-11-87-c4... Operation not permitted (http://ipxe.org/410c613c)

Version-Release number of selected component (if applicable):
OSP10, 10/31 puddle

How reproducible:
With SELINUX in enforcing mode on the director node, attempt an overcloud deployment.

Steps to Reproduce:
1. Install and configure director setting SELINUX to enforcing.
2. Attempt and overcloud deployment.
3. Note the error above on the console of every overcloud node.

Actual results:
Overcloud fails to deploy.

Expected results:
Overcloud should deploy.

Additional info:
- Setting SELINUX on the director node to permissive resolved the problem.
- With a browser, you can navigate to the following URL successfully:
    http://<ip_of_director>:8088/pxelinux.cfg/
  however, the directory shows as empty
- Navigating to /httpboot/pxelinux.cfg in a shell on the director node and doing an "ls" shows symlinks to the correct PXE configuration for each node
- See attached for an example of the error.

Comment 1 Chris Dearborn 2016-11-16 18:18:35 UTC
I've verified that this issue has been fixed in the 11/14 puddle.  Closing.


Note You need to log in before you can comment on or make changes to this bug.