Bug 1580142

Summary: Warning sign on capsule status and hovering mouse on status UI says: core and proxy versions do not match
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: Foreman ProxyAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Nikhil Kathole <nkathole>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: ddolguik, inecas, mdekan, nkathole, omaciel, peter.vreman
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-14 13:01:12 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: 1122832, 1619394    
Attachments:
Description Flags
capsule status none

Description Sachin Ghai 2018-05-20 16:21:30 UTC
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:

Comment 2 Eric Helms 2018-06-11 11:20:28 UTC
*** Bug 1585833 has been marked as a duplicate of this bug. ***

Comment 6 Ivan Necas 2018-08-14 13:01:12 UTC
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 ***