Bug 2067464
Summary: | FailedMount MountVolume.SetUp failed for volume "kube-api-access" : object "openshift-kube-scheduler"/"kube-root-ca.crt" not registered | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Kaushal <kmudalia> |
Component: | Node | Assignee: | Ryan Phillips <rphillips> |
Node sub component: | Kubelet | QA Contact: | Sunil Choudhary <schoudha> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | high | CC: | aos-bugs, ehashman, erich, kangell, nagrawal, patmarti, rphillips |
Version: | 4.10 | Keywords: | Reopened, ServiceDeliveryBlocker |
Target Milestone: | --- | ||
Target Release: | 4.10.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1999325 | Environment: | |
Last Closed: | 2022-05-23 13:25:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1999325 | ||
Bug Blocks: | 2075704 |
Description
Kaushal
2022-03-23 21:00:06 UTC
@kaushal(In reply to Kaushal from comment #0) > I believe this has been fixed in 4.11 but given the nature of this (it > blocks IBM for months), we would like to request that it be back-ported to > 4.10 This is not yet fixed in 4.11 because the rebase hasn't happened yet. We plan on backporting to all affected versions, both 4.10 and 4.9, when we've confirmed the fix. Can you share a bit more information about the impact of this bug? My understanding from the parent BZ and the patches in Kubernetes is that this is just logspam; a warning is printed suggesting there is a mount issue, but the mounts are successful and their contents are available in pods, hence why I've marked the bug as severity medium. IBM team did some further testing and have verified that this is only a logging error. The mounts are successful despite the error. Should we just keep this ticket open for the back-port request or close it and track with the original ticket ? CC @kangell CC @ehashman CC @patmarti @kmudalia I would say it depends if this is already tracked elsewhere. I think at this time I will close this bug, and we'll have the bot open backport bugs automatically when we are ready to backport the patches. It will be a little bit cleaner/more centralized that way. *** This bug has been marked as a duplicate of bug 1999325 *** Reopening for backport. Checked CI logs and don't see these errors for 4.10 https://search.ci.openshift.org/?search=FailedMount+MountVolume.SetUp+failed+for+volume.*kube-api-access.*not+registered&maxAge=168h&context=1&type=junit&name=4.9&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.10.15 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:2258 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |