Bug 1294971 - OpenShiftDeploymentVerifier build step fails with false positive.
Summary: OpenShiftDeploymentVerifier build step fails with false positive.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Gabe Montero
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-31 11:21 UTC by Ali Sogukpinar
Modified: 2019-09-12 09:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-04 15:24:39 UTC
Target Upstream Version:
Embargoed:


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

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.


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