Document URL: Section Number and Name: Describe the issue: Bug 1859235 and bug 1856412 result with 2 templates for each OS, which may led to a VM created with terminationGracePeriodSeconds 0 (taken from the previous templates version). The new temlates have the correct value for terminationGracePeriodSeconds(fixed in bug 1861297) When a VM is created from common templates (or via the UI using the wizard), please verify that terminationGracePeriodSeconds is not 0. If it is, update is to 180 (linux-based) or 3600 (windows-based) in the VM yaml. Suggestions for improvement: Additional information:
@rnetser, is this intended as a release note?
@aspauldi - yes
@rnetser, what info are you waiting for from me?
@aspauldi - was just a response to https://bugzilla.redhat.com/show_bug.cgi?id=1875383#c1 Nothing is needed from my side.
There was an existing Release Note (BZ#1859237) about there being two versions of each common-template after upgrade. I've amended that and added a step for how to verify if a virtual machine has been created from an older version (terminationGracePeriod: 0), and also how to patch it with an appropriate value if necessary. PR: https://github.com/openshift/openshift-docs/pull/25685 Build: https://cnv-bz1875383-grace-period--ocpdocs.netlify.app/openshift-enterprise/latest/virt/virt-2-4-release-notes.html#virt-2-4-known-issues (3rd Known Issue from top) Ruth, can you please review. Thank you!
(In reply to Ruth Netser from comment #4) > @aspauldi - was just a response to > https://bugzilla.redhat.com/show_bug.cgi?id=1875383#c1 > Nothing is needed from my side. Thank you, Ruth!
Please see my comment in the PR.
Thanks Ruth PR updated: Added a note and slightly rewrote so that users with VMs created from common templates prior to upgrade will also pay attention to the workaround
Reviewed, added /lgtm in the PR
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Low: OpenShift Virtualization 2.4.2 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4201