-
Notifications
You must be signed in to change notification settings - Fork 27
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
packer/scylla_install_image: update gpg key inisde the image #534
packer/scylla_install_image: update gpg key inisde the image #534
Conversation
Following the changes in 23bc340, it seems i missed a place for the gpg key replacement adding it so we can run `apt-get update` inside our images Fixes: scylladb/scylla-pkg#4255
Verified with https://jenkins.scylladb.com/job/scylla-master/job/releng-testing/job/next-machine-image/370/ (https://jenkins.scylladb.com/job/scylla-master/job/releng-testing/job/artifacts/job/artifacts-ami-arm-test/46/ failed due unrelated failure, re-run was ok) Also created an instance based on the AMI that was created and verified
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Is there a way to prevent this in the future?
Some kind of unit test, or just one place to update these keys?
We should, and we plan For now we are following the procedure in https://github.com/scylladb/scylla-pkg/wiki/GPG---keys-lifecycle-and-setup , i have made it more clear for next time (it was my first time :-) ) |
Following the changes in 23bc340, it seems i missed a place for the gpg key replacement
adding it so we can run
apt-get update
inside our imagesFixes: https://github.com/scylladb/scylla-pkg/issues/4255