Bug 1311897 - [online_private_558]Builder pod specification has no activeDeadlineSeconds by default
[online_private_558]Builder pod specification has no activeDeadlineSeconds by...
Status: CLOSED NOTABUG
Product: OpenShift Origin
Classification: Red Hat
Component: Build (Show other bugs)
3.x
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Cesar Wong
Wenjing Zheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-25 04:55 EST by Xingxing Xia
Modified: 2016-02-25 21:09 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-25 21:09:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Xingxing Xia 2016-02-25 04:55:50 EST
Description of problem:
Deployer/Builder pods are kind of run-once pod, oc get pod <deployer/builder pod> -o yaml should have activeDeadlineSeconds by default. But builder pod does not have.

Version-Release number of selected component (if applicable):
oc v1.1.3-267-g0842757
kubernetes v1.2.0-alpha.7-703-gbc4550d

How reproducible:
Alwyas

Steps to Reproduce:
1. Start openshift with default configuration:
1> $ openshift start --public-master=https://<master>:8443 --write-config='openshift.local.config'
2> $ openshift start --master-config='openshift.local.config/master/master-config.yaml' --node-config='openshift.local.config/<node dir>/node-config.yaml'
3> Deploy openshift registry
2. In CLI side, oc login and create project
3. Create new app
$ oc new-app -f origin/examples/sample-app/application-template-stibuild.json
4. Before deployer pod completes, check activeDeadlineSeconds of them
$ oc get pod database-1-deploy ruby-sample-build-1-build -o yaml

Actual results:
4. Only deployer pod has but builder pod does no have:
spec:
    activeDeadlineSeconds: 21600

Expected results:
4. Both pods should have activeDeadlineSeconds

Additional info:
Comment 1 Cesar Wong 2016-02-25 09:42:02 EST
Xingxing Xia I think this is a misunderstanding of our conversation on Trello. The build pods do not have an activeDeadlineSeconds value by default. However, when you enable the plugin and configure a global override value, the build pod should get that value. I tested that case and that works as expected.
Comment 2 Xingxing Xia 2016-02-25 21:09:25 EST
Cesar Wong, got it. Then this is NOTA.

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