Bug 1464396
Summary: | Pool VMs console disconnect action revert to "lock screen" instead of "shutdown virtual machine" | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | paul |
Component: | General | Assignee: | Tomas Jelinek <tjelinek> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Vladimir <vshypygu> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.1.2.2 | CC: | bugs, michal.skrivanek, tjelinek, ylavi |
Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
The "console disconnect action" was not stored in ovf
Consequence:
After restart, the "console disconnect action" always reverted to the default, which is lock screen
Fix:
Added it to the ovf
Result:
Now the "console disconnect action" is preserved during restarts.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-22 09:58:39 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
paul
2017-06-23 10:52:39 UTC
Found out this happens when the machine is started as "stateless". It does not matter if this is done as an pre-started machine or as a machine started by user in the UserPortal. This has the unwanted implication these vms are not available anymore in the pool for other users (even if the user logged out) because of "strict user checking". According to [1] strict user checking is recommended ("Disable strict checking with caution, because you can expose the previous user's session to the new user.") [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/appe-reference_settings_in_administration_portal_and_user_portal_windows#sect-Explanation_of_Settings_in_the_New_Virtual_Machine_and_Edit_Virtual_Machine_Windows This actually happens also on normal stateless VMs (not only pooled ones). Targeting 4.2 Verified on 4.2.1.6-0.1.el7 Scenarios: 1. Create stateless VM with every console action, reboot vm multiple times, check that action stays the same - PASS 2. Create pool with every console action, reboot vms multiple times, check that action stays the same - PASS 3. Create usual VM with every console action, reboot vm multiple times, check that action stays the same - PASS This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |