Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1536629 - send job state and credentials from job
send job state and credentials from job
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.9.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.9.0
Assigned To: Jesus M. Rodriguez
Zihan Tang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-19 14:12 EST by Jesus M. Rodriguez
Modified: 2018-03-28 10:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:21:18 EDT
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:22 EDT

  None (edit)
Description Jesus M. Rodriguez 2018-01-19 14:12:57 EST
As discussed on IRC with @eriknelson, while looking at the last operation PR it occurred to me it would make more sense to have the Job send through the JobState as part of its msg that is consumed by the subscribers rather than the subscribers deciding what state to set as can be seen here:

 https://github.com/openshift/ansible-service-broker/blob/master/pkg/broker/provision_subscriber.go#L55

I intended to include this change in my main PR for the last_operation feature, but after discussion, it probably makes more sense to have it as a standalone PR.

Upstream issue referenced:
https://github.com/openshift/ansible-service-broker/issues/608
Comment 1 Jesus M. Rodriguez 2018-01-19 14:14:19 EST
PR: https://github.com/openshift/ansible-service-broker/pull/610
Comment 2 Zhang Cheng 2018-01-20 10:13:43 EST
zitang, please try to trace and reproduce. Thanks.
Comment 3 Jesus M. Rodriguez 2018-01-20 10:26:59 EST
(In reply to Zhang Cheng from comment #2)
> zitang, please try to trace and reproduce. Thanks.

This is an internal bug to capture a feature that entered late into the release cycle of the Ansible Broker. Largely internal restructuring of the work engine inside the broker.
Comment 4 Zhang Cheng 2018-01-20 10:47:20 EST
So, is that means regression test is the good choice for us?
Comment 5 Jesus M. Rodriguez 2018-01-20 11:15:40 EST
(In reply to Zhang Cheng from comment #4)
> So, is that means regression test is the good choice for us?

Yes, that is acceptable to test this bug. As long as there are no regressions introduced with the provision, deprovision, bind & unbind features this bug should be covered by those tests.
Comment 6 Jesus M. Rodriguez 2018-01-25 13:49:37 EST
PR https://github.com/openshift/ansible-service-broker/pull/671
Comment 8 Zhang Cheng 2018-02-01 22:35:55 EST
I'm changing status to "Modified" since downstream image not ready for test.
Comment 13 errata-xmlrpc 2018-03-28 10:21:18 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0489

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