Description of problem:
There should be the advance search in manage errata page. We should be able to search the errata like (type = security).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Go to satellite web UI > Hosts > content hosts.
2. click on the check box of any content hosts > select action > manage errata
3. try to search (type = security).
No able to search.
should able to sort security errata.
This exists today. There is not an advanced checkbox, but you can type in things like 'type = security'
I updated today satellite with 6.4.1 but still it is not addressed.
Please reopen the bug again and make the permanent fix.
I also updated the redhat case with screenshot. Please check with support engineer for the screenshot.
Created redmine issue https://projects.theforeman.org/issues/26318 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26318 has been resolved.
Created attachment 1601885 [details]
*** Satellite 6.4.4 Hotfix Available ***
1) Download tfm-rubygem-katello-188.8.131.52-2.HOTFIXHRBZ1653293.el7sat.noarch.rpm from this bugzilla to your Satellite
rpm -Uvh tfm-rubygem-katello-184.108.40.206-2.HOTFIXHRBZ1653293.el7sat.noarch.rpm
foreman-maintain service restart
4) resume operations
Verified fix in Sat 6.6 snap 16
1. Created hosts that had applicable errata.
2. Content Hosts -> check content host boxes -> Select Action -> Manage Errata
3. Search for "type = security"
Security errata where filtered correctly. See attached screenshot
Created attachment 1605134 [details]
Screen shot of manage errata popup for when verifying bug
Thanks. I will check and let you know how it works in our environment.
It is not working after applying the patch and restarting the satellite.
Error: Web application not started
Undefined method 'post_exector_init' for no method error.
log attrached in redhat case. 02255581
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.