-
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
not mounted layers should be reported as info not error #20456
Conversation
@edsantiago might help. |
Code LGTM |
libpod/container_internal.go
Outdated
} else { | ||
switch { | ||
case errors.Is(err, storage.ErrLayerNotMounted): | ||
logrus.Info("Storage for container %s is not mounted: %v", c.ID(), err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logrus.Info("Storage for container %s is not mounted: %v", c.ID(), err) | |
logrus.Infof("Storage for container %s is not mounted: %v", c.ID(), err) |
There is a potential race condition we are seeing where we are seeing a message about a removed container which could be caused by a non mounted container, this change should clarify which is causing it. Also if the container does not exists, just warn the user instead of reporting an error, not much the user can do. Fixes: containers#19702 [NO NEW TESTS NEEDED] Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/unhold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan, vrothberg 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 |
There is a potential race condition we are seeing where we are seeing a message about a removed container which could be caused by a non mounted container, this change should clarify which is causing it.
Also if the container does not exists, just warn the user instead of reporting an error, not much the user can do.
Fixes: #19702
[NO NEW TESTS NEEDED]
Does this PR introduce a user-facing change?