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:
Created attachment 538475 [details] No +Add option to add the distro in changeset
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 !
Sachin, I have been able to repro the issue. Definitely appears to be a regression. Will investigate.
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.
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.
Created attachment 547643 [details] I can add the distro independently
getting rid of 6.0.0 version since that doesn't exist