| Summary: | `Active Deadline Seconds` does not display on pod details | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Robb Hamilton <rhamilto> |
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, jokerman, spadgett, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1816362 | Environment: |
Version: 4.5.0-0.ci-2020-03-21-123603
Cluster ID: 26d70ff0-7f61-4770-b8b5-0127493bcbad
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36
|
| Last Closed: | 2020-05-04 11:47:20 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1816362 | ||
| Bug Blocks: | |||
|
Description
Robb Hamilton
2020-03-24 12:13:36 UTC
1. Create Pod with following YAML which has activeDeadlineSeconds set
apiVersion: v1
kind: Pod
metadata:
name: init-deadline
spec:
containers:
- name: hello-pod
image: docker.io/ocpqe/hello-pod
ports:
- containerPort: 80
volumeMounts:
- name: workdir
mountPath: /usr/share/nginx/html
initContainers:
- name: init
image: centos:centos7
command:
- /bin/sh
- "-c"
- "sleep 30"
activeDeadlineSeconds: 15
volumes:
- name: workdir
emptyDir: {}
2. Check details on Pod details page, it shows
Active Deadline Seconds
15 seconds
Verified on 4.4.0-0.nightly-2020-04-09-194724
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, 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-2020:0581 |