1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00

CNV -30825: add KubevirtHcoSingleStackIPv6

Signed-off-by: Avital Pinnick <apinnick@redhat.com>
This commit is contained in:
Avital Pinnick
2023-07-23 13:30:52 +03:00
committed by openshift-cherrypick-robot
parent 2cff3c59c0
commit 316002c81c
3 changed files with 59 additions and 2 deletions

View File

@@ -0,0 +1,56 @@
// Do not edit this module. It is generated with a script.
// Do not reuse this module. The anchor IDs do not contain a context statement.
// Module included in the following assemblies:
//
// * virt/monitoring/virt-runbooks.adoc
:_content-type: REFERENCE
[id="virt-runbook-KubevirtHcoSingleStackIPv6"]
= KubevirtHcoSingleStackIPv6
[discrete]
[id="meaning-kubevirthcosinglestackipv6"]
== Meaning
This alert fires when you install {VirtProductName} on a single stack
IPv6 cluster.
[discrete]
[id="impact-kubevirthcosinglestackipv6"]
== Impact
You cannot create virtual machines.
[discrete]
[id="diagnosis-kubevirthcosinglestackipv6"]
== Diagnosis
* Check the cluster network configuration by running the following command:
+
[,shell]
----
$ oc get network.config cluster -o yaml
----
+
The output displays only an IPv6 CIDR for the cluster network.
+
.Example output
+
[source,text]
----
apiVersion: config.openshift.io/v1
kind: Network
metadata:
name: cluster
spec:
clusterNetwork:
- cidr: fd02::/48
hostPrefix: 64
----
[discrete]
[id="mitigation-kubevirthcosinglestackipv6"]
== Mitigation
Install {VirtProductName} on a single stack IPv4 cluster or on a
dual stack IPv4/IPv6 cluster.

View File

@@ -85,7 +85,7 @@ Update the `HyperConverged` CR to enable automatic workload updates.
[id="stopping-a-vm-associated-with-a-non-live-migratable-vmi-outdatedvirtualmachineinstanceworkloads"]
=== Stopping a VM associated with a non-live-migratable VMI
* If a VMI is not live-migratable and if `runStrategy: Always` is
* If a VMI is not live-migratable and if `runStrategy: always` is
set in the corresponding `VirtualMachine` object, you can update the
VMI by manually stopping the virtual machine (VM):
+

View File

@@ -10,7 +10,6 @@ You can use the procedures in these runbooks to diagnose and resolve issues that
{VirtProductName} alerts are displayed on the *Virtualization* -> *Overview* -> xref:../../virt/getting_started/virt-web-console-overview.adoc#overview-overview_virt-web-console-overview[*Overview* tab] in the web console.
include::modules/virt-runbook-cdidataimportcronoutdated.adoc[leveloffset=+1]
include::modules/virt-runbook-cdidatavolumeunusualrestartcount.adoc[leveloffset=+1]
@@ -39,6 +38,8 @@ include::modules/virt-runbook-kubevirtcomponentexceedsrequestedmemory.adoc[level
include::modules/virt-runbook-kubevirtdeprecatedapirequested.adoc[leveloffset=+1]
include::modules/virt-runbook-kubevirthcosinglestackipv6.adoc[leveloffset=+1]
include::modules/virt-runbook-kubevirthyperconvergedclusteroperatorcrmodification.adoc[leveloffset=+1]
include::modules/virt-runbook-kubevirthyperconvergedclusteroperatorinstallationnotcompletedalert.adoc[leveloffset=+1]