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.

Sign up for GitHub

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

Jump to bottom

[pkg.origin.jenkins.io] `sync.sh` and puppet agent competes to update the jenkins repo keys #3364

Open

dduportal opened this issue Mar 29, 2024 · 0 comments

Contributor

dduportal commented Mar 29, 2024

Since #2720, the puppet agent deploys the 2023 keys into /var/www/pkg.jenkins.io (e.g. production of pkg.origin.jenkins.io).

However the sync.sh script, executed once per hour by the mirrorbrain's crontab copies the content of /var/www/pkg.jenkins.io.staging to pkg.origin.jenkins.io (production) and overrides the key values.

We need to:

Ensure that this competition stops happening (we can remove key management from puppet, or from the Core release process which populates the pkg staging, of fix both)
Ensure that the proper key is used.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment