Bug 1379408 - After adding a provider with an incorrect port, Updating to the correct port does not result in Provider Refresh Success
Summary: After adding a provider with an incorrect port, Updating to the correct port ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: Aparna Karve
QA Contact: Matt Mahoney
URL:
Whiteboard: hawkular
Depends On:
Blocks: 1388665
TreeView+ depends on / blocked
 
Reported: 2016-09-26 15:36 UTC by Matt Mahoney
Modified: 2019-08-06 20:05 UTC (History)
6 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1388665 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:50:28 UTC
Category: ---
Cloudforms Team: Middleware
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matt Mahoney 2016-09-26 15:36:45 UTC
Description of problem:
Added provider with the wrong port (with correct username creds), and then later updating the provider info to be that of the correct port did not result in a provider Refresh Success. The "Last Refresh" state remains at "Never"

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

How reproducible:
Always

Steps to Reproduce:
1. Add Provider, correct IP and user CREDS but with incorrect Port number
2. Click Validate button. CRED should NOT validate successfully
3. Click Add button
4. Navigate to Provider Summary/Detail view, and select Configuration->Refresh. Provider will stay in Status: "Never"
5. Select Configuration->Edit
6. Update Port number to be that of the valid port
7. Click Validate button. CRED should now validate successfully.
8, Click Save button
9. Navigate to Provider Summary/Detail view, and select Configuration->Refresh

Actual results:
Provider State remains "Never"

Expected results:
Provider State should reflect a successful Refresh

Additional info:

Comment 3 Aparna Karve 2016-10-24 21:57:37 UTC
Please verify if this is still an issue. Thanks.

Comment 4 Satoe Imaishi 2016-10-25 12:38:55 UTC
PR: https://github.com/ManageIQ/manageiq/pull/11673

Comment 6 Heiko W. Rupp 2016-10-28 09:05:14 UTC
This was merged and backported to Euwe


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