Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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

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

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