Bug 1393074

Summary:	UI Log Collection for Red Hat Dropbox does not ask for case number
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	UI - OPS	Assignee:	Martin Povolny <mpovolny>
Status:	CLOSED ERRATA	QA Contact:	Oleksii Tsuman <otsuman>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.6.0	CC:	cpelland, hkataria, jhardy, jocarter, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	5.7.0
Hardware:	All
OS:	All
Whiteboard:	log_depot
Fixed In Version:	5.7.0.10	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1388593	Environment:
Last Closed:	2017-01-04 13:20:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1388593
Bug Blocks:

Comment 2 Oleksii Tsuman 2016-11-10 15:32:24 UTC

It present in 5.7.0.10-beta3.20161109111947_9a61b18 
But, if you select "collect all" or "collect current" second time "prevent this page from creating additional dialogs" check-box will occur. So if you select this option and after this will try to collect log another time - nothing will happen( even pop-up menu with usecase number will be absent) 

Is it work as defined or not?

Comment 4 Oleksii Tsuman 2016-11-15 08:41:36 UTC

Moving "on_dev" because of problem described previously in comments(comment 2). Problem present in 5.7.0.10-beta3.20161109111947_9a61b18

Comment 5 Martin Povolny 2016-11-15 10:27:48 UTC

So if you prevent the page from creating pop-ups, then the page cannot create pop-ups ;-) Even the one for the case number.

Works as designed.

Comment 6 Oleksii Tsuman 2016-11-15 10:35:23 UTC

Thanks Martin. My bad. 

verified in  5.7.0.10-beta3.20161109111947_9a61b18. Now log collection asking case number for dropbox

Comment 8 errata-xmlrpc 2017-01-04 13:20:38 UTC

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://rhn.redhat.com/errata/RHBA-2017-0012.html