| Summary: | Unable to promote two errata with same ID in the CLI | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
| Component: | katello-agent | Assignee: | Katello Bug Bin <katello-bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | bkearney, cwelton, mmccune, sthirugn, tkolhar, walden |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-12 13:59:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1130651 | ||
This should be fixed but please test. 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 This bug is slated to be released with Satellite 6.1. This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015. |
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.