diff --git a/modules/virt-runbook-nodestatusmaximagesexceeded.adoc b/modules/virt-runbook-nodestatusmaximagesexceeded.adoc
index 41bf2b0fe3..47f96ace0e 100644
--- a/modules/virt-runbook-nodestatusmaximagesexceeded.adoc
+++ b/modules/virt-runbook-nodestatusmaximagesexceeded.adoc
@@ -15,7 +15,7 @@
 This alert fires when a node exceeds the configured maximum number of images
 reported in the node status (default: 50). Once this limit is reached, the
 scheduler might not be able to accurately schedule new pods because the reported
-image count is wrong.
+image count is wrong. link:https://bugzilla.redhat.com/1984442[BZ#1984442]
 
 [discrete]
 [id="impact-nodestatusmaximagesexceeded"]
diff --git a/virt/support/virt-runbooks.adoc b/virt/support/virt-runbooks.adoc
index c382b2b62d..04640c547a 100644
--- a/virt/support/virt-runbooks.adoc
+++ b/virt/support/virt-runbooks.adoc
@@ -66,6 +66,8 @@ include::modules/virt-runbook-lowvirtoperatorcount.adoc[leveloffset=+1]
 
 include::modules/virt-runbook-networkaddonsconfignotready.adoc[leveloffset=+1]
 
+include::modules/virt-runbook-nodestatusmaximagesexceeded.adoc[leveloffset=+1]
+
 include::modules/virt-runbook-noleadingvirtoperator.adoc[leveloffset=+1]
 
 include::modules/virt-runbook-noreadyvirtcontroller.adoc[leveloffset=+1]