From c3ea71068a4628d59ba690ca73c2193ed92af4e3 Mon Sep 17 00:00:00 2001 From: Pan Ousley Date: Mon, 13 Oct 2025 15:01:14 -0400 Subject: [PATCH] CNV#70576: known issue in 4.18.13 and bug fix for same in 4.18.17 --- .../virt-4-18-release-notes.adoc | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/virt/release_notes/virt-4-18-release-notes.adoc b/virt/release_notes/virt-4-18-release-notes.adoc index 5e1ba7c5b0b2..a7f29c822b29 100644 --- a/virt/release_notes/virt-4-18-release-notes.adoc +++ b/virt/release_notes/virt-4-18-release-notes.adoc @@ -263,3 +263,27 @@ You can also disable free page reporting of memory ballooning for all new VMs. T // cnv-56890 - threads * In the web console, it is erroneously possible to define multiple CPU threads for a VM based on s390x architecture. If you define multiple CPU threads, the VM enters a `CrashLoopBackOff` state with the error `qemu-kvm: S390 does not support more than 1 threads`. (link:https://issues.redhat.com/browse/CNV-56890[CNV-56890]) + +[id="virt-4.18-asynch-releases_{context}"] +== Maintenance releases + +Release notes for asynchronous releases of Red{nbsp}Hat {VirtProductName}. + +[id="virt-4.18.17_{context}"] +=== Version 4.18.17 + +.Bug fixes + +//CNV-70576: VM operations fail after update to 4.18.13 or below +* As of 4.18.17, updating from {VirtProductName} 4.17 to {VirtProductName} 4.18 no longer causes VM operations to fail. (link:https://issues.redhat.com/browse/CNV-69894[CNV-69894]) + +[id="virt-4.18.13_{context}"] +=== Version 4.18.13 + +.Known issues + +//CNV-70576: VM operations fail after update to 4.18.13 or below +* VM operations fail after updating from {VirtProductName} 4.17.27 to 4.18.13 and earlier 4.18 releases. The `virt-handler` pod logs show the error `unable to create virt-launcher client connection: can not add ghost record when entry already exists with differing socket file location`. (link:https://issues.redhat.com/browse/CNV-69894[CNV-69894]) +** To fix this issue, update to {VirtProductName} 4.18.17 or later. If you have a disconnected cluster, you might need to refresh your internal repositories first. ++ +For more information, see link:https://access.redhat.com/solutions/7131692[{VirtProductName}: VM operations fail after upgrade to 4.18 from 4.17.27 or above] in the Red{nbsp}Hat Knowledgebase.