Bug 1316246

Summary:	[RFE] find out if foreman-installer --upgrade was run after yum update
Product:	Red Hat Satellite	Reporter:	Chris Roberts <chrobert>
Component:	Upgrades	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1.8	CC:	bkearney, dlobatog, ehelms, inecas, mbacovsk, mmccune, stbenjam
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged, UserExperience
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-22 13:24:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	260381, 1115190

Description Chris Roberts 2016-03-09 18:53:46 UTC

Description of problem:
When running a yum update with a minor release, alot of times the --upgrade flag is not run with katello-installer which can result in multiple issues.

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


How reproducible:


Steps to Reproduce:
1. install 6.1 latest then when next minor release comes out just do a yum update 

Actual results:
Satellite will experience issues at some point in the future.

Expected results:
have a way to verify if ## katello-installer --upgrade" was run after a yum update.

Additional info:

Comment 3 Daniel Lobato Garcia 2016-04-14 10:30:30 UTC

Not sure this is 'the fix' for this, but this might catch some errors on upgrade: https://github.com/theforeman/foreman/pull/3426

Comment 4 Stephen Benjamin 2016-10-14 13:50:48 UTC

Created redmine issue http://projects.theforeman.org/issues/16940 from this bug

Comment 5 Bryan Kearney 2018-06-22 13:24:45 UTC


*** This bug has been marked as a duplicate of bug 1459358 ***