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

Bug 1512838

Summary: [RFE][UI] - Add indication that a template is a sealed template
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.VirtAssignee: Lucia Jelinkova <ljelinko>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: bugs, ljelinko, michal.skrivanek, mtessun, nsimsolo, rbarry, rdlugyhe
Target Milestone: ovirt-4.4.0Keywords: FutureFeature, Improvement
Target Release: ---Flags: pm-rhel: ovirt-4.4+
mtessun: planning_ack+
pm-rhel: devel_ack+
pm-rhel: testing_ack+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.0 gitb5b5c99ca2f Doc Type: Enhancement
Doc Text:
The current release adds a new capability: In the "Edit Template" window, you can use the "Sealed" checkbox to indicate whether a template is sealed. The Compute > Templates window has a new "Sealed" column, which displays this information.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:04:00 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 Michael Burman 2017-11-14 09:15:46 UTC 
Description of problem:
[UI] - Add indication that a template is a sealed template.

We now have the option to seal(Linux) a VM on template create, but we have no such indication in the UI that the template is a sealed one. 

If we have a multiple templates and some are sealed and some not, it's hard to know(almost not impossible) to figure out which template was sealed before creation(unless setting comment or description). 

I believe that such indication is pretty important and might be very useful to some admins/users.

We can add it -
By column or
By tooltip - like we have for stateless VMs or
By new icon or
By general info in the Template's 'General' sub tab with Sealed=true/false

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Create VM
2. Create a template from the VM and set 'Seal Template (Linux only)' by checking the checkbox and press 'OK'

Actual results:
Template created and sealed, but we have no indication that the template is a sealed one.
Comment 1 Red Hat Bugzilla Rules Engine 2018-07-06 14:57:13 UTC 
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
Comment 2 Michal Skrivanek 2020-03-18 13:46:57 UTC 
done?
Comment 3 Lucia Jelinkova 2020-03-19 11:41:14 UTC 
UI done but maybe I should add it to REST API too?
Comment 4 Ryan Barry 2020-03-19 13:59:16 UTC 
Ok by me to skip the REST part for this in particular
Comment 5 Nisim Simsolo 2020-03-25 11:00:37 UTC 
Verification version:
ovirt-engine-4.4.0-0.26.master.el8ev
vdsm-4.40.7-1.el8ev.x86_64
libvirt-daemon-6.0.0-13.module+el8.2.0+6048+0fa476b4.x86_64
qemu-kvm-4.2.0-15.module+el8.2.0+6029+618ef2ec.x86_64

Polarion TC added to external trackers
Comment 6 Sandro Bonazzola 2020-05-20 20:04:00 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.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.