Bug 1988460 - When applying an applicable errata on a host that is using a CV it does not generate a incremental CV version with REX turned on
Summary: When applying an applicable errata on a host that is using a CV it does not g...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.9.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: 6.10.0
Assignee: Ian Ballou
QA Contact: Akhil Jha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-30 15:21 UTC by Rudnei Bertol Jr.
Modified: 2022-01-25 21:02 UTC (History)
8 users (show)

Fixed In Version: tfm-rubygem-katello-4.1.1.17-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:12:53 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 33382 0 None None None 2021-08-31 15:18:32 UTC
Red Hat Knowledge Base (Solution) 6607941 0 None None None 2021-12-22 13:13:59 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:12:59 UTC

Description Rudnei Bertol Jr. 2021-07-30 15:21:49 UTC 
Description of problem:

When trying to apply an applicable errata on a host via: 'Content > Errata' the incremental content view that is triggered by default is not being triggered.

Version-Release number of selected component (if applicable):

6.8.6

How reproducible:

We were not able to reproduce on a Satellite, but we restored a backup from the server that we were facing this issue.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Will be provided on an internal update.
Comment 8 Justin Sherrill 2021-08-02 19:37:55 UTC 
The key to reproducing this issue is to turn Remote Execution on by default via the Administer > settings > content > 'Use remote execution by default' 

If that is set to 'yes', this should be easy to reproduce.
Comment 9 Justin Sherrill 2021-08-02 19:46:05 UTC 
Also a couple of workarounds:

* Apply the incremental update via hammer, then manually run the remote execution job
* set 'Use remote execution by default' to No/false and perform the incremental update, then manually run the remote execution job

I know that none of these are great workarounds and do not completely solve the issue, we will work on fixing it.

Justin
Comment 10 Rudnei Bertol Jr. 2021-08-02 19:48:36 UTC 
Hey Justin,

Thank you for your update here, I have suggested the customer disable the 'Use remote execution by default'.

regards
rbertol
Comment 15 Ian Ballou 2021-08-31 15:18:31 UTC 
Created redmine issue https://projects.theforeman.org/issues/33382 from this bug
Comment 16 Bryan Kearney 2021-09-01 00:05:28 UTC 
Upstream bug assigned to iballou
Comment 17 Bryan Kearney 2021-09-01 00:05:30 UTC 
Upstream bug assigned to iballou
Comment 18 Bryan Kearney 2021-09-09 16:05:01 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33382 has been resolved.
Comment 20 Akhil Jha 2021-09-27 07:26:36 UTC 
Verified. 
Satellite 6.10.0-20.0.

When trying to apply an applicable errata on a host via: 'Content > Errata' the incremental content view that is triggered by default.
Comment 23 errata-xmlrpc 2021-11-16 14:12:53 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 (Moderate: Satellite 6.10 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/RHSA-2021:4702
Note You need to log in before you can comment on or make changes to this bug.