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 758620 - UI should show +ADD/Remove on UI to independently add the distro to changeset.
Summary: UI should show +ADD/Remove on UI to independently add the distro to changeset.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-11-30 09:14 UTC by Sachin Ghai
Modified: 2019-09-26 13:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:09:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
No +Add option to add the distro in changeset (27.31 KB, image/png)
2011-11-30 09:15 UTC, Sachin Ghai 		no flags Details
I can add the distro independently (24.96 KB, image/png)
2011-12-16 08:28 UTC, Sachin Ghai 		no flags Details
View All

Description Sachin Ghai 2011-11-30 09:14:19 UTC 
Description of problem:
I was trying to promote a disto independently from 'Locker' to next env. However couldn't see the +ADD on UI like we have for product/repo.

Version-Release number of selected component (if applicable):
[root@dhcp201-133 f15]# rpm -qa | grep katello
katello-glue-pulp-0.1.117-1.fc15.x86_64
katello-common-0.1.117-1.fc15.noarch
katello-glue-candlepin-0.1.117-1.fc15.x86_64
katello-configure-0.1.21-1.fc15.noarch
katello-cli-common-0.1.18-1.fc15.noarch
katello-glue-foreman-0.1.117-1.fc15.x86_64
katello-all-0.1.117-1.fc15.x86_64
katello-cli-0.1.18-1.fc15.noarch
katello-repos-0.1.4-1.fc15.noarch
katello-0.1.117-1.fc15.x86_64
[root@dhcp201-133 f15]# rpm -qa pulp
pulp-0.0.244-5.fc15.noarch
[root@dhcp201-133 f15]

How reproducible:
always

Steps to Reproduce:

1. First I synced the f15 repo on my local disk (e.g. /home/f15) using grinder and moved the .treeinfo file to some location
3. Now I create a repo in katello and pass the file based URL e.g. file:///home/f15
3. Promoted the product to next env 'test'
4. Now move back the .treeinfo file to /home/f15/
5. Re-sync the repo in katello
6. created a changeset
7. I can see the disto in UI but couldn't add it to changeset as no +ADD button was there.
Actual results:
I can see the disto in UI but couldn't promote it as no +ADD button was there on UI.

Expected results:
distro should be promoted independently and UI should show +ADD/Remove on UI  to add the distro to changeset. 

Additional info:
Comment 1 Sachin Ghai 2011-11-30 09:15:57 UTC 
Created attachment 538475 [details]
No +Add option to add the distro in changeset
Comment 2 Sachin Ghai 2011-12-06 08:17:46 UTC 
I retested this on latest build:

[root@dhcp193-175 f15]# rpm -qa | grep katello
katello-repos-0.1.4-1.el6.noarch
katello-cli-0.1.20-1.el6.noarch
katello-glue-pulp-0.1.123-1.el6.x86_64
katello-cli-common-0.1.20-1.el6.noarch
katello-glue-foreman-0.1.123-1.el6.x86_64
katello-configure-0.1.21-1.el6.noarch
katello-glue-candlepin-0.1.123-1.el6.x86_64
katello-common-0.1.123-1.el6.noarch
katello-0.1.123-1.el6.x86_64
katello-all-0.1.123-1.el6.x86_64
You have new mail in /var/spool/mail/root
[root@dhcp193-175 f15]# 


I'm expecting ADD/Remove option on UI to add/remove the distro to changeset independently. I followed the steps as mentioned in comment0. but couldn't succeed.

@Brad, please correct me if I'm following anything wrong here. Thanks !
Comment 3 Brad Buckingham 2011-12-12 16:15:31 UTC 
Sachin, I have been able to repro the issue.  Definitely appears to be a regression.  Will investigate.
Comment 4 Brad Buckingham 2011-12-12 18:53:02 UTC 
commit: 154adab352a6ab87b765b5b8d3a75d548852cf5a

Recent change to store repo information in katello db introduced a regression.  Previously, we used the repo.id in logic to determine if user could promote the distro.  With the recent change, that previous repo.id is now repo.pulp_id.
Comment 5 Sachin Ghai 2011-12-16 08:26:39 UTC 
Thank you Brad !

Verified with following katello build. I can promote the distro independently. 

[root@dhcp201-123 f15]# rpm -qa | grep katello
katello-glue-candlepin-0.1.143-2.el6.noarch
katello-cli-common-0.1.25-2.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-certs-tools-1.0.1-2.el6.noarch
katello-glue-pulp-0.1.143-2.el6.noarch
katello-all-0.1.143-2.el6.noarch
katello-trusted-ssl-cert-1.0-1.noarch
katello-configure-0.1.37-2.el6.noarch
katello-common-0.1.143-2.el6.noarch
katello-0.1.143-2.el6.noarch
katello-cli-0.1.25-2.el6.noarch
katello-glue-foreman-0.1.143-2.el6.noarch
katello-httpd-ssl-key-pair-1.0-1.noarch
[root@dhcp201-123 f15]# 


Since the issue has been fixed, moving this to verified.
Comment 6 Sachin Ghai 2011-12-16 08:28:02 UTC 
Created attachment 547643 [details]
I can add the distro independently
Comment 9 Mike McCune 2013-08-16 18:22:52 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.