New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1504729 - Log job state when getting last op #505
Conversation
| a.log.Debug(fmt.Sprintf("service_id: %s", req.ServiceID)) // optional | ||
| a.log.Debug(fmt.Sprintf("plan_id: %s", req.PlanID)) // optional | ||
| a.log.Debug(fmt.Sprintf("operation: %s", req.Operation)) // this is provided with the provision. task id from the work_engine | ||
| a.log.Debugf("service_id: %s", req.ServiceID) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for killing the fmt.Sprint, there's a lot of that left over from the old days :)
pkg/broker/broker.go
Outdated
| a.log.Debug(fmt.Sprintf("operation: %s", req.Operation)) // this is provided with the provision. task id from the work_engine | ||
| a.log.Debugf("service_id: %s", req.ServiceID) | ||
| a.log.Debugf("plan_id: %s", req.PlanID) | ||
| a.log.Debugf("operation: %s", req.Operation) // this is provided with the provision. task id from the work_engine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: the comment is a little inaccurate, it'll be there with every async op, not just provision.
pkg/broker/broker.go
Outdated
| @@ -1004,7 +1004,7 @@ func (a AnsibleBroker) LastOperation(instanceUUID uuid.UUID, req *LastOperationR | |||
| */ | |||
| a.log.Debugf("service_id: %s", req.ServiceID) | |||
| a.log.Debugf("plan_id: %s", req.PlanID) | |||
| a.log.Debugf("operation: %s", req.Operation) // this is provided with the provision. task id from the work_engine | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this an erroneous comment? The operation is expected to be the job token (task_id) from the work_engine that happened during the provision. At a minimum I'd remove provision and make it clear that we expect operation to be the job token id.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just remarked it wasn't entirely accurate since all async jobs will set that to be the job token, not just provision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cleanup the comment to make it more clear vs removing.
bcb5fe2
to
2a6fdda
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry while this is a TRIVIAL change, we're in bug mode. So in order to get this into 3.7 we need a bugzlila. The bug will only need QE to look at the logs to see the desired statement.
|
If this was changing something in docs or build file stuff I would let it slide. This is actually changing mainline broker code so a bugzilla is required. |
2a6fdda
to
a10ae7d
Compare
Simple enhancement so that we can see the state of the last operation when the service-catalog requests it.