Red Hat Bugzilla – Bug 964195
No 'WAN options' in Console options
Last modified: 2016-10-04 00:03:05 EDT
Description of problem:
In Console Options in Power User Portal should be checkbox for WAN options.
Version-Release number of selected component (if applicable):
RHEVM Tools 3.2.7
Steps to Reproduce:
1.Log into Power User Portal
2.Click to Edit Console options on VM where is RHEVM Agent and RHEVM Spice Agent installed and running
No checkbox for WAN options
THere is a checkbox for WAN options
it seems it's related to bug in GA, when the guest info wasn't reported (https://bugzilla.redhat.com/show_bug.cgi?id=962667). When the guest agent doesn't report its version, the engine supposes the GA is not installed and hides WAN options in the dialog. Could you test whether it is reportable with newer tools?
I've tried to install GA 3.2.8
Same result (WLAN option is missing)
If VDSM service is restarted on host, works as expected.
(In reply to Frantisek Kobzik from comment #1)
> it seems it's related to bug in GA, when the guest info wasn't reported
> (https://bugzilla.redhat.com/show_bug.cgi?id=962667). When the guest agent
> doesn't report its version, the engine supposes the GA is not installed and
> hides WAN options in the dialog. Could you test whether it is reportable
> with newer tools?
Frantisek, I am seeing this same issue with my customer on 2 separate environments both running RHEV-M 3.1.3 and vdsm-4.9-113.1 on DEV and vdsm-4.10.2-1.9 on PUREFLEX. I filed bug#967136 to report this.
however this was supposed to be fixed in 3.1.4.
Keep it open to investigate possible root cause bug 909059
remove 3.2.z request as bug 909059 is not going to happen any time soon. Still keep it open just in case we can reproduce it with some more information
all vdsm code is fixed and bug 909059 may or may not happen(it's a significant change and backport may be too risky) and we can't reproduce it to verify
on test build. We believe we fixed all what we can in vdsm
Lowering priority as after bug 972749 the impact is not that bad. Only the affected VM won't have guest agent data reported, and no vdsm restart is needed to make it work again. So one possible workaround is to simply reboot the machine or use live snapshot with RAM and suspend&resume
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
haven't seen that for a long time, please reopen if still relevant