Bug 1466113 - Incorrect info for invalid value of activeDeadlineSeconds
Summary: Incorrect info for invalid value of activeDeadlineSeconds
Keywords:
Status: CLOSED DUPLICATE of bug 1449080
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: oc
Version: 3.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-29 05:38 UTC by Weihua Meng
Modified: 2017-06-29 13:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-29 13:59:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Weihua Meng 2017-06-29 05:38:50 UTC
Description of problem:
Incorrect info for invalid value of activeDeadlineSeconds

Version-Release number of selected component (if applicable):
openshift v3.6.126.1

How reproducible:
Always

Steps to Reproduce:
1. create a pod
# cat act-pod.yaml 
apiVersion: v1
kind: Pod
metadata:
  name: hello-pod
spec:
  containers:
    - image: "docker.io/ocpqe/hello-pod"
      name: hello-pod
# oc create -f act-pod.yaml
pod "hello-pod" created

2. patch spec.activeDeadlineSeconds with a negtive value
# oc patch pod hello-pod -p \{\"spec\":\{\"activeDeadlineSeconds\":-361\}\}


Actual results:
# oc patch pod hello-pod -p \{\"spec\":\{\"activeDeadlineSeconds\":-361\}\}
The Pod "hello-pod" is invalid: 
* spec.activeDeadlineSeconds: Invalid value: -361: must be between 1 and 2147483647, inclusive
* spec.activeDeadlineSeconds: Invalid value: -361: must be between 0 and 2147483647, inclusive

Expected results:
remove the last line, which is incorrect and duplicated

Additional info:

Comment 1 yufchang 2017-06-29 09:30:43 UTC
Dup with https://bugzilla.redhat.com/show_bug.cgi?id=1449080

Comment 2 Jessica Forrester 2017-06-29 13:59:27 UTC

*** This bug has been marked as a duplicate of bug 1449080 ***


Note You need to log in before you can comment on or make changes to this bug.