Bug 1379341 – restarting goferd on client forces applicability regeneration

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1379341 - restarting goferd on client forces applicability regeneration

Summary:	restarting goferd on client forces applicability regeneration

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	katello-agent (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	high Severity medium (vote)
Target Milestone:	GA
Target Release:	Unused
Assigned To:	satellite6-bugs
QA Contact:	Katello QA List
Docs Contact:

URL:
Whiteboard:
Keywords:	PrioBumpGSS, Triaged

Depends On:	1368677 1368746
Blocks:	1122832
	Show dependency tree / graph

Reported:	2016-09-26 08:27 EDT by Chris Duryee
Modified:	2018-02-21 07:57 EST (History)
CC List:	13 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Restarting the agent on the client forced package applicability calculations which were not necessary. This case has been fixed.
Story Points:	---
Clone Of:	1368746
Environment:
Last Closed:	2018-02-21 07:57:01 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	16209	None	None	None	2016-09-26 08:27 EDT
Red Hat Product Errata	RHBA-2018:0338	normal	SHIPPED_LIVE	Red Hat Satellite 6.3 Tools	2018-02-21 14:30:02 EST

Groups: None (edit)

Comment 2 Bryan Kearney 2016-09-26 10:19:26 EDT

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16209 has been resolved.

Comment 6 errata-xmlrpc 2018-02-21 07:57:01 EST

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.

https://access.redhat.com/errata/RHBA-2018:0338

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