Problem:
I am not able to see the application errata’s in the Foreman Webui
Expected outcome:
It should show the errata status
Operating system is Centos but the content view which i have applied is contain : Centos7 and EPEL7 repositories. hence it should show the errata status.
Foreman and Proxy versions:
foreman-release-2.2.0-0.3.develop.el7.noarch
foreman-installer-2.0.1-1.el7.noarch
katello-3.15.3-1.el7.noarch
Foreman and Proxy plugin versions:
Distribution and version:
Centos 7
Other relevant data:
{root@client}{/root}
epel: download.nus.edu.sg
repo id repo name status
!Ansys_CentOS_CentOS CentOS7 10,070
!Ansys_EPEL_EPEL EPEL7 13,426
epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 13,426
foreman-client/x86_64 Foreman client nightly 16
repolist: 36,938
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, langpacks, product-id, subscription-manager
Do suggest how to get these errata (Bug,security,enhacnce) package details in the webui.
I have tried registering and subscribing again but that did not solve the problem.
irb(main):007:0> ForemanTasks.sync_task(::Actions::Katello::Host::GenerateApplicability, Host.all)
Traceback (most recent call last):
8: from lib/tasks/console.rake:5:in block in <top (required)>' 7: from (irb):7 6: from foreman-tasks (1.1.3) lib/foreman_tasks.rb:58:in sync_task’
5: from foreman-tasks (1.1.3) lib/foreman_tasks.rb:27:in trigger_task' 4: from foreman-tasks (1.1.3) lib/foreman_tasks.rb:48:in rails_safe_trigger_task’
3: from foreman-tasks (1.1.3) lib/foreman_tasks.rb:49:in block in rails_safe_trigger_task' 2: from foreman-tasks (1.1.3) lib/foreman_tasks.rb:29:in block in trigger_task’
1: from foreman-tasks (1.1.3) lib/foreman_tasks.rb:23:in `trigger’
RuntimeError (The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer)
For foreman-rake i got same error when i have tried earlier by googling. Please do suggest how to rectify it.
CentOS repositories don’t have errata. There are scripts to import errata for CentOS but if you don’t use those, there won’t be any errata.
EPEL repositories provide errata. If there is an update from EPEL pending it should show in errata.
Your screenshot is cut and incomplete. It’s not even visible, whether the sources are really from your katello server or maybe simply coming from the centos repositories directly. I have only checked a few of those shown, but those are all CentOS updates, i.e. without errata. Are you sure there are really EPEL updates pending? Only those would show errata unless you have imported errata for CentOS.
Check the products - repositories page for each product. It shows the number of total errata in the repositories. For CentOS you see 0. For EPEL you see something else.
All the packages which are getting listed those are coming from the Centos repository not the EPEL one.
[/uploads/default/original/2X/2/27772ff8ec2f908c93d7a144afa3ed2c3993aeac.png]
However, I am able to see the erratas available in the EPEL repository, please find the screen-shot below
Will it mean this should show the erratas in the webui and it should update the packages over the Centos 7 machine?
Also, as I have shared the foreman-rake console command output, can you please confirm is there any problem with the Setup which I have configured?
Appreciated your help .
If you don’t import CentOS errata then it won’t show any errata. Again: check the Products - Repository page for your CentOS product. It shows the number of errata imported into the repository. If it’s 0 then there won’t be any errata installable ever.
[quote=“ganesh.patil, post:5, topic:20130”]
However, I am able to see the erratas available in the EPEL repository, please find the screen-shot below
[/quote] I can’t see your screenshot. If there are EPEL updates pending on your server those should show up as availabla errata.
I got your point, but there are erratas in the EPEL 7 repository but those are not getting reflected, is it right behavior?
Also, what is the cause of error in foreman-rake console, can you please let me know if there is any issue with the setup.
Ganesh
If I wrote before: it depends on whether there are actually packages needing an update from EPEL 7. If all packages installed from EPEL7 are up to date on your server then there are obviously no installable/applicable packages nor errata. I can’t tell you what updates your server is missing…
