Bug 1253479 - WebUI: Credential fields missing while adding new foreman provider
Summary: WebUI: Credential fields missing while adding new foreman provider
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.5.0
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-13 19:18 UTC by Ramesh A
Modified: 2015-12-08 13:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:27:18 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Foreman Credential field missing (40.44 KB, image/png)
2015-08-13 19:18 UTC, Ramesh A
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Ramesh A 2015-08-13 19:18:53 UTC
Created attachment 1062800 [details]
Foreman Credential field missing

Description of problem:
Credential fields missing while adding new foreman provider

Version-Release number of selected component (if applicable):
master.20150813094605_98b8bee

How reproducible:
Very

Steps to Reproduce:
1. Navigate to Infrastructure ==> Configuration Management ==> Providers ==> All Foreman Providers ==> Configuration ==> Add a new Provider
2. Check for the credential field
3.

Actual results:
Credential fields are missing.  Refer the screenshot for more details

Expected results:
Credential field should be available

Additional info:

Comment 2 bmorriso 2015-10-15 18:25:11 UTC
Verified fixed in 5.5.0.6-beta1.2.20151014155446_ed40d96

Credential fields for foreman are present on the "Add Provider" page.

Comment 4 errata-xmlrpc 2015-12-08 13:27:18 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/RHSA-2015:2551


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