-
Notifications
You must be signed in to change notification settings - Fork 288
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
4.7.0-0.okd-2021-04-11-124433: The update cannot be verified: unable to locate a valid signature for one or more sources #605
Comments
Hey Rob, Long time no see/hear. This has happened before. Some image signing process hasn't run yet. Maybe one of the admins need to to restart that process. |
Right, seems the signer has stuck. We'll restart it, until then please use 'oc adm upgrade --force' or set |
I'll wait for the signer to do it's job. |
We see this almost every month. Is there no sustainable solution for this? |
I have the same issue |
just for general info 'oc adm upgrade --force' didn't work |
The second option did work for me to force the update for an unverified image, specifically set |
However the previous signer key has expired, so you'd have to force upgrade this time (and, most likely, the next time too). Sorry for the inconvenience |
Got same problem, mitigated: $ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.okd-2021-04-11-124433 True True 70s Unable to apply 4.7.0-0.okd-2021-04-24-103438: the image may not be safe to use
$ oc adm upgrade --clear=true
Cleared the update field, still at 4.7.0-0.okd-2021-04-24-103438
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.okd-2021-04-11-124433 True True 8m4s Working towards 4.7.0-0.okd-2021-04-11-124433: 601 of 669 done (89% complete)
...
version 4.7.0-0.okd-2021-04-11-124433 True False 107s Cluster version is 4.7.0-0.okd-2021-04-11-124433
$ oc adm upgrade --force --to=4.7.0-0.okd-2021-04-24-103438
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to 4.7.0-0.okd-2021-04-24-103438
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.okd-2021-04-11-124433 True True 5s Working towards 4.7.0-0.okd-2021-04-24-103438: downloading update
...
version 4.7.0-0.okd-2021-04-11-124433 True True 57m Working towards 4.7.0-0.okd-2021-04-24-103438: 301 of 669 done (44% complete)
...
version 4.7.0-0.okd-2021-04-24-103438 True False 20s Cluster version is 4.7.0-0.okd-2021-04-24-103438 |
thanks |
my upgrade --force take a little while but finally completes thanks |
I got: oc get clusterversionNAME VERSION AVAILABLE PROGRESSING SINCE STATUS Can anyone help? |
openshift/cluster-update-keys#36 would resolve that. 4.8 nightlies signature verification works. |
Fixed in 4.7.0-0.okd-2021-05-22-050008. Note that release verification needs to forced this one time. |
I have the same issue: The update cannot be verified: unable to locate a valid signature for one or more sources |
Describe the bug
Hi,
Today I used the update button to update from 4.7.0-0.okd-2021-04-11-124433 to 4.7.0-0.okd-2021-04-24-103438.
But it seems unable to verify the image.
Version
How reproducible
use the update function in okd
Log bundle
Is a log needed ? the update hasn't done anything yet.
Rob
The text was updated successfully, but these errors were encountered: