how to create an outstanding patch per machine report for Satellite 6
Does anyone know how to create a report for Satellite 6 the will display the same type of information that is displayed when I go out the REDHAT and look at my classic registration list. It lists how many Errata and how may packages need to be applied to the registered host. We find this info useful for planning and checking on our patch needs. Is there any help out there with this as the books are not a real big help.
Bob
Responses
@matthias: That is for Satellite 5.
I have created a script for Satellite 6. See https://access.redhat.com/discussions/1395523.
There are still open tickets for a bunch of these kind of things (but also a load of resolved ones) in the Katello issue tracker.
http://projects.theforeman.org/projects/katello/issues
I'd certainly expect this kind of functionality in 6.1 with more to come later. I'm waiting for the ability to report outstanding errata for a Production system by looking at all Errata that have arrived in the Library. Reporting against the current environment is OK, but doesn't then show Errata that are still only in Dev or Test for example.
Untill 6.1 is release and if it is not bugged, you might want to use "yum updateinfo list available"
The old way, on all of your servers then parse the results.
Is this feature available in Redhat Satelite 6.2?
This is trivial to do with Satellite 6.2 and newer:
Firstly, get a list of hosts. use the hammer host list command. Optionally, provide a search query to limit the number of hosts to a host collection or other subset of hosts
#HOST_LIST=$(hammer --output csv host list --search "host_collection = Infrastructure"| cut -f 2 -d ','| tail --lines=+2)
Then given that list of hosts, show their errata
#for host in $HOST_LIST; do echo $host; hammer host errata list --host $host; done
auth01.example.com
---|------------|------|-------|------------
ID | ERRATUM ID | TYPE | TITLE | INSTALLABLE
---|------------|------|-------|------------
kvm01.example.com
---|------------|------|-------|------------
ID | ERRATUM ID | TYPE | TITLE | INSTALLABLE
---|------------|------|-------|------------
monitoring.example.com
---|------------|------|-------|------------
ID | ERRATUM ID | TYPE | TITLE | INSTALLABLE
---|------------|------|-------|------------
rhevm.example.com
------|----------------|----------|----------------------------------|------------
ID | ERRATUM ID | TYPE | TITLE | INSTALLABLE
------|----------------|----------|----------------------------------|------------
16931 | RHBA-2018:0597 | bugfix | tzdata enhancement update | true
16891 | RHSA-2018:0592 | security | Important: slf4j security update | true
------|----------------|----------|----------------------------------|------------
rhv-hypervisor1.example.com
------|----------------|--------|---------------------------|------------
ID | ERRATUM ID | TYPE | TITLE | INSTALLABLE
------|----------------|--------|---------------------------|------------
16931 | RHBA-2018:0597 | bugfix | tzdata enhancement update | true
16882 | RHBA-2018:0580 | bugfix | glusterfs bug fix update | true
------|----------------|--------|---------------------------|------------
rhv-hypervisor2.example.com
------|----------------|--------|---------------------------|------------
ID | ERRATUM ID | TYPE | TITLE | INSTALLABLE
------|----------------|--------|---------------------------|------------
16931 | RHBA-2018:0597 | bugfix | tzdata enhancement update | true
16882 | RHBA-2018:0580 | bugfix | glusterfs bug fix update | true
------|----------------|--------|---------------------------|------------
You can get creative with the API if you want, but this works too.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
