Bug 1679875 - Validate the availability of gluster-ansible-roles before deployment
Summary: Validate the availability of gluster-ansible-roles before deployment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHHI-V 1.6
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1679687 1679876
Blocks: RHHI-V-1-6-Engineering-InFlight-BZs
TreeView+ depends on / blocked
 
Reported: 2019-02-22 06:17 UTC by Gobinda Das
Modified: 2019-05-09 06:09 UTC (History)
3 users (show)

Fixed In Version: cockpit-ovirt-0.12.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1679876 (view as bug list)
Environment:
Last Closed: 2019-05-09 06:09:09 UTC
Embargoed:

Attachments (Terms of Use)
Screenshot showing the warning that gluster-ansible is not available (30.65 KB, image/png)
2019-03-06 08:19 UTC, SATHEESARAN 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1121 0 None None None 2019-05-09 06:09:21 UTC

Description Gobinda Das 2019-02-22 06:17:42 UTC 
Description of problem:
 Now we don't have validation whether gluster ansible role is installed or not.If it's not installed then the deployment will fail without any message.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
 Should have valid message before deployment. 

Additional info:
Comment 4 SATHEESARAN 2019-02-27 11:49:21 UTC 
The dependent bug is ON_QA
Comment 5 SATHEESARAN 2019-03-06 08:18:56 UTC 
Tested with cockpit-ovirt-dashboard-0.12.4 and found that there is the warning,
when gluster-ansible-roles is not available in the setup
Comment 6 SATHEESARAN 2019-03-06 08:19:46 UTC 
Created attachment 1541240 [details]
Screenshot showing the warning that gluster-ansible is not available
Comment 8 errata-xmlrpc 2019-05-09 06:09:09 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/RHEA-2019:1121
Note You need to log in before you can comment on or make changes to this bug.