Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1014673 - Assigning repo to content view definition in UI clears the puppet repo selection
Summary: Assigning repo to content view definition in UI clears the puppet repo selection
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-02 14:05 UTC by Ivan Necas
Modified: 2019-09-26 17:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ivan Necas 2013-10-02 14:05:39 UTC 
Steps to Reproduce:
1. create yum and puppet repo
2. create content view definition, add the puppet repo to it
3. add the yum repo to the definition
4. reload the page

Actual results:
the puppet repo is not selected in the definition

Expected results:
the puppet repo keeps selected after adding the yum repo
Comment 2 David Davis 2013-10-07 20:24:50 UTC 
https://github.com/Katello/katello/pull/3111
Comment 3 David Davis 2013-10-09 12:48:24 UTC 
katello f3997174e38e1a9639a2cb1b0398902f10ded4b0

1014673: Fix problem where puppet repo gets unset
Comment 6 Sachin Ghai 2013-10-21 08:54:22 UTC 
Bz 1021394 needs to be fixed to verify this bz.
Comment 7 Sachin Ghai 2013-10-22 11:03:33 UTC 
Bz 1021394 is fixed  which is duplicate of 1020463. So I re-verified it with following build:
 
[root@HOST201-143 ~]# rpm -qa | grep katello
katello-1.4.6-44.el6sat.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-configure-1.4.7-7.el6sat.noarch
katello-glue-elasticsearch-1.4.6-44.el6sat.noarch
katello-foreman-all-1.4.6-44.el6sat.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
ruby193-rubygem-foreman-katello-engine-0.0.17-6.el6sat.noarch
katello-common-1.4.6-44.el6sat.noarch
pulp-katello-plugins-0.2-1.el6sat.noarch
katello-configure-foreman-1.4.7-7.el6sat.noarch
katello-cli-1.4.3-26.el6sat.noarch
katello-certs-tools-1.4.4-1.el6sat.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-selinux-1.4.4-4.el6sat.noarch
katello-glue-pulp-1.4.6-44.el6sat.noarch
katello-glue-candlepin-1.4.6-44.el6sat.noarch
katello-cli-common-1.4.3-26.el6sat.noarch
katello-all-1.4.6-44.el6sat.noarch
ruby193-rubygem-katello_api-0.0.3-4.el6sat.noarch
signo-katello-0.0.23-2.el6sat.noarch
ruby193-rubygem-katello-foreman-engine-0.0.12-3.el6sat.noarch

After adding the puppet repo and then yum repo to cv, when we reload the page, the puppet repo keeps selected. Please see the screenshot for verification.
Comment 8 Bryan Kearney 2014-04-24 17:10:47 UTC 
This was verified and delivered with MDP2. Closing it out.
Comment 9 Bryan Kearney 2014-04-24 17:11:53 UTC 
This was delivered and verified with MDP2. Closing the bug.
Note You need to log in before you can comment on or make changes to this bug.