-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman-remote untag image is broken #7716
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@mheon PTAL, |
I think we need @vrothberg or @baude or someone else more familiar with the image code to comment here... I don't really know why this was added. Tests are red without it, though. |
@saschagrunert added that code. It sounds reasonable to not display a name twice. I am currently trying to reproduce the untag issue as I fail to see a relation at the moment. |
It looks like a symptomatic fix. Local and remote untag should execute the same code. If there's a hiccup in remote, I suspect there's something else going on. |
Looking closer at the untag endpoint, there are a couple of issues:
... and probably more |
c562850
to
23c77a9
Compare
cd9d2f4
to
25a5e79
Compare
Untagging all is still broken as the endpoint forces a repo to be specified. I'll wrap up something for that and link it here. |
It bit me in the tests in #7823 |
2da9800
to
5b1ef38
Compare
There seems to be some questionable code in NamesHistory which is not returning the true value of the history. Basically this ends up truncating the last item on the list which causes the test to fail. Not sure if this code is still necessary or what it breaks. Signed-off-by: Daniel J Walsh <[email protected]>
Replaced with #7840 |
There seems to be some questionable code in NamesHistory which is not
returning the true value of the history. Basically this ends up truncating
the last item on the list which causes the test to fail.
Not sure if this code is still necessary or what it breaks.
Signed-off-by: Daniel J Walsh [email protected]