Bug 1294971

Summary: OpenShiftDeploymentVerifier build step fails with false positive.
Product: OpenShift Container Platform Reporter: Ali Sogukpinar <asogukpi>
Component: BuildAssignee: Gabe Montero <gmontero>
Status: CLOSED NOTABUG QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, bparees
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-04 15:24:39 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:
Attachments:
Description Flags
Build logs none

Description Ali Sogukpinar 2015-12-31 11:21:59 UTC
Created attachment 1110740 [details]
Build logs

Description of problem:

I have a build job with a OpenShiftDeploymentVerifier build step. It is configured to verify if there is one pod running after build set. Even though I have one pod running this steps fails hence, my build job fails.


Version-Release number of selected component (if applicable):

docker.io/openshift/jenkins-1-centos7 latest 212bac2225d0 6 days ago 655.4 MB

How reproducible:

1) Create a build job following build steps

- Scale deployments in Openshift (scale down to 0)
- Perform builds in Openshift
- Scale deployments in Openshift (scale up to 1)
- Verify a service is up in OpenShift
- Check Deployment Success in OpenShift (number of replicas is scaled to 1)

2) Trigger a build

Actual results:

There is one replica running however, build is marked as failed.

Expected results:

Build is successful.

Additional info:

Comment 1 Ali Sogukpinar 2015-12-31 11:25:52 UTC
Upstream issue has been created.

https://github.com/openshift/jenkins-plugin/issues/11

Comment 2 Ben Parees 2016-01-04 15:24:39 UTC
Per discussion in the issue, this is not a bug, but the docs could be improved.  we'll get the docs fixed via the issue mentioned above.