Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1599635

Summary: RFE: print the exact location of the client configuration RPM that rhui-manager has built
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: Radek Bíba <rbiba>
Component: ToolsAssignee: Martin Minar <mminar>
Status: CLOSED ERRATA QA Contact: Radek Bíba <rbiba>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.0.4CC: mminar
Target Milestone: 3.0.5Keywords: FutureFeature
Target Release: 3.0.x   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-05 17:04:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Radek Bíba 2018-07-10 09:05:00 UTC 
Description of problem:
When I'm creating a client configuration, I need to know the path to the resulting package, but I only get the buildroot directory. This reduces my efficiency.

Version-Release number of selected component (if applicable):
rh-rhui-tools-3.0.4-1

How reproducible:
Always

Steps to Reproduce:
1. Create a client configuration RPM in rhui-manager, specifying a directory of your choice when asked.

Actual results:
In the end, rhui-manager prints:

Successfully created client configuration RPM.
RPMs can be found at THE_DIRECTORY

Expected results:
rhui-manager gives me the full path. Note that only a single RPM is created, so the plural isn't appropriate either.

For example, if I enter "config" as the package name, "2.0" as the version, and "/tmp" as the directory, I'd like to see the following output:

Successfully created client configuration RPM:
/tmp/config-2.0/build/RPMS/noarch/config-2.0-1.noarch.rpm
Comment 6 errata-xmlrpc 2018-09-05 17:04:27 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://access.redhat.com/errata/RHBA-2018:2649