Red Hat Knowledgebase
Welcome to Red Hat’s Knowledgebase information center. Find resources for resolving problems and troubleshooting. Log in to see all our solutions and articles. Some are restricted to verified users.
If you don’t have a Red Hat account yet, register and open one! For details about these accounts, see Developer Subscription Information or Customer Account Information.
Find what you need
Latest resources
Browse the latest published and updated knowledgebaseKernel Live Patch life cycles
This document is meant to be a resource for tracking the life cycle of Kernel Live patches, which CVEs they address, and their release date. For more information on which Red Hat Enterprise Linux versions have access to kernel live patching please see the [Is live kernel patch (kpatch) supported in Red Hat Enterprise Linux?](https://access.redhat.com/solutions/2206511) solution. For documentation on implementing kernel live patch please see the [Enabling kernel live patching](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/kernel_administration_guide/index#sect-enabling_kernel_live_patching) in the [Kernel Administration Guide](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/kernel_administration_guide/index).
Kernel panic at lpfc_dev_loss_tmo_callbk() with NULL pointer dereference after FC link down and up
+ The system panicked with a NULL pointer dereference in lpfc_dev_loss_tmo_callbk() after the FC links of an lpfc HBA went down and came back up. ``` [389.807380] rport-6:0-6: blocked FC remote port time out: removing rport [389.807386] rport-6:0-4: blocked FC remote port time out: removing rport [389.807388] rport-6:0-5: blocked FC remote port time out: removing rport [389.807390] rport-6:0-3: blocked FC remote port time out: removing rport [389.807391] rport-6:0-2: blocked FC remote port time out: removing rport [389.807393] rport-6:0-1: blocked FC remote port time out: removing rport [389.807394] rport-6:0-0: blocked FC remote port time out: removing rport [389.807397] **** lpfc_rport_invalid: Null vport on ndlp xff2377d8866cf200, DID xfffc01 rport xff2377d8866da000 SID xffffffff [389.807402] BUG: kernel NULL pointer dereference, address: 0000000000000000 [389.807403] #PF: supervisor read access in kernel mode [389.807404] #PF: error_code(0x0000)- not-present page [389.807406] PGD c124d59067 P4D 0 [389.807408] Oops: 0000 [#1] PREEMPT SMP NOPTI [389.807410] CPU: 48 PID: 997 Comm: kworker/48:1 Kdump: loaded Not tainted 5.14.0-570.119.1.el9_6.x86_64 #1 [389.807412] Hardware name: Dell Inc. PowerEdge R7725/0KRFPX, BIOS 1.7.6 05/04/2026 [389.807413] Workqueue: fc_wq_6 fc_rport_final_delete [scsi_transport_fc] [389.807423] RIP: 0010:lpfc_dev_loss_tmo_callbk+0x54/0x420 [lpfc] [389.807443] Code: 01 00 00 0f b7 8d b4 00 00 00 48 c7 c2 58 d4 12 c1 48 89 fb 44 8b 8d 98 00 00 00 44 8b 85 a0 00 00 00 be 80 00 00 00 4c 89 e7 <4d> 8b 2c 24 e8 93 04 04 00 48 8b 95 10 01 00 00 8b 82 2c 03 00 00 [389.807443] RSP: 0018:ff5f8ea41b553e20 EFLAGS: 00010286 [389.807445] RAX: ff2377d8866da538 RBX: ff2377d8866da000 RCX: 000000000000ffff [389.807446] RDX: ffffffffc112d458 RSI: 0000000000000080 RDI: 0000000000000000 [389.807446] RBP: ff2377d8866cf200 R08: 0000000000fffc01 R09: 0000000000000000 [389.807447] R10: ff5f8ea41b553d00 R11: ffffffffaa3e1888 R12: 0000000000000000 [389.807447] R13: ff2377d8866da000 R14: ff237894c4426000 R15: 0000000000000000 [389.807448] FS: 0000000000000000(0000) GS:ff2379579d400000(0000) knlGS:0000000000000000 [389.807448] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [389.807449] CR2: 0000000000000000 CR3: 000000030940e004 CR4: 0000000000771ef0 [389.807449] PKRU: 55555554 [389.807450] Call Trace: [389.807451] [389.807453]? show_trace_log_lvl+0x1c4/0x2df [389.807458]? show_trace_log_lvl+0x1c4/0x2df [389.807460]? fc_rport_final_delete+0xe7/0x1b0 [scsi_transport_fc] [389.807463]?__die_body.cold+0x8/0xd [389.807464]? page_fault_oops+0x134/0x170 [389.807467]?_prb_read_valid+0x81/0xe0 [389.807470]? exc_page_fault+0x62/0x150 [389.807472]? asm_exc_page_fault+0x22/0x30 [389.807477]? lpfc_dev_loss_tmo_callbk+0x54/0x420 [lpfc] [389.807487] fc_rport_final_delete+0xe7/0x1b0 [scsi_transport_fc] [389.807491] process_one_work+0x194/0x380 [389.807494] worker_thread+0x2fe/0x410 [389.807496]?__pfx_worker_thread+0x10/0x10 [389.807497] kthread+0xdd/0x100 [389.807498]?__pfx_kthread+0x10/0x10 [389.807499] ret_from_fork+0x29/0x50 [389.807502] [...] [389.807550] CR2: 0000000000000000 ```
ROSA HCP IDP login fails with "failed to initialize identity providers" or "failed to resolve name" due to konnectivity-agent unhealthy in kube-system
- ROSA HCP IDP login fails with "failed to initialize identity providers" or "failed to resolve name" due to konnectivity-agent unhealthy in kube-system
ROSA HCP 4.22: All NLB Targets Unhealthy (Target.FailedHealthChecks) After PROXY Protocol Enabled on Default IngressController
- On ROSA HCP clusters running OpenShift 4.22.x, all AWS Network Load Balancer(NLB) targets are marked unhealthy (Target.FailedHealthChecks) in the AWS Target Groups for the default IngressController. Custom NLB-type IngressControllers created on the cluster are also affected.
Instance creation randomly fails with "Failed to allocate the network(s), not rescheduling" due to flapping SR-IOV ports exhausting the Neutron event queue
- Instance creation fails intermittently and randomly due to `Failed to allocate the network(s), not rescheduling` error. WARNING nova.virt.libvirt.driver [...] [instance: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Timeout waiting for [(�39;network-vif-plugged�39;, ';bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb�39;)] for instance with vm_state building and task_state spawning: eventlet.timeout.Timeout: 300 seconds ERROR nova.virt.block_device [...] [instance: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Build of instance aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa aborted: Failed to allocate the network(s), not rescheduling.: nova.exception.BuildAbortException: Build of instance aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa aborted: Failed to allocate the network(s), not rescheduling.- `neutron-server` logs show an abnormally high rate of `OVN reports status up/down for port: ` messages (e.g.: tens of thousands per hour).: INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status down for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status down for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status down for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status up for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status up for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status down for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status down for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status up for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [...] OVN reports status down for port: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
Nodes transition to NotReady / processes stuck in D-state with Palo Alto Cortex XDR
- One or more worker nodes abruptly transition to a `NotReady` state.- Application pods on the affected nodes fail, remain in `ContainerCreating`, or report CNI errors.- The container runtime (`crio`) and `kubelet` stop logging or updating their status.- Multiple processes (such as `crio`, `ovnkube`, or `bash`) are stuck in uninterruptible sleep (`D`-state): ~~~ ps-eo state,pid,cmd | grep "^D" ~~~- Stack traces of blocked processes show them waiting indefinitely on `fanotify_get_response`.- System journals or `coredumpctl` show the Cortex XDR `pmd` agent process crashing (e.g., `SIGABRT`, `SIGSEGV`, or kernel traps) shortly before the node hangs: ~~~ coredumpctl list /opt/traps/bin/pmd ~~~
Virtual machines constantly live-migrate within a zone when nodes in other zones become schedulable with the KubeVirtRelieveAndMigrate descheduler profile
* VMs are repeatedly live-migrated between nodes of the same zone. * The migrations start when nodes in other zones are marked schedulable, and stop when those nodes are cordoned. * Many VirtualMachineInstanceMigration objects named kubevirt-evacuation-* are created. The same VMs often migrate back and forth between two nodes (A → B → A).
Certified OpenShift CNI Plug-ins
This article shows the CNI (Container Network Interface) plug-ins certified for use with Red Hat OpenShift Container Platform.
Trending
Solutions
Solve specific problems that has been raised with Red HatHPE Morpheus VM Essentials – Audio Device Support and Linux RDP Audio Workaround
When running Red Hat Enterprise Linux (RHEL) virtual machines under certain VM configurations, virtual PCI audio devices may present specific behavior and support limitations. This article outlines the support status for virtual PCI audio devices in HPE VM Essentials, known issues, and customer convenience workarounds using RDP audio.
Configuring Red Hat Ansible Automation Platform for Offline Use with Private Hub
- Control Plane Execution Environment misconfigured to registry.redhat.io - Internal registry hub not used for Execution Environments
Unable to load Virtio-Win Driver disks during Windows VM installation in OpenShift V...
- The user has attached the virtio-win driver disk but is unable to locate or load the correct drivers to proceed with the installation.
Articles
Technical briefs, reference architectures, and early stages of documentation(WIP)Why can't I download content from Red Hat Customer Portal download sections
Red Hat Customer Portal download access permissions
Optimizing ODF PersistentVolumes for Windows VMs
Red Hat OpenShift Virtualization can run virtual machines with Microsoft Windows. Red Hat OpenShift Data Foundation can provide PersistentVolumes which can be used as disks by virtual machines. A combination of the two products, and the use of Windows inside the VMs may benefit from tuning storage options for improving performance.
Red Hat Case Management - Attachment Service API Guide
This document is the API usage guide for the Red Hat Case Management Attachment Service. It covers authentication, upload (single part and multipart up to 5 TB), download, deletion, status tracking, and metadata listing for file attachments on Red Hat support cases. The intended audience is developers and integration engineers building clients that interact with the attachment APIs at `https://api.access.redhat.com/support`.
Latest discussions in the Red Hat Community
Ansible Automation Portal Appliance has no network connection
test
Get support
Support cases
Get answers quickly by opening a support case with us.
Live chat
Directly access our support engineers during weekday business hours.
Call or email
Speak directly with a Red Hat Support expert by phone or through email.
