Bug 1623931 - "Unexpected error encountered" when switching VM console type and navigating
Summary: "Unexpected error encountered" when switching VM console type and navigating
Keywords:
Status: CLOSED DUPLICATE of bug 1574488
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.9.5
Assignee: Dávid Halász
QA Contact: Jad Haj Yahya
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-30 13:29 UTC by Antonin Pagac
Modified: 2018-09-04 13:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 10:33:17 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
excerpt from production.log (7.87 KB, text/plain)
2018-08-30 13:29 UTC, Antonin Pagac
no flags Details

Description Antonin Pagac 2018-08-30 13:29:41 UTC
Created attachment 1479812 [details]
excerpt from production.log

Description of problem:
If user navigates back to a VM after switching console type, an unexpected error appears. See reproduction steps.

Error text:
"param is missing or the value is empty: secret [vm_infra/launch_vmware_console]"

It seems the appliance is trying to use VM console that was previously configured. See also excerpt from production.log.

Version-Release number of selected component (if applicable):
5.9.4.7
occurs also in 5.8.5.0

How reproducible:
Always

Steps to Reproduce:
1. Have a vsphere provider added and a running VM present
2. Have at lease two working console types configured in appliance (VMRC, WebMKS)
3. Navigate to Compute -> Infrastructure -> Virtual Machines
4. Click on the VM to see its details; navigate Access -> VM console
5. It's not necessary to wait for console to connect
6. Navigate ta Administrator -> Configuration (for admin user)
7. Set the console type to a different one in section "VMware Console Support
"
8. Click on Compute to navigate back to the VM
9. Don't click on anything else, only Compute from the left menu
10. Error appears

Actual results:
VM details displayed

Expected results:
Unexpected error displayed

Additional info:
In 5.10. this seems to work fine; I don't think this is a blocker
Tested on Fedora 28, browser Google Chrome v. 68.0.3440.106


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