Bug 1398094 - Default satellite version is set as 6.1 when we Open New Case from Satellite 6.2 GUI.
Summary: Default satellite version is set as 6.1 when we Open New Case from Satellite ...
Keywords:
Status: CLOSED DUPLICATE of bug 1403979
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Insights
Version: 6.2.4
Hardware: x86_64
OS: Linux
low
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 06:35 UTC by Amit Kumar Das
Modified: 2020-08-13 08:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 19:42:57 UTC
Target Upstream Version:


Attachments (Terms of Use)
Sat6.2.4 screenshot (58.64 KB, image/png)
2016-11-24 06:35 UTC, Amit Kumar Das
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2786401 0 None None None 2017-10-02 00:12:25 UTC

Description Amit Kumar Das 2016-11-24 06:35:48 UTC
Created attachment 1223521 [details]
Sat6.2.4 screenshot

Description of problem:

Default satellite version is set as 6.1 when we open new case from Satellite 6.2.4 GUI.

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

How reproducible:

a) Login to satellite 6.2.4 server.
b) Navigate to Red Hat Access>Open new case>It asks for Red Hat Customer Portal login details.
c) After logging in below are present as default

Product: Red Hat Satellite or Proxy
Product Version: 6.1

d) Even if you navigate via Red Hat Access>My Cases>Open a New Support Case

Default's are-
Product: Red Hat Satellite or Proxy
Product Version: 6.1

Actual results:
Default satellite version is set as 6.1 

Expected results:
Customer is expected default and current login version should be equal i.e 6.2

Comment 4 Bryan Kearney 2017-03-23 19:42:57 UTC
Closing this as a dupe of 1403979 since it will be fixed in that version.

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


Note You need to log in before you can comment on or make changes to this bug.