Bug 1294971 - OpenShiftDeploymentVerifier build step fails with false positive.
OpenShiftDeploymentVerifier build step fails with false positive.
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Gabe Montero
Wenjing Zheng
Depends On:
  Show dependency treegraph
Reported: 2015-12-31 06:21 EST by Ali Sogukpinar
Modified: 2016-01-04 10:24 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-01-04 10:24:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Build logs (119.81 KB, text/plain)
2015-12-31 06:21 EST, Ali Sogukpinar
no flags Details

  None (edit)
Description Ali Sogukpinar 2015-12-31 06:21:59 EST
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 06:25:52 EST
Upstream issue has been created.

Comment 2 Ben Parees 2016-01-04 10:24:39 EST
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.

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