Bug 1327650 - Error adding Openstack Compute Resource while SELINUX is Enabled
Summary: Error adding Openstack Compute Resource while SELINUX is Enabled
Keywords:
Status: CLOSED DUPLICATE of bug 1318327
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 14:34 UTC by Jitendra Yejare
Modified: 2019-04-01 20:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-20 09:16:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
BG logs attached (50.77 KB, text/plain)
2016-04-15 14:34 UTC, Jitendra Yejare
no flags Details

Description Jitendra Yejare 2016-04-15 14:34:02 UTC
Created attachment 1147679 [details]
BG logs attached

Description of problem:
Error in UI while adding/submitting a new Openstack Compute Resource when SELINUX is enabled:
Oops, we're sorry but something went wrong Permission denied - connect(2) for 10.8.100.1:8774 (Errno::EACCES)

Version-Release number of selected component (if applicable):
Sat 6.2 Snap 8.1

How reproducible:
Always (When SELINUX enabled)

Steps to Reproduce:
1. Start creating an openstack Compute Resource.
2. Load the tenants before submitting the openstack compute resource.
3. Submit the openstack Compute Resource.

Actual results:
Error on UI(Oops, we're sorry but something went wrong Permission denied - connect(2) for 10.8.100.1:8774 (Errno::EACCES)) and in bg(http://pastebin.com/vZggFLyX - failed to generate key pair) while submitting the openstack CR when SELINUX on server is enabled.

But It works when SELINUX is disabled.

Expected results:

One should be able to add Openstack CR when SELINUX is enabled.
Additional info:

Comment 2 Lukas Zapletal 2016-04-20 09:16:45 UTC

*** This bug has been marked as a duplicate of bug 1318327 ***


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