Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 1341660

Summary:	[RFE] capsule-installer to test if Satellite is of the same version than capsule
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1.8	CC:	chrobert, satellite6-bugs, stbenjam
Target Milestone:	Unspecified	Keywords:	FutureFeature, Improvement
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-09-04 19:07:40 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:

Description Pavel Moravec 2016-06-01 12:42:54 UTC

Description of problem:
Please add a test to the start of capsule-installer that will verify if Satellite version matches to-be-installed Capsule version.

User story:
- have a Satellite on some version for a long time
- have a sync plan updating capsules repos
- after few months, install a new capsule

The installation can fail due to so many various reasons. A check if Satellite and Capsule versions match will prevent debugging of really unexpected problem.


Version-Release number of selected component (if applicable):
Any Sat/Caps version (incl. 6.2 beta)


How reproducible:
100%


Steps to Reproduce:
- See user story above
- alternativelly, upgrade Sat but dont update Capsule repos such that you try to install old Capsule version under new version of Satellite


Actual results:
capsule-installer attempts to install Capsule (and optionally fails on hard-to-debug/understand issues)


Expected results:
capsule-installer to stop with warning Satellite/Capsule versions mismatch


Additional info:

Comment 3 Bryan Kearney 2016-07-08 20:38:04 UTC

Per 6.3 planning, moving out non acked bugs to the backlog

Comment 6 Pavel Moravec 2016-08-28 10:51:39 UTC

Another Satellite/Capsule version mismatch causing issues - not sure if worth fixing it here on via separate BZ.

Assume a customer upgraded Satellite only, leaving Capsules on older versions. That breaks various communication (i.e. pulp changes between 2.6.0.15-1 and 2.6.0.20-1 versions, even). But it is very tricky to identify this.

Can't a general way of "Sat/Caps check" help here? I.e. during some service startup that is upgraded on every Sat upgrade (foreman-proxy?), add version exchange and its check. If the check fails, the connecting service on Capsule is stopped with a fatal error log. And its already running peer on Sat will log an error "some peer tried to connect but it was on a different version - check it".

This approach will:
- stop capsule installer since a service wont start due to the fatal error (so it will fix this BZ)
- will give sufficient hints for the other use case (Sat upgraded, Caps not), since Caps will have the service down and Sat will have errors.

Does this seem feasible?

Comment 7 Stephen Benjamin 2016-10-14 16:21:34 UTC

We have the capsule status page, and could show the version or the capsule, and could prevent syncing, etc if it was incompatible.

But, pulp is breaking semver if the api changes in a patch level! They need BZ's opened to fix the regression.

Comment 8 Stephen Benjamin 2016-10-14 16:21:58 UTC

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

Comment 9 Bryan Kearney 2018-09-04 18:56:55 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 10 Bryan Kearney 2018-09-04 19:07:40 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.