You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After troubleshooting some more we were able to narrow it down a bit more:
Successful create
Vim into bundle to ensure the hash it complains about exists:
Successfully published the bundle
Attempted to pull down the bundle:
JaseKoonce
changed the title
SHAs being cached and not re-evaluated if there is no version change
SHAsum validation issues
Nov 13, 2024
JaseKoonce
changed the title
SHAsum validation issues
Certain Layers not being published to remote registry
Nov 13, 2024
Environment
Tested with uds cli 0.18.0 and 0.19.0
Steps to reproduce
Expected result
It pulls down just fine and can be used
Actual Result
An error message about a shasum not existing in the manifest list
We also noticed you can deploy the bundle just fine as long as its stored locally (assuming additional checks are ran when the bundle is remote)
Severity/Priority
Medium
We did attempt to clear the uds and zarf cache:
/tmp/uds* /tmp/zarf* ~/.zarf-cache ~/.uds-cache
is there somewhere else hashes are being cached?The text was updated successfully, but these errors were encountered: