Bug 1470851 - Image Pull Error is being marked as Success
Image Pull Error is being marked as Success
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.6.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.7.0
Assigned To: Todd Sanders
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-13 16:03 EDT by Shawn Hurley
Modified: 2017-07-13 17:00 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Shawn Hurley 2017-07-13 16:03:18 EDT
Description of problem:
When the broker is unable to pull the image from a registry it will incorrectly set the state to succeded.

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


How reproducible:
Always 

Steps to Reproduce:
1. Setup a service so that the APB can not be pulled from the registry and the broker always pulls.
2. Provision the service
3.

Actual results:
See that the service succeeded in the etcd job status like this:
{"action":"get","node":{"key":"/state/d6ad07d5-51b3-437b-afe8-870eb4ce5482/job","dir":true,"nodes":[{"key":"/state/d6ad07d5-51b3-437b-afe8-870eb4ce5482/job/4924d165-56fa-4236-b52d-506ded36572e","value":"{\"token\":\"4924d165-56fa-4236-b52d-506ded36572e\",\"state\":\"succeeded\",\"podname\":\"apb-f36b9efb-4c82-4c4f-9880-4eab6ffa5fb4\"}","modifiedIndex":9,"createdIndex":9}],"modifiedIndex":7,"createdIndex":7}}

You should also see the create console screen say that the service was provisioned correctly.

Expected results:
The job should be marked as a failure or in progress if additional attempts at pull are going to be made.

Additional info:

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