-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cypress - fix after pulp-ci-centos s6-overlay upgrade #2503
Conversation
After pulp/pulp-oci-images#231, the path to restart the pulpcore-api service has changed, updating. `find /var/run/s6* -name pulpcore-api` finds 2 options... /var/run/s6/db/servicedirs/pulpcore-api /var/run/s6-rc:s6-rc-init:GFjbCb/servicedirs/pulpcore-api the first fails with `s6-svc: fatal: unable to control /var/run/s6/db/servicedirs/pulpcore-api: supervisor not listening` the second seems to work, except the `GFjbCb` bit is a random hash that keeps changing => assuming /var/run/s6-rc:*/ will always find just one option No-Issue
Merging to get tests green |
* Cypress - fix after pulp-ci-centos s6-overlay upgrade After pulp/pulp-oci-images#231, the path to restart the pulpcore-api service has changed, updating. `find /var/run/s6* -name pulpcore-api` finds 2 options... /var/run/s6/db/servicedirs/pulpcore-api /var/run/s6-rc:s6-rc-init:GFjbCb/servicedirs/pulpcore-api the first fails with `s6-svc: fatal: unable to control /var/run/s6/db/servicedirs/pulpcore-api: supervisor not listening` the second seems to work, except the `GFjbCb` bit is a random hash that keeps changing => assuming /var/run/s6-rc:*/ will always find just one option No-Issue * Prefer /var/run/s6-rc/ symlink over /var/run/s6-rc:s6-rc-init:RANDOM_HASH/ (cherry picked from commit 8e11117)
* Cypress - fix after pulp-ci-centos s6-overlay upgrade After pulp/pulp-oci-images#231, the path to restart the pulpcore-api service has changed, updating. `find /var/run/s6* -name pulpcore-api` finds 2 options... /var/run/s6/db/servicedirs/pulpcore-api /var/run/s6-rc:s6-rc-init:GFjbCb/servicedirs/pulpcore-api the first fails with `s6-svc: fatal: unable to control /var/run/s6/db/servicedirs/pulpcore-api: supervisor not listening` the second seems to work, except the `GFjbCb` bit is a random hash that keeps changing => assuming /var/run/s6-rc:*/ will always find just one option No-Issue * Prefer /var/run/s6-rc/ symlink over /var/run/s6-rc:s6-rc-init:RANDOM_HASH/ (cherry picked from commit 8e11117)
Does NOT need a backport for now, looks like the 3.15 and 3.18 images still use the old s6 service paths. |
Ok, does seem to be needed now for 4.4: https://github.com/ansible/ansible-hub-ui/runs/8114735243?check_suite_focus=true EDIT: Oh never mind, ordering, #2512 was created before merging #2500, so it was still trying to use pulp-ci-centos:latest, instead of pulp-ci-centos:3.15 |
After pulp/pulp-oci-images#231, the path to restart the pulpcore-api service has changed, leading to cypress failing to build on CI: https://github.com/ansible/ansible-hub-ui/runs/8098212627?check_suite_focus=true
=> updating the path.
find /var/run/s6* -name pulpcore-api
finds 2 options...the first fails with
s6-svc: fatal: unable to control /var/run/s6/db/servicedirs/pulpcore-api: supervisor not listening
the second seems to work, except the
GFjbCb
bit is a random hash that keeps changing=> assuming/var/run/s6-rc:*/servicedirs/pulpcore-api
will always find just one option.... but there's also a
/var/run/s6-rc
symlink to the rights6-rc:s6-rc-init:GFjbCb
dir.=> using
/var/run/s6-rc/servicesdirs/pulpcore-api
now