Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered: Adding of tags could make the image briefly unavailable / not found [1]
What you expected to happen: Updating the <image>:dev tag works without downtime.
Resolution to the old value for a few seconds would be preferred over
getting a "not found".
[1] failed to resolve dev:
not found
Steps to reproduce:
1. Have a script that continuously pulls <image>:dev
2. Update the dev tag via `gcloud artifacts docker tags add
<image>:1.2.0 <image>:dev`
With just a single concurrent request in the pull script around 20% of the
times this causes one failed request (when e.g. alternating between 1.1.0
and 1.2.0 as version for the dev tag).
Other information (workarounds you have tried, documentation consulted, etc):