Hide Forgot
Description of problem: - HS startup script fails due to file permission errors in OpenShift. - '/opt/hawkular' probably does not allow access to arbitrary user per https://docs.openshift.org/latest/creating_images/guidelines.html Version-Release number of selected component (if applicable): - Hawkular-Services ER1 - OpenShift v3.2 How reproducible: 100% Steps to Reproduce: 1. Download attached template .yaml 2. # oc create -f er-hs-template.yaml 3. # oc new-app -t hawkular-rh Actual results: - HS pod fails to start Expected results: - HS pod starts normally
Created attachment 1227438 [details] console error log
Created attachment 1227439 [details] openshift template file
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.
Severity=Medium. While OpenShift v3 is out of scope for this release I think the OSE support should be the priority in future releases.
Created attachment 1230874 [details] dir permissions The pod was run as default/authenticated user SCC. As you we can see here the directory lacks "w" permission for group root
Does this issue also occur using the upstream image?
The upstream image built by QE works fine. Repo: https://github.com/Hawkular-QE/hawkular-services-docker
I mean the upstream hawkular services image available here: https://hub.docker.com/r/hawkular/hawkular-services/ For the prod image I'll update the permissions to give write access to the group and make the root group the owner, similar to the QE image and the recommendation in the openshift docs.
I built a new image which hopefully has the correct permissions. If you pull the latest middleware-manager image you should be able to test.
I'm able to launch in OSE3.4.
Created attachment 1250421 [details] verified1
Created attachment 1250422 [details] verified2