Bug 1649219 - User object is shown instead of user id in the logs
Summary: User object is shown instead of user id in the logs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.6
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: 5.9.z
Assignee: drew uhlmann
QA Contact: Jaroslav Henner
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-13 07:47 UTC by Dmitry Misharov
Modified: 2020-01-03 16:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-22 20:14:37 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dmitry Misharov 2018-11-13 07:47:43 UTC 
Version-Release number of selected component (if applicable):
5.9.6.0.20181105224828_652732b

How reproducible:
Always

Steps to Reproduce:
1. Create a user.
2. Create a generic service.
3. Provision it.
4. Retire it.

Actual results:
User object is shown in the log: "retirement_requester: #<User:0x0000000013cfd560>"

Expected results:
The log message should show user id.
Comment 4 drew uhlmann 2018-11-13 15:21:20 UTC 
https://github.com/ManageIQ/manageiq/pull/18193
Comment 5 drew uhlmann 2018-11-13 15:28:46 UTC 
This is _only_ a 5.9 issue, it's been fixed on hammer and everything later.
Comment 6 drew uhlmann 2018-11-13 16:46:45 UTC 
Hey Dennis, can I get the target release changed, per comment 5, please?
Comment 7 drew uhlmann 2018-12-17 14:07:06 UTC 
This got approved 20 days ago, so I'm moving it from on dev to assigned because it's done but I'm waiting for it to be merged...
Comment 9 dmetzger 2018-12-18 16:45:39 UTC 
Previous closure was in error, leaving this as cfme_future for consideration in future 5.9 errata
Comment 10 drew uhlmann 2019-01-14 16:42:59 UTC 
Thanks, Dennis. 

PR is reopened, approved, and green.

I have a small issue with the fact that this ticket is still assigned to me because at this point it's kinda out of my hands to do anything with it and I'd really like for it to no longer be my responsibility. 

Can we please get this merged?
Comment 12 drew uhlmann 2019-01-17 14:37:21 UTC 
Dennis, can we please do something with this?
Comment 13 dmetzger 2019-01-22 20:14:37 UTC 
Based on input from CEE/PM, this ticket is being closed fixed in current release.
Comment 14 drew uhlmann 2019-01-22 20:18:00 UTC 
Wow.
Note You need to log in before you can comment on or make changes to this bug.