Skip to content

Conversation

@mtrmac
Copy link
Collaborator

@mtrmac mtrmac commented Feb 21, 2022

... to help diagnosing later possible broken references to this layer; compare #1136 for situations where that might be relevant.

Note: This will add user-visible warnings even in situations where we are handling incomplete layers correctly. Maybe we should just fix #1136 and the like, and then only log this at a debug level.

@rhatdan
Copy link
Member

rhatdan commented Feb 22, 2022

I am fine logging at this level. If this happens commonly we need to know about it.

LGTM

@mtrmac mtrmac force-pushed the delete-incomplete-warn branch from d6b1a49 to ece0e83 Compare February 22, 2022 13:59
... to help diagnosing later possible broken references
to this layer; compare containers#1136 .

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac mtrmac force-pushed the delete-incomplete-warn branch from ece0e83 to 5654974 Compare February 23, 2022 12:56
@rhatdan
Copy link
Member

rhatdan commented Feb 23, 2022

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vrothberg vrothberg merged commit dc58854 into containers:main Feb 23, 2022
@mtrmac mtrmac deleted the delete-incomplete-warn branch February 23, 2022 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Crash resiliency: deleting incomplete layers doesn’t reliably happen

3 participants