Bug 1460304

Summary: Ansible Repository SCM Credential cannot be cleared after being set
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: James Wong <jwong>
Status: CLOSED ERRATA QA Contact: Dmitry Misharov <dmisharo>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: dclarizi, dmisharo, gblomqui, hkataria, jfrey, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ansible:ui:automate
Fixed In Version: 5.8.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1448483 Environment:
Last Closed: 2017-08-02 17:28:27 UTC Type: ---
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: 1448483    
Bug Blocks:    

Comment 2 CFME Bot 2017-06-09 15:56:14 UTC 
New commit detected on ManageIQ/manageiq/fine:
https://github.com/ManageIQ/manageiq/commit/46c68927589fe98e01a7793ee2495c51aac2bb6a

commit 46c68927589fe98e01a7793ee2495c51aac2bb6a
Author:     Greg Blomquist <blomquisg>
AuthorDate: Tue May 23 09:43:24 2017 -0400
Commit:     Satoe Imaishi <simaishi>
CommitDate: Fri Jun 9 11:51:35 2017 -0400

    Merge pull request #15029 from jameswnl/project-cred
    
    Allow Tower Project to reset credential
    (cherry picked from commit 4d1624833a316c9cf7c63b4ab1a17f9664679d96)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1460304

 .../configuration_script_source.rb                 |  6 ++++--
 .../configuration_script_source.rb                 | 25 +++++++++++++++++++---
 2 files changed, 26 insertions(+), 5 deletions(-)
Comment 3 Dmitry Misharov 2017-06-29 10:24:43 UTC 
Verified in 5.8.1.0.20170623170756_3ed4411. Credentials can e successfully removed from a repository.
Comment 5 errata-xmlrpc 2017-08-02 17:28:27 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-2017:1758