CNV-26432: Update and assemble CNV 4.14 release notes#65340
CNV-26432: Update and assemble CNV 4.14 release notes#65340ousleyp merged 1 commit intoopenshift:enterprise-4.14from
Conversation
|
@aspauldi: This pull request references CNV-26432 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/label cnv |
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/30435 |
a3cb126 to
850939e
Compare
9903b55 to
0bf1e10
Compare
|
@stu-gott, is this text acceptable for the former Known issue that is now a bug fix? Windows 11 virtual machines now boot on clusters running in FIPS mode. (BZ#2089301) |
|
Yes
…On Wed, Oct 18, 2023 at 2:43 PM Audrey Spaulding ***@***.***> wrote:
@stu-gott <https://github.com/stu-gott>, is this text acceptable for the
former Known issue that is now a bug fix?
Windows 11 virtual machines now boot on clusters running in FIPS mode
<https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/security_hardening/index#con_federal-information-processing-standard-fips_assembly_installing-the-system-in-fips-mode>.
(BZ#2089301 <https://bugzilla.redhat.com/show_bug.cgi?id=2089301>)
—
Reply to this email directly, view it on GitHub
<#65340 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABYOC4SDN6DOMFFE5NYVH5DYAAPNBAVCNFSM6AAAAAA5JZJDJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGEZDCNBWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@aglitke, Is this text acceptable for the former Known issue that is now a bug fix? Maybe the comment about the VM status is no longer needed? When you use two pods with different SELinux contexts, VMs with the |
64e11e1 to
017723f
Compare
|
@aspauldi: This pull request references CNV-26432 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ousleyp
left a comment
There was a problem hiding this comment.
The RNs are really looking good! I didn't click every link since the individual notes were already reviewed. Just a few minor things to address. Thanks, Audrey!
81539ab to
aeedb4b
Compare
ousleyp
left a comment
There was a problem hiding this comment.
Just a few things to fix before merge. Thanks, Audrey!
| //4.14 Leave in per Adam | ||
| * In some instances, multiple virtual machines can mount the same PVC in read-write mode, which might result in data corruption. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1992753[*BZ#1992753*]) | ||
| ** As a workaround, avoid using a single PVC in read-write mode with multiple VMs. |
There was a problem hiding this comment.
This RN appears on line 275 as well, so one of them should be removed
| link:https://access.redhat.com/support/offerings/techpreview[Technology Preview Features Support Scope] | ||
|
|
||
| //CNV-27107 | ||
| * You can now install and edit xref:../../virt/virtual_machines/creating_vms/virt-creating-vms-from-rh-images.adoc#virt-creating-vm-instancetype_virt-creating-vms-from-rh-images[customized instance types] and preferences to create a VM from a volume or PersistentVolumeClaim (PVC). |
There was a problem hiding this comment.
It looks like this link needs to be updated so that it points to this page (possibly a recent restructuring - I didn't have it in my local copy of 4.14 until I rebased just now):
https://65340--docspreview.netlify.app/openshift-enterprise/latest/virt/virtual_machines/creating_vms_rh/virt-creating-vms-from-instance-types
I believe the correct xref is now:
xref:../../virt/virtual_machines/creating_vms_rh/virt-creating-vms-from-instance-types.adoc#virt-creating-vm-instancetype_virt-creating-vms-from-instance-types[customized instance types]
| //CNV-18298 force stop | ||
| * You can now force stop an unresponsive VM from the xref:../../virt/getting_started/virt-web-console-overview.adoc#virtualmachine-details-page_virt-web-console-overview[action menu]. To force stop a VM, select *Stop* and then *Force stop* from the action menu. | ||
| // CNV-29848: Release: Mechanism to manage DP/TP features in the UI | ||
| * Cluster administrators can enable or disable link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] features on the link:https://docs.openshift.com/container-platform/4.14/virt/getting_started/virt-web-console-overview.html#overview-settings-cluster_virt-web-console-overview[*Settings*] tab on the *Virtualization* -> *Overview* page. |
There was a problem hiding this comment.
This needs to be an xref, and I think it should point to the Settings tab (the current link actually points to the Cluster tab, which is in the Settings tab section). IIUC this should be the xref:
xref:../../virt/getting_started/virt-web-console-overview.adoc#overview-settings_virt-web-console-overview[*Settings*]
| //Known issues from 4.13 (and several carried over from 4.12) begin here.Leave in all for now; will be re-reviewed for 4.14. | ||
|
|
||
| //4.13 Leave in per Simone | ||
| * Uninstalling {VirtProductName} does not remove the `feature.node.kubevirt.io` node labels created by {VirtProductName}. You must remove the labels manually. (link:https://issues.redhat.com/browse/CNV-22036[*CNV-22036*]) |
There was a problem hiding this comment.
This RN is duplicated on line 272, so you can remove one of them
Version(s): 4.14
Issue: CNV-26432
Link to docs preview: https://65340--docspreview.netlify.app/openshift-enterprise/latest/virt/release_notes/virt-4-14-release-notes
QE review: Each of the release notes has been reviewed individually in the doc review process.
Additional information: