Bug 1754870 - "WARNING: Excluding 11574 updates due to foreman-protector." message scared me
Summary: "WARNING: Excluding 11574 updates due to foreman-protector." message scared me
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.8.0
Assignee: Lukáš Hellebrandt
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-24 09:30 UTC by Jan Hutař
Modified: 2023-09-07 20:39 UTC (History)
9 users (show)

Fixed In Version: rubygem-foreman_maintain-0.5.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:38:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28684 0 Normal Closed "WARNING: Excluding 11574 updates due to foreman-protector." message scared me 2020-11-20 17:45:15 UTC
Red Hat Product Errata RHBA-2020:4365 0 None None None 2020-10-27 12:38:41 UTC

Description Jan Hutař 2019-09-24 09:30:14 UTC
Description of problem:
IMO no admin should allow 12k updates being applicable on its system and this message is implying that:

    WARNING: Excluding 11574 updates due to foreman-protector.

I assume it should state:

-WARNING: Excluding 11574 updates due to foreman-protector.
+WARNING: Excluding 11574 packages due to foreman-protector.


Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-0.4.8-1.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. # yum repolist


Actual results:
[root@satellite tmp]# yum repolist | tee
Loaded plugins: foreman-protector, langpacks, product-id, search-disabled-repos,
              : subscription-manager

WARNING: Excluding 11574 updates due to foreman-protector. 
Use foreman-maintain packages install/update <package> 
to safely install packages without restrictions.

repo id                                                                   status
!Sat6-CI_Red_Hat_Satellite_6_6_Composes_Satellite_6_6_RHEL7                    0+421
Sat6-CI_Red_Hat_Satellite_6_6_Composes_Satellite_Maintenance_Next_RHEL7         2+13
!Sat6-CI_Red_Hat_Satellite_6_6_Composes_Satellite_Tools_6_6_RHEL7/x86_64        0+61
rhel-7-server-ansible-2.6-rpms/x86_64                                           0+24
rhel-7-server-rpms/7Server/x86_64                                         130+26,182
rhel-server-rhscl-7-rpms/7Server/x86_64                                     0+11,385
repolist: 132


Expected results:
Less scary messaging

Comment 3 Kavita 2020-01-08 12:21:03 UTC
Created redmine issue https://projects.theforeman.org/issues/28684 from this bug

Comment 5 Bryan Kearney 2020-02-27 09:03:34 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28684 has been resolved.

Comment 6 Lukáš Hellebrandt 2020-05-21 13:58:20 UTC
Verified with Sat 6.8 snap 1.

```
# yum install emacs
Loaded plugins: foreman-protector, product-id, search-disabled-repos, subscription-manager
[...]   

WARNING: Excluding 4609 packages due to foreman-protector. 
Use foreman-maintain packages install/update <package> 
to safely install packages without restrictions.
Use foreman-maintain upgrade run for full upgrade.

No package emacs available.
Error: Nothing to do
```

=> The message now correctly mentions packages and is less scary. Note, however, that running `yum update` has the same message with "packages" while it actually *does* block some updates so maybe it should be scary.

Comment 9 errata-xmlrpc 2020-10-27 12:38:20 UTC
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 (Satellite 6.8 Satellite Maintenance Release), 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/RHBA-2020:4365


Note You need to log in before you can comment on or make changes to this bug.