Bug 1352054 - Parameters tab under Subnet is not working
Summary: Parameters tab under Subnet is not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: orabin
QA Contact: Stephen Benjamin
URL:
Whiteboard:
Depends On: 1296662
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-01 13:59 UTC by Jitendra Yejare
Modified: 2019-09-26 17:31 UTC (History)
7 users (show)

Fixed In Version: foreman-1.11.0.43-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:05:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
[Screenshot] Parameters tab selected but not accessible (47.11 KB, image/png)
2016-07-01 13:59 UTC, Jitendra Yejare
no flags Details

Description Jitendra Yejare 2016-07-01 13:59:32 UTC
Created attachment 1174938 [details]
[Screenshot] Parameters tab selected but not accessible

Description of problem:
Parameters tab in subnet is not working. The tab is selectable but not accessible to view/add/delete parameter.

Version-Release number of selected component (if applicable):
Sat 6.2 Snap 18.1 GA

How reproducible:


Steps to Reproduce:
1. Attempt to add parameter in subnet.

Actual results:
The parameter tab in Subnet is not working and not accessible.

Expected results:
The parameter should be working and accessible to add/view/remove parameters.

Additional info:

Comment 4 orabin 2016-07-01 17:17:45 UTC
Hi Jitendra,

What are the permissions for the user you are using?
Do you have any of the parameter permissions?

Comment 5 Jitendra Yejare 2016-07-04 06:50:51 UTC
Hey Ori,

The user is Admin, and so has access to everything including parameters.

Comment 7 Stephen Benjamin 2016-07-07 16:48:20 UTC
Verified in Satellite 6.2 Snap 19.0, foreman-1.11.0.43-1.el7sat.noarch

The incorrect parameters tab is no longer visible.

Comment 8 Bryan Kearney 2016-07-27 11:05:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501


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