Bug 1539431 - VMRC Console Access Fails with error "Console access failed: no console credentials defined"
Summary: VMRC Console Access Fails with error "Console access failed: no console crede...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.3
Assignee: Dávid Halász
QA Contact: Kedar Kulkarni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-28 22:04 UTC by Kedar Kulkarni
Modified: 2018-03-01 15:49 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-22 16:12:31 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
kkulkarn: automate_bug-


Attachments (Terms of Use)

Description Kedar Kulkarni 2018-01-28 22:04:47 UTC
Description of problem:
VMRC Console access is failing with following error message:
Console access failed: no console credentials defined

This happens when the VMware Remote Console Credentials are left blank in "Add Provider" step. Currently VMware Remote Console tab shows a message as:

Used for VMRC connections to all VMs in this provider. If not set, the credentials from the Default tab will be used. 

Hence, leaving creds blank should not be barred based on absence of console credentials.

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

How reproducible:
100%

Steps to Reproduce:
1.Add VMware Provider(Don't add VMRC console credentials)
2.Navigate to Infrastructure_> Virtual Machines
3.Select any running VM and try to access VM Console

Actual results:
Console access failed: no console credentials defined

Expected results:
Leaving creds blank should not be barred based on absence of console credentials.


Additional info:

Comment 3 Sudhir Mallamprabhakara 2018-01-31 03:28:17 UTC
Removed the need info and changed the version to 5.8.


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