-
Bug
-
Resolution: Obsolete
-
Undefined
-
None
-
4.12
-
Moderate
-
False
-
Description of problem:
When trying to run ‘oc new-app httpd --name httpd’ it always leaves pods in crashLoopBackOff or error state but while performing same with `oc new-app httpd:2.4-el7 --name httpd` works fine with out any issues
Version-Release number of selected component (if applicable):
[knarra@knarra ~]$ oc versionClient Version: 4.12.0-202211081039.p0.g854f807.assembly.stream-854f807Kustomize Version: v4.5.7Server Version: 4.12.0-rc.4Kubernetes Version: v1.25.4+86bd4ff
How reproducible:
Always
Steps to Reproduce:
1. Install latest 4.12 cluster 2. Run command ‘oc new-app httpd --name httpd`
Actual results:
Pods are in crashLoopBackOff or error state and when checking for pod logs below has been observed but when running `oc new-app httpd:2.4-el7 --name httpd` always works.[knarra@knarra ~]$ oc logs -f httpd-59f6564b74-7dw8qAH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 10.135.0.7. Set the 'ServerName' directive globally to suppress this message(13)Permission denied: AH00072: make_sock: could not bind to address [::]:80(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80no listening sockets available, shutting downAH00015: Unable to open logs
Expected results:
`oc new-app httpd --name httpd` command should work fine
Additional info:
If oc new-app httpd:2.4-el7 works, and httpd:latest does not work it might be because it requires additional oc adm policy add-scc-to-user anyuid -z default -n <ns_hosting_httpd>
