Bug 1504729 – Ansible Service Broker should log job state

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1504729 - Ansible Service Broker should log job state

Summary:	Ansible Service Broker should log job state

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Service Broker (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	All All

Priority	unspecified Severity low
Target Milestone:	---
Target Release:	3.7.0
Assigned To:	David Zager
QA Contact:	Zhang Cheng
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-20 09:36 EDT by David Zager
Modified:	2017-11-28 17:18 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-11-28 17:18:47 EST
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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:3188	normal	SHIPPED_LIVE	Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update	2017-11-28 21:34:54 EST

Groups: None (edit)

Description David Zager 2017-10-20 09:36:17 EDT

Description of problem:

When the service-catalog is asking for the status of a service instance operation currently in progress, the broker should log the state of that operation before constructing a response object to send back to the service-catalog. This is most useful when debugging messages between the service-catalog and the broker.


How reproducible: Always


Steps to Reproduce:
1. Start an OpenShift cluster with the Service Catalog and Ansible Service Broker
2. Provision an APB
3. Look at the service broker's logs

Actual results:

[DEBUG] service_id: 9f7da06f179b895a8ee5f9a3ce4af7ef
[DEBUG] plan_id: 2529017a538fda00903782ddd68124c9
[DEBUG] operation:  d998adef-3b18-4940-93c6-fc64b5f81243
"GET /ansible-service-broker/v2/service_instances/30994e86-94ba-48fc-8ddb-97f383906897/last_operation?operation=d998adef-3b18-4940-93c6-fc64b5f81243&plan_id=2529017a538fda00903782ddd68124c9&service_id=9f7da06f179b895a8ee5f9a3ce4af7ef HTTP/1.1" 200 29


Expected results:

[DEBUG] service_id: 9f7da06f179b895a8ee5f9a3ce4af7ef
[DEBUG] plan_id: 2529017a538fda00903782ddd68124c9
[DEBUG] operation:  d998adef-3b18-4940-93c6-fc64b5f81243
[DEBUG] state: in progress
"GET /ansible-service-broker/v2/service_instances/30994e86-94ba-48fc-8ddb-97f383906897/last_operation?operation=d998adef-3b18-4940-93c6-fc64b5f81243&plan_id=2529017a538fda00903782ddd68124c9&service_id=9f7da06f179b895a8ee5f9a3ce4af7ef HTTP/1.1" 200 29

Comment 1 David Zager 2017-10-20 09:36:54 EDT

https://github.com/openshift/ansible-service-broker/pull/505

Comment 3 Zhang Cheng 2017-11-01 05:26:23 EDT

Verified and test with ose-ansible-service-broker:v3.7.0-0.188.0.0

Have below logs in asb log while provisioning:
[2017-11-01T09:22:55.27Z] [DEBUG] service_id: 268dbc13f56297fdd3737b7d30104eb4
[2017-11-01T09:22:55.27Z] [DEBUG] plan_id: c54bf88ce67b96a39e639d2bdf6caf1a
[2017-11-01T09:22:55.27Z] [DEBUG] operation:  be456468-8b4e-48e5-ab43-8b669927386d
[2017-11-01T09:22:55.271Z] [DEBUG] state: in progress

Comment 6 errata-xmlrpc 2017-11-28 17:18:47 EST

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/RHSA-2017:3188

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