Bug 1983205
| Summary: | StatefulSet fails to deploy with error Readiness Probe exec failed open /dev/tty failure no such address when .spec.tty is set to true [OCP 4.6.34] | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Hradayesh Shukla <hshukla> |
| Component: | Node | Assignee: | Peter Hunt <pehunt> |
| Node sub component: | CRI-O | QA Contact: | pmali |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | andcosta, aos-bugs, dlandis, dseals, dwalsh, fsoppels, jokerman, mg4924.kim, naygupta, nkashyap, pehunt, pmali, smolnar |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.9.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-18 17:39:54 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 1985539 | ||
|
Description
Hradayesh Shukla
2021-07-16 20:20:18 UTC
we are seeing the same behavior in OCP 4.6.36 as well, but not in 4.6.20. (In reply to Hradayesh Shukla from comment #0) > Description of problem: > StatefulSet fails to deploy with error Readiness Probe exec failed open > /dev/tty failure no such address when .spec.tty is set to true [] > > > Version-Release number of selected component (if applicable): > OCP 4.6.34 > > > How reproducible: > 100% > > > Steps to Reproduce: > 1. Create a statefulset with ReadinessProbe exec and specifiy .spec.tty to > true and try to deploy it. > > 2. The pods will fail due to failed ReadinessProbe. > > 3. If the .spec.tty is set to false, the pod is scheduled successfully and > it works without any issue. > > > Actual results: > - We see failed readiness probe with following error message: > ~~~ > Warning Unhealthy 77m kubelet > Readiness probe failed: time="2021-07-02T15:29:49Z" level=error msg="exec > failed: open /dev/tty: no such device or address" > Warning Unhealthy 77m kubelet > Readiness probe failed: time="2021-07-02T15:29:59Z" level=error msg="exec > failed: open /dev/tty: no such device or address" > ~~~ > > > Expected results: > - Stateful set should deploy properly. > > > Additional info: > - I feel this could be related to this issue reported here [0], but I am not > sure. > > [0] [rootless+"privileged"] creating device nodes caused: open > /..<snipped>../dev/tty: no such device or address #2450 > https://github.com/opencontainers/runc/issues/2450 weird I'm not able to reproduce on 4.6.34 with the reproducer in https://bugzilla.redhat.com/show_bug.cgi?id=1983205#c5 is there anything I may be missing? Both with and without tty run no problem I have possibly found a fix to the issue in the attached PR setting target for that PR. I will backport to appropriate branches if it proves to work. Hi -- are there any plans yet to backport this fix, in particular to the 4.6.x versions? Hi. I've got this issue as well. In 4.6.43 there was no issue. But in 4.6.45 it occurred. When will it be fixed? Why is it occured again..? 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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/RHSA-2021:3759 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |