Description of problem: Getting errata info on a particular errata using the katello CLI seems overly complex. It's much quicker to do a web search for errata info than to use the katello CLI. Katello CLI tools require not only the errata ID, but also repo name and product or product ID. A sysadmin needs to copy the errata ID from step 1, copy the repo from step 2 and copy the product list from step 3 and paste this into step 4. This is difficult if the lists are long. # katello -u admin -p **** errata system_group --name=<my_sys_grp> # katello -u admin -p **** repo list --org=<my_org> # katello -u admin -p **** product list # katello -u admin -p **** errata info --repo="Red Hat Enterprise Linux 6 Server RPMs i386 6.3" --product="Red Hat Enterprise Linux Server" --id=RHBA-2011:1395 In contrast, the first hit from a web search on "RHBA-2011:1395" returns http://rhn.redhat.com/errata/RHBA-2011-1395.html Version-Release number of selected component (if applicable): 1.1.2 How reproducible: always
1) We need to offer better searching from the CLI similar to Content Search in our webui 2) since errata should be unique by ID we also should also not require repo and product. If the errata exists in multiple repositories we should just show that in the details of the errata
getting rid of 6.0.0 version since that doesn't exist
in 6.1 you'll be able to do: hammer -u admin -p changeme erratum info --id='RHEA-2012:0056' You also can do just: hammer -u admin -p changeme erratum list to recieve errata across all orgs you have access to. (optionally you can pass org id).
The previous erratum info hammer command only showed about 4 or 5 fields, so I will add these fields as part of this bz: + field :severity, _("Severity") + field :updated, _("Updated") + field :description, _("Description") + field :summary, _("Summary") + field :solution, _("Solution")
Created redmine issue http://projects.theforeman.org/issues/8275 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/8275 has been closed ------------- Justin Sherrill Applied in changeset commit:hammer-cli-katello|c377a7ba5b3d0470ce8fa7787388bad871b4cd96.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** RHEL65 / RHEL7 Version Tested: foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-gce-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch foreman-vmware-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-release-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch foreman-postgresql-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch foreman-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-ovirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch foreman-libvirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-compute-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592