dkcbk

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023
10:35 AM
- 4,610 Views
1 Solution
Accepted Solutions
dkcbk

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023
02:38 PM
- 4,592 Views
I found the issue. The problem was port 80. Openshift uses restricted SCC, which prevents the use of ports < 1024. The solution was to enable the anyuid SCC for the service account used by the awx-web pod.
4 Replies

Community Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023
02:25 PM
- 4,594 Views
Hey @dkcbk !
Are you getting anything in the pod logs ? What type is the service ? How are you accessing the console ?
dkcbk

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023
02:38 PM
- 4,593 Views
I found the issue. The problem was port 80. Openshift uses restricted SCC, which prevents the use of ports < 1024. The solution was to enable the anyuid SCC for the service account used by the awx-web pod.

Community Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023
02:44 PM
- 4,586 Views
Cant we use port 8080 instead of enabling the anyuid security constraint context ?
dkcbk

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023
02:50 PM
- 4,584 Views
I think you can use different port only in case of LoadBalancer type of service
Join the discussion
You must log in to join this conversation.