Bug 1649222 - Failed to seal template of RHEL 8 guest
Summary: Failed to seal template of RHEL 8 guest
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.5
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1671895 1739583
Blocks: 1661283
TreeView+ depends on / blocked
 
Reported: 2018-11-13 07:56 UTC by SATHEESARAN
Modified: 2019-11-08 13:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1671895 (view as bug list)
Environment:
Last Closed: 2019-10-24 11:58:49 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2018-11-13 07:56:25 UTC
Description of problem:
------------------------
RHEL 8 guest was successfully created with RHHI-V 1.5 environment. While trying to make the template of this RHEL 8 guest with 'Seal Template' option, error was observed with 'Failed to seal the template' from RHV Manager UI

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHHI 1.5
    - RHV 4.2.7
    - RHGS 3.4.1

How reproducible:
------------------
Always

Steps to Reproduce:
--------------------
1. Create a RHEL 8 guest
2. Poweroff the VM
3. Make a template of this guest with 'Seal Template'

Actual results:
---------------
Failed to seal the template

Expected results:
-----------------
Successful sealing of template

Additional info:
-----------------

RHV Manager UI Events:
	
Nov 13, 2018, 1:05:38 PM
Failed to seal Template RHEL8_Template (VM: appvm02).

Comment 1 SATHEESARAN 2018-11-13 07:57:02 UTC
Snip from engine.log

<snip>

2018-11-13 13:05:35,079+05 INFO  [org.ovirt.engine.core.bll.VirtJobCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] Command SealVmTem
plate id: 'b356d40a-806d-4816-a95f-3d87ee8837a3': job 'fae09b9a-eb4d-4249-b189-b7be2a8ed92c' execution was completed with VDSM job status 'failed'
2018-11-13 13:05:35,083+05 INFO  [org.ovirt.engine.core.bll.VirtJobCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] Command SealVmTem
plate id: 'b356d40a-806d-4816-a95f-3d87ee8837a3': execution was completed, the command status is 'FAILED'
2018-11-13 13:05:36,085+05 ERROR [org.ovirt.engine.core.bll.SealVmTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-56) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] Ending comm
and 'org.ovirt.engine.core.bll.SealVmTemplateCommand' with failure.
2018-11-13 13:05:37,112+05 INFO  [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [78ed563b-9f16-46a7-9ba9-7fcf77864b
bc] Command 'AddVmTemplate' id: '8c4c86c9-628d-4f58-abff-199f934b922a' child commands '[067114b0-ec4c-4202-8a5e-b1662b1e5c3e, b356d40a-806d-4816-a95f-3d87ee8837a3]' executions were comp
leted, status 'FAILED'
2018-11-13 13:05:38,174+05 ERROR [org.ovirt.engine.core.bll.AddVmTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-29) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] Ending comma
nd 'org.ovirt.engine.core.bll.AddVmTemplateCommand' with failure.
2018-11-13 13:05:38,182+05 INFO  [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-29) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] START
, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='80d9f34e-5615-4ec5-8aeb-4a82b6a70e4a', status='Down', exitStatus='Normal'}), log id: 657e9ea6
2018-11-13 13:05:38,184+05 INFO  [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-29) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] FINIS
H, SetVmStatusVDSCommand, log id: 657e9ea6
2018-11-13 13:05:38,193+05 INFO  [org.ovirt.engine.core.bll.AddVmTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-29) [78ed563b-9f16-46a7-9ba9-7fcf77864bbc] Lock freed t
o object 'EngineLock:{exclusiveLocks='[654ca84c-62a6-4715-830e-bb7a18667ebb=DISK, RHEL8_Template=TEMPLATE_NAME, 7903571a-5093-4019-9fa5-a3322f76fd9c=TEMPLATE]', sharedLocks='[80d9f34e-5
615-4ec5-8aeb-4a82b6a70e4a=VM]'}'
2018-11-13 13:05:38,210+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-29) [78ed563b-9f16-46a7-9ba9-7fcf
77864bbc] EVENT_ID: USER_ADD_VM_TEMPLATE_SEAL_FAILURE(1,324), Failed to seal Template RHEL8_Template (VM: appvm02).

</snip>

Comment 2 Sahina Bose 2018-11-19 05:00:13 UTC
Can you clone this bug to RHV?

Comment 3 SATHEESARAN 2019-02-02 03:21:09 UTC
(In reply to Sahina Bose from comment #2)
> Can you clone this bug to RHV?

Hi Sahina,

Cloned this bug to oVirt - https://bugzilla.redhat.com/show_bug.cgi?id=1671895

Comment 4 SATHEESARAN 2019-02-04 06:50:43 UTC
The dependent oVirt bug is targeted for 4.3.2

Comment 6 Sahina Bose 2019-10-24 11:58:49 UTC
See dependent bug 1671895 - documentation has been added on how to seal templates


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