Bug 1775105 - Editing an embedded Ansible machine credential does not display the configured username for that credential
Summary: Editing an embedded Ansible machine credential does not display the configure...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.12.0
Assignee: Milan Zázrivec
QA Contact: Satyajit Bulage
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1788721
TreeView+ depends on / blocked
 
Reported: 2019-11-21 12:15 UTC by Peter McGowan
Modified: 2020-10-26 16:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1788721 (view as bug list)
Environment:
Last Closed: 2020-10-26 16:13:48 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter McGowan 2019-11-21 12:15:31 UTC
Description of problem:
Editing an embedded Ansible machine credential does not show the defined username for that credential, just an empty field.

Version-Release number of selected component (if applicable):
CFME 5.11.0.28
Chrome 78 (Mac)

How reproducible:
Every time


Steps to Reproduce:
1. In Automation -> Ansible -> Credentials, create a new credential of type 'Machine'.
2. Give the new credential a name, and username value, and a password, and save this.
3. Now edit the new credential from Configuration -> Edit this credential. 

Actual results:
Observe that the 'Username' field is empty

Expected results:
The Username field should display the configured username for that credential.

Additional info:

Comment 3 Milan Zázrivec 2019-12-17 15:37:54 UTC
This is in fact the same bug as is described in https://bugzilla.redhat.com/show_bug.cgi?id=1775093
although here it's manifested in a slightly different way.

This has been fixed in https://github.com/ManageIQ/manageiq-ui-classic/pull/6466

I'm moving this over to POST so that the bug can be properly verified.


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