Bug 796582 - Unable to promote two errata with same ID in the CLI
Summary: Unable to promote two errata with same ID in the CLI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Tazim Kolhar
URL:
Whiteboard:
Depends On:
Blocks: 1130651
TreeView+ depends on / blocked
 
Reported: 2012-02-23 09:07 UTC by Lukas Zapletal
Modified: 2017-02-23 21:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:59:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Zapletal 2012-02-23 09:07:14 UTC
Import fake CDN, enable and sync three repositories. Five is recommended.

Create an environment "test" and create a changeset:

# kk  changeset create --name test3 --environment test

List all the repos:

# kk repo list
-----------------------------------------------------------------------------------------------
                    Repo List For Org ACME_Corporation Environment Library

 Id   Name                           Package Count  
-----------------------------------------------------------------------------------------------
 6    Zoo Enterprise x86_64 6.2      32             
 19   Zoo Enterprise x86_64 5.4      32             
 58   Zoo Enterprise i386 7          32             
 81   Nature Enterprise i386 1.0     32             
 84   Nature Enterprise x86_64 1.1   32  

Now list all the errata. In this case some repos has the very same errata IDs. In real life I believe those are always unique, but users could possibly create some with same IDs.

# kk errata list 
-----------------------------------------------------------------------------------------------
                                          Errata List

 Id               Title             Type      
-----------------------------------------------------------------------------------------------
 RHEA-2012:0002   Sea_Erratum       security  
 RHEA-2012:0003   Bird_Erratum      security  
 RHEA-2012:0001   Bear_Erratum      security  
 RHEA-2012:0004   Gorilla_Erratum   security  
 RHEA-2012:0002   Sea_Erratum       security  
 RHEA-2012:0003   Bird_Erratum      security  
 RHEA-2012:0001   Bear_Erratum      security  
 RHEA-2012:0004   Gorilla_Erratum   security  
 RHEA-2012:0002   Sea_Erratum       security  
 RHEA-2012:0003   Bird_Erratum      security  
 RHEA-2012:0001   Bear_Erratum      security  
 RHEA-2012:0004   Gorilla_Erratum   security  
 RHEA-2012:0002   Sea_Erratum       security  
 RHEA-2012:0003   Bird_Erratum      security  
 RHEA-2012:0001   Bear_Erratum      security  
 RHEA-2012:0004   Gorilla_Erratum   security  
 RHEA-2012:0002   Sea_Erratum       security  
 RHEA-2012:0003   Bird_Erratum      security  
 RHEA-2012:0001   Bear_Erratum      security  
 RHEA-2012:0004   Gorilla_Erratum   security 

Now let's add an erratum to the changeset. We need to add a product first:

# kk changeset update --name test3 --environment test --from_product "Zoo Enterprise" --add_repo "Zoo Enterprise i386 7"
Successfully updated changeset [ test3 ]

Then erratum. But from which repo: Let's try it:

# kk changeset update --name test3 --environment test --from_product "Zoo Enterprise" --add_erratum RHEA-2012:0001 
Validation failed: Repository of the erratum 'RHEA-2012:0001' has not been promoted into the target environment!

Oh wait, we dont know which one Katello picks up! Now you need to add ALL the repositories until you add the one that matches the erratum:

# kk changeset update --name test3 --environment test --from_product "Zoo Enterprise" --add_repo "Zoo Enterprise x86_64 5.4"
Successfully updated changeset [ test3 ]

This is LOW PRIO bug. We'd need to add some optioin like --from_repo maybe. Not sure.

Comment 2 Walden Raines 2015-02-19 15:52:58 UTC
This should be fixed but please test.

Comment 3 Tazim Kolhar 2015-03-26 10:22:52 UTC
VERIFIED:

# rpm -qa  | grep foreman
foreman-debug-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.6-1.el7sat.noarch
foreman-ovirt-1.7.2.13-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
dhcp201-150.englab.pnq.redhat.com-foreman-client-1.0-1.noarch
dhcp201-150.englab.pnq.redhat.com-foreman-proxy-1.0-2.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.3-1.el7sat.noarch
foreman-compute-1.7.2.13-1.el7sat.noarch
foreman-libvirt-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.6-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.9-1.el7sat.noarch
foreman-selinux-1.7.2.8-1.el7sat.noarch
dhcp201-150.englab.pnq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-discovery-image-2.1.0-9.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el7sat.noarch
foreman-vmware-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.3-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.9-1.el7sat.noarch
foreman-gce-1.7.2.13-1.el7sat.noarch
foreman-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.8-1.el7sat.noarch
foreman-postgresql-1.7.2.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el7sat.noarch

Comment 4 Bryan Kearney 2015-08-11 13:34:34 UTC
This bug is slated to be released with Satellite 6.1.

Comment 5 Bryan Kearney 2015-08-12 13:59:41 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.


Note You need to log in before you can comment on or make changes to this bug.