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.

Created attachment 1439243 [details]
capsule status

Description of problem:
Warning sign on capsule status and hovering mouse on status UI says: core and proxy versions do not match

Satellite 1.18.0.0.7
foreman-proxy 1.18.0-develop


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

How reproducible:
always

Steps to Reproduce:
1. Install satellite
2. Go to "Infrastructure -> capsule" -> Status
3.

Actual results:
Warning sign on capsule status and hovering mouse on status UI says: core and proxy versions do not match

Satellite 1.18.0.0.7
foreman-proxy 1.18.0-develop

Expected results:
Status should be up with green tick

Additional info:

*** Bug 1585833 has been marked as a duplicate of this bug. ***

I'm marking this as duplicate, as this issue is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1500593

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