Red Hat Bugzilla – Bug 806076
Promotion - viewing system template doesn't show the repos in that template
Last modified: 2013-08-16 14:03:25 EDT
Description of problem:
When a user views a system template through the Content sliding tree on the promotions page, the information presented about the template is incomplete.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a system template (e.g. template1)
2. add some repos, packages and package groups to the template (and save)
3. go to Content Management -> Promotions
4. navigate to the template just created
A pane is opened showing information about the template such as the name and the list of packages contained within it.
The actual results plus the rest of the information added to the template (e.g. repositories, package groups...etc)
is there any kind of workaround to this?
A possible workaround would be for the user to go to the System Templates page and view the content of the template from there. Unfortunately, I do not feel that is a good workaround. The reason being,a user could conceivably see the 'partial' data that is shown in the Promotions view, add the template and promote, in which case they'd end up promoting unintended content.
katello commit - 6f16244c646dfdb3330b1259c4aa05960a48d7c7
mmccune, what's the status on this bug. With the lack of a sufficient workaround, is this a 1.0 blocker?
If not, let's set 'cloudforms-1.1.0?' and aim to resolve this in the next release.
Verified this defect with following CFSE build:
I can see the complete info of system template on right pane ( name, packages, repo, package groups, KS distribution). Please see the attachment.
Created attachment 616379 [details]
sys template shows the complete info (packages, package_group, ks_distribution,repo) on right pane.
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.
getting rid of 6.0.0 version since that doesn't exist