Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2064380

Summary: VNC Console: Operation Cancelled "Setting vm ticket failed" on engine 4.4.10.7
Product: [oVirt] ovirt-engine Reporter: D. Ercolani <licenze+RedHat>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.10.6CC: ahadas, ashwsing, bugs, fdelorey, fgarciad
Target Milestone: ovirt-4.5.0Flags: pm-rhel: ovirt-4.5?
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Since [libvirt 8](https://github.com/libvirt/libvirt/commit/27c1d06b5bd68bdce55efff0a50a15a30cb2a96b), a warning appears when providing a ticket with a password with length over than 8. Until now the extra characters were dropped silently in QEMU. But with libvirt new handling of longer passwords it causes the console trigger to fail. Now the password we will provided will be in the right length.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-21 12:43:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description D. Ercolani 2022-03-15 17:05:35 UTC
On engine 4.4.10.7
From web UI launching VNC or noVNC console on a VM:

from engine.log

2022-03-15 16:55:28,682Z ERROR [org.ovirt.engine.core.bll.SetVmTicketCommand] (default task-22) [64e416b3] Command 'org.ovirt.engine.core.bll.SetVmT
icketCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed t
o SetVmTicketVDS, error = General Exception: ('unsupported configuration: VNC password is 12 characters long, only 8 permitted',), code = 100 (Faile
d with error GeneralException and code 100)


searching in internet I found a possible explanation:
OK for info. It looks like libvirt 8 was accidentally included in the oVirt Node ISO 4.4.10 3rd March.
Therefore use the February one libvirt 7.10 or if you're using upstream then the following command will work for you:
dnf install libvirt-7.10.0

Comment 1 Arik 2022-03-21 12:43:07 UTC
We currently have no plan to release another 4.4.10 version of NODE
In 4.5 is is supposed to be fixed by https://gerrit.ovirt.org/c/ovirt-engine/+/118313

Comment 2 Sandro Bonazzola 2022-04-20 06:32:24 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.