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 knowledgebasebwrap fails with "Can't mkdir parents for
bwrap fails with "Can't mkdir parents for : Permission denied" after updating to bubblewrap-0.6.3-1.el9_9.1 Red Hat Enterprise Linux 9.9 bubblewrap-0.6.3-1.el9_9.1 (RHSA-2026:98521) A bwrap mount destination located below a directory that is traversable but not readable by the calling user (mode 0711, e.g. per-user home trees, pam_tmpdir / pam_mktemp $TMPDIR) After updating bubblewrap, sandboxes no longer start and the requested command is never executed: bwrap: Can't mkdir parents for /parent/user/workspace: Permission denied The same command worked with bubblewrap-0.6.3-1.el9_8.1. A corrected bubblewrap package for RHEL 9.9 is being prepared. Until it is available, downgrade to the 9.8 build, which already contains the complete CVE-2026-87766 fix and the follow-up correction: dnf downgrade bubblewrap-0.6.3-1.el9_8.1 dnf install python3-dnf-plugin-versionlock dnf versionlock add bubblewrap-0.6.3-1.el9_8.1 The version lock is required because the affected build has a higher NEVR and would otherwise be reinstalled by the next dnf update. Remove the lock once the corrected 9.9 package is released. This does not reduce security. bubblewrap-0.6.3-1.el9_8.1 is a Red Hat signed package that fully addresses CVE-2026-87766. IMPORTANT NOTE: relaxing the directory to 0755, or granting read with setfacl -m u::rx, also works but allows the user to list the contents of a directory that was deliberately made non-listable. Downgrade the version instead. The CVE-2026-87766 fix replaced the string-based creation of the mount destination with a file-descriptor-based path walk. In bubblewrap-0.6.3-1.el9_9.1, ensure_newroot_parents_at() opens each parent directory with O_DIRECTORY only: openat_in_root ("/newroot", , O_DIRECTORY) O_DIRECTORY implies O_RDONLY, so every component of the destination path must now be readable, whereas previously only search (+x) permission was needed. A root-owned 0711 ancestor therefore returns EACCES and bwrap aborts during setup. Upstream corrected this in commit c336e929 ("Use O_PATH when opening parent directories", containers/bubblewrap#806). Red Hat carries that correction as bubblewrap-0.6.3-CVE-2026-87766-followup.patch, which is applied in the 9.8 build but was missing from the 9.9 build — the latter was produced from an earlier source snapshot. References: * This bug is tracked under Jira: bubblewrap-0.6.3-1.el9_9.1: CVE-2026-87766 backport is missing the O_PATH follow-up patch * CVE-2026-87766: https://access.redhat.com/security/cve/cve-2026-87766 * RHSA-2026:98521, RHSA-2026:85309 * Upstream issue: https://github.com/containers/bubblewrap/issues/806 Confirm the ancestor is traversable but not readable: $ ls -ld /parent drwx--x--x. 3 root root 20 Nov 19 10:33 /parent Confirm the failing syscall: $ strace -f -e trace=openat2 bwrap --ro-bind / / --bind "$ws" "$ws" -- /bin/true openat2(4, "/parent", {flags=O_RDONLY|O_DIRECTORY, resolve=RESOLVE_NO_MAGICLINKS|RESOLVE_IN_ROOT}, 24) = -1 EACCES On an unaffected build the same call uses O_PATH and succeeds: openat2(4, "/parent", {flags=O_RDONLY|O_PATH|O_DIRECTORY, resolve=RESOLVE_NO_MAGICLINKS|RESOLVE_IN_ROOT}, 24) = 7 Confirm the trigger by temporarily testing with a readable ancestor (chmod 0755): the command succeeds, which isolates the parent-directory permission as the cause. bwrap fails with "Can't mkdir parents for : Permission denied" after updating to bubblewrap-0.6.3-1.el9_9.1
OpenWire Protocol is a deprecated feature for Red Hat AMQ 7
OpenWire Protocol is a deprecated feature for Red Hat AMQ 7 Red Hat AMQ - 7.x A Red Hat support person mentioned in a AMQ 7.8.x support case that the OpenWire protocol will be discontinued According to the 7.10 release notes OpenWire protocol Starting in 7.9, the OpenWire protocol is a deprecated feature. If you are creating a new AMQ Broker-based system, use one of the other supported protocols. This feature will be removed in a future release. What does that mean? The OpenWire protocol was deprecated as a result of the End of Life of AMQ 6 The deprecated state of OpenWire, signals we will not be adding any new features to the OpenWire protocol in AMQ 7 and customers should migrate to one of the more current protocols. Red Hat will continue to fix OpenWire protocol bugs in the broker, however clients adhere to the AMQ 6 product lifecycle. If there is a bug in the OpenWire client (not the broker) a support exception and an ELS subscription would be required to produce a fix, as these clients were productized with AMQ 6. There are currently no plans to remove the OpenWire protocol from AMQ 7.x. This will likely remain for migration purposes however support for this protocol will adhere to the limitations mentioned above. The OpenWire protocol was deprecated as a result of the End of Life of AMQ 6 OpenWire Protocol is a deprecated feature for Red Hat AMQ 7
Why df command has inaccuracies for automount filesystems in RHEL 9.x?
Why df command has inaccuracies for automount filesystems in RHEL 9.x? Red Hat Enterprise Linux 9.x (RHEL) automount (autofs) df command displays incorrect "Filesystem" and "Mounted On" information for automount targets on initial run; Executing the command again, shows the correct information: # df -hT /test/auth_sys_nfs Filesystem Type Size Used Avail Use% Mounted on /etc/auto.test autofs 4.9G 1.4G 3.5G 29% /test # df -hT /test/auth_sys_nfs Filesystem Type Size Used Avail Use% Mounted on rhel9-server:/nfs_export nfs4 4.9G 1.4G 3.5G 29% /test/auth_sys_nfs This is seen across all RHEL 9.x kernels. JIRA RHEL-180583 was raised for back porting the missing patch. An ERRATA RHBA-2026:97476 has now been released to fix this behavior. Please update coreutils to coreutils-8.32-43.el9 or later. The issue doesn't occur on RHEL 10+, since it already has the required patches. When df is run against automount paths on the command line, it triggers the automount but displays stale/incorrect filesystem information on the first run. The second run is correct because the filesystems are already mounted. coreutils-8.29 introduced a bug that mounts automount paths given on the command line, but still uses the device major/minor from the stat before the path was mounted. This results in incorrect mount point information in the output. The bug was introduced in the following commit: commit b04ce61958c1f1fc264950f8d3b6058f640ee491 Author: Pádraig Brady Date: 2017-10-29 15:29:05 -0700 df: fix hang with fifo argument * src/df.c (main): stat() before open(), and avoid the optional open when given a fifo argument. * tests/df/unreadable.sh: Add a test case. * NEWS: Mention the fix. Fixes https://bugs.gnu.org/29038 The fix for the bug is in the following commit, which is already included in RHEL 10+: commit a3c04f8da14f0fe2a0561bf5562032b8ce5dafa9 Author: Paul Eggert Date: 2021-08-11 11:16:05 -0700 df: fix bug with automounted If the command-line argument is automounted, df would use stat info that became wrong after the following open. * NEWS: Mention the fix (bug#50012). * src/df.c (automount_stat_err): New function. This fixes the hang on fifos in a better way, by using O_NONBLOCK. (main): Use it. The issue can be easily re-created using a simple configuration: Mount point: /test source(s): instance type(s): file map: /etc/auto.test auth_sys_nfs | -fstype=nfs,sec=sys rhel9-server:/nfs_export Execute df -h on the concerned path, which usually triggers a mount operation. It would not show accurate information, on the "Filesystem" and "Mounted on" fields: # df -hT /test/auth_sys_nfs Filesystem Type Size Used Avail Use% Mounted on /etc/auto.test autofs 4.9G 1.4G 3.5G 29% /test Execute df -h on the concerned path again. This time, the information is correct, because the filesystems are already mounted: # df -hT /test/auth_sys_nfs Filesystem Type Size Used Avail Use% Mounted on rhel9-server:/nfs_export nfs4 4.9G 1.4G 3.5G 29% /test/auth_sys_nfs Why df command has inaccuracies for automount filesystems in RHEL 9.x?
Virtual Machine snapshot fails immediately with "snapshot deadline exceeded" in OpenShift Virtualization
Virtual Machine snapshot fails immediately with "snapshot deadline exceeded" in OpenShift Virtualization Red Hat OpenShift Container Platform 4.x OpenShift Virtualization 4.x When attempting to create a snapshot of a Virtual Machine via the OpenShift Web Console UI or the command line, the snapshot operation fails immediately. Checking the status of the VirtualMachineSnapshot Custom Resource (CR) reveals that the snapshot is marked as Failed with the error snapshot deadline exceeded: status: conditions: - lastProbeTime: null lastTransitionTime: "2026-11-18T14:51:57Z" reason: snapshot deadline exceeded status: "True" type: Failure ... phase: Failed readyToUse: false Additionally, the vmsnapshotcontent object (which is normally created as one of the first steps during the snapshot operation) is never created, and the virt-controller logs do not provide any specific errors, they only show the snapshot getting stuck for exactly 5 minutes before failing due to the timeout. During a planned maintenance window, drain and reboot the cordoned node and correct its system time. As an immediate workaround, temporarily bypass the issue by forcing the virt-controller to schedule on a healthy node with correct time synchronization. Find out which node is currently running the active virt-controller pod: oc get pods -n openshift-cnv -l kubevirt.io=virt-controller -o wide Mark the node as unschedulable so the controller cannot be placed there again. oc adm cordon Delete the virt-controller pods. They will be automatically recreated and scheduled onto a different, healthy node. oc delete pods -n openshift-cnv -l kubevirt.io=virt-controller Create the VM snapshot again. It should now succeed. This failure occurs because the OpenShift node currently hosting the active virt-controller pod has an incorrect system time. When a VirtualMachineSnapshot is created, the Kubernetes API server stamps it with a creationTimestamp based on the master nodes' system time. The virt-controller evaluates this timestamp against its own local node time to enforce the 5-minute timeout window for snapshot operations. If the worker node hosting the virt-controller pod has a system clock that is running 5 minutes (or more) ahead of the cluster's master nodes, the virt-controller instantly calculates that the 5-minute deadline has already passed upon receiving the snapshot request. Consequently, the controller aborts the operation immediately and marks it as Failed with snapshot deadline exceeded, without ever attempting to create the vmsnapshotcontent. Start a watch on the vmsnapshot before creating the snapshot: while true;do oc get vmsnapshot rh-test-snap -o yaml -w |tee snapshot.log;done Create a snapshot named "rh-test-snap" and check if the status immediately goes into failed and compare the creationtimsteamp and status time when it marked the snapshot as failed. Virtual Machine snapshot fails immediately with "snapshot deadline exceeded" in OpenShift Virtualization
Ceph Storage in HEALTH_ERR after OpenShift Data Foundation (ODF) Upgrade - CephCluster/StorageCluster "phase: Error, CephClusterHealthNotOK, failed the ceph version check"
Ceph Storage in HEALTH_ERR after OpenShift Data Foundation (ODF) Upgrade - CephCluster/StorageCluster "phase: Error, CephClusterHealthNotOK, failed the ceph version check" Red Hat OpenShift Container Platform (RHOCP) v4.x Red Hat OpenShift Data Foundation (RHODF) v4.21 Red Hat OpenShift Data Foundation (RHODF) v4.22 StorageCluster in "phase: error - CephClusterHealthNotOK" CephCluster in "phase: error - failed the ceph version check" Ceph firing HEALTH_ERR "XX auth client entities with insecure key types" Ceph versions showing daemons were not upgraded Related Articles: After upgrade of ODF Health Warn all OSDs require_osd_release < "version" Fix will be provided in the following ODF versions ODF Version Bug Fixed Version 5.1 DFBUGS-11621 5.1.0 5.0 DFBUGS-12807 not yet 4.22 DFBUGS-12806 not yet 4.21 DFBUGS-12805 not yet 4.20 DFBUGS-12809 not yet 4.19 DFBUGS-12804 not yet 4.18 DFBUGS-12808 not yet NOTE. This table will be completed when fix is available on above versions. WORKAROUND - Until fix is available, proceed with below steps 1. Once the ODF reports HEALTH_OK as per below steps, please revert the skipUpgradeChecks: true setting using the below command. 2. It is not recommended to keep the parameter set post resolving of the health error $ oc patch storagecluster ocs-storagecluster -n openshift-storage --type=json -p '[{"op": "remove", "path": "/spec/managedResources/cephCluster/skipUpgradeChecks"}]' Confirm all CSVs are on the same version as the odf-operator and ALL have succeeded: $ oc get csv -n openshift-storage Set the CephCluster to skipUpgradeChecks: true and allow PLENTY of time for the rook-ceph components to upgrade. oc patch storagecluster ocs-storagecluster -n openshift-storage --type merge --patch '{"spec": {"managedResources": {"cephCluster": {"skipUpgradeChecks": true}}}}' NOTE: While watching $ oc get pods -n openshift-storage output, if there are no rook-ceph pods restarting/upgrading, delete the rook-ceph-operator pod. After ~25 minutes, check $ ceph -s and $ ceph versions. If step 2 allowed ODF to reconcile and Ceph is now in HEALTH_OK, STOP HERE. Only continue to step 4 if the Diagnostic Steps are still yielding the same failures. $ oc exec -it $(oc get pod -n openshift-storage -l app=rook-ceph-operator -o name) -n openshift-storage -- ceph status -c /var/lib/rook/openshift-storage/openshift-storage.config $ oc exec -it $(oc get pod -n openshift-storage -l app=rook-ceph-operator -o name) -n openshift-storage -- ceph versions -c /var/lib/rook/openshift-storage/openshift-storage.config You should only perform these next steps if steps 1-3 did not reconcile ODF/Ceph. Capture the desiredImage shown under the ceph image: oc get storagecluster -n openshift-storage -oyaml | grep -Ei "current|desired" -C10 images: ceph: actualImage: registry.redhat.io/rhceph/ desiredImage: registry.redhat.io/rhceph/ <--------------------- Scale down the rook-ceph-operator: $ oc scale deployment -n openshift-storage rook-ceph-operator --replicas=0 Upgrade each Ceph Daemon (just the main container, Rook should reconcile the rest): WARNING: Because this issue does not cause Client IO not to be served. To avoid losing access to storage ONLY perform these image upgrades one at a time, ONLY proceeding to the next Ceph Daemon when the previous daemon reflects a successful upgrade in $ ceph versions, and pod is fully up and "Running". a. Take a backup of the deployment yaml for each rook-ceph resource: $ mkdir -p rook-deploy-backup-$(date +%F) && cd $_ for d in $(oc get deployment -n openshift-storage -l 'app in (rook-ceph-mgr,rook-ceph-mon,rook-ceph-osd,rook-ceph-mds,rook-ceph-rgw)' -o jsonpath='{.items[*].metadata.name}'); do oc get deployment -n openshift-storage "$d" -o yaml > "$d.yaml"; done c. Upgrade the images *change deployment names to match environment): Syntax: mgr: oc -n openshift-storage set image deployment/ mgr=registry.redhat.io/rhceph/ mon: oc -n openshift-storage set image deployment/ mon=registry.redhat.io/rhceph/ mds: oc -n openshift-storage set image deployment/ mds=registry.redhat.io/rhceph/ osd: oc -n openshift-storage set image deployment/ osd=registry.redhat.io/rhceph/ rgw oc -n openshift-storage set image deployment/ rgw=registry.redhat.io/rhceph/ Validate all pods are successfully running and upgraded in Ceph: $ oc get pods -n openshift-storage $ oc exec -it $(oc get pod -n openshift-storage -l app=rook-ceph-operator -o name) -n openshift-storage -- ceph versions -c /var/lib/rook/openshift-storage/openshift-storage.config After validating step 7, scale up the rook-ceph-operator. Rook will reconcile the rest of the images in the deployments and reconcile Ceph on the backend. Please be patient during this reconciliation. $ oc scale deployment -n openshift-storage rook-ceph-operator --replicas=1 Revert skipUpgradeChecks: true to its default value (IMPORTANT) oc patch storagecluster ocs-storagecluster -n openshift-storage --type='json' -p='[{"op": "remove", "path": "/spec/managedResources/cephCluster/skipUpgradeChecks"}]' This issue is being tracked in DFBUGS-11621, that describes RCA: After mons are upgraded to a ceph version that support AES256K key, ceph reports AUTH_INSECURE_SERVICE_KEY_TYPE and AUTH_INSECURE_SERCVICE_TICKETS as heath error until the remaining daemons are upgraded and their keys are rotated. If the cluster reconciles/restarts in that window, for example due to operator restart, a reconcile error, or CR update, the upgrade check sees health error and refuses the upgrade. Now the upgrade is stuck but only an upgrade can clear this error. So we have deadlock. Fix still being worked, proposed PR core: don't block upgrade on cephx key type errors - #18759#18759 Check the CephCluster: $ oc get cephcluster -n openshift-storage -o yaml status: ceph: details: AUTH_INSECURE_CLIENT_KEY_TYPE: message: 10 auth client entities with insecure key types severity: HEALTH_WARN AUTH_INSECURE_KEYS_ALLOWED: message: Monitors are configured to allow auth using insecure key types severity: HEALTH_WARN AUTH_INSECURE_KEYS_CREATABLE: message: Monitors are configured to allow creation of insecure key types severity: HEALTH_WARN AUTH_INSECURE_ROTATING_SERVICE_KEY_TYPE: message: 4 rotating auth service keys using insecure key types severity: HEALTH_WARN AUTH_INSECURE_SERVICE_KEY_TYPE: message: 7 auth service entities with insecure key types severity: HEALTH_ERR AUTH_INSECURE_SERVICE_TICKETS: message: Monitors are configured to issue insecure service tickets
OpenTelemetry Traces Are Not Exported to Tempo in Red Hat Openshift AI 3.5.3
OpenTelemetry Traces Are Not Exported to Tempo in Red Hat Openshift AI 3.5.3 Product: Red Hat OpenShift AI (RHOAI) Version: 3.5.3 Component: OpenTelemetry Collector and Tempo Feature: Distributed Tracing / Observability When configuring distributed tracing for an application using OpenTelemetry in Red Hat OpenShift AI 3.5.3, traces may be successfully received by the OpenTelemetry Collector but fail to reach the Tempo backend. As a result, expected tracing information may not be available in the observability interface. Temporary Workaround: To temporarily restore trace export functionality, add the required gRPC port mapping to the Tempo Gateway Service using the following command: $ oc patch svc tempo-data-science-tempostack-gateway \ -n redhat-ods-monitoring \ --type=json \ -p '[ { "op": "add", "path": "/spec/ports/-", "value": { "name": "otlp-grpc", "port": 4317, "protocol": "TCP", "targetPort": "grpc-public" } } ]' This workaround adds port 4317 to the Tempo Gateway Service and maps it to the existing grpc-public target port. The Tempo Operator reconciliation process may revert this manual modification. If the modification is reverted, the command may need to be reapplied. This is a temporary workaround and not a permanent product fix. This issue is caused by an incorrect Tempo Gateway endpoint configuration generated by the RHOAI operator. The configured endpoint does not match the actual gRPC ingestion port exposed by the Tempo Gateway, resulting in connection failures during trace export. OpenTelemetry Traces Are Not Exported to Tempo in Red Hat Openshift AI 3.5.3
Kernel panic at selinux_inode_free_security+0x52
Kernel panic at selinux_inode_free_security+0x52 Red Hat Enterprise Linux 3rd party module cbsensor Kernel panic with following logs: [2095622.767550] cbsensor: file-process-tracking.c:149: Fail to delete inode=65798148, pid=773615 from hash table [2095622.782248] cbsensor: file-process-tracking.c:149: Fail to delete inode=65798148, pid=773615 from hash table [2096980.710028] general protection fault: 0000 [#1] SMP [2096980.710543] last sysfs file: /sys/module/ipv6/initstate [2096980.710800] CPU 28 [2096980.710808] Modules linked in: iptable_filter ip_tables tcp_diag inet_diag mpt2sas scsi_transport_sas raid_class mptctl mptbase ipmi_devintf dell_rbu cbsensor(P)(U) sunrpc bonding ipv6 power_meter acpi_ipmi ipmi_si ipmi_msghandler microcode iTCO_wdt iTCO_vendor_support dcdbas joydev sg bnx2x ptp pps_core libcrc32c mdio sb_edac edac_core lpc_ich mfd_core ext4 jbd2 mbcache sd_mod crc_t10dif megaraid_sas wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] [2096980.713072] [2096980.713323] Pid: 483, comm: kswapd0 Tainted: P -- ------------ 2.6.32-754.33.1.el6.x86_64 #1 Dell Inc. PowerEdge R720xd/0020HJ [2096980.713861] RIP: 0010:[] [] selinux_inode_free_security+0x52/0x90 [2096980.714410] RSP: 0018:ffff88204f43fb70 EFLAGS: 00010206 [2096980.714668] RAX: ffff881f20586788 RBX: ffff881f20586780 RCX: 3030303030303064 [2096980.715181] RDX: ffff881f20586470 RSI: ffff881e58ee7700 RDI: ffff88404f50e6a0 [2096980.715718] RBP: ffff88204f43fb90 R08: 0038000000000000 R09: e189191f3b81c007 [2096980.716253] R10: 0000000000000000 R11: 0000000000000000 R12: ffff881e58ee74e8 [2096980.716765] R13: ffff88404f50e6a0 R14: ffffffff81ffa740 R15: ffff881e58ee74f8 [2096980.717266] FS: 0000000000000000(0000) GS:ffff880120f80000(0000) knlGS:0000000000000000 [2096980.717792] CS: 0010 DS: 0018 ES: 0018 CR0: 0000000080050033 [2096980.718144] CR2: 000000000042e110 CR3: 0000000001a8e000 CR4: 00000000001607e0 [2096980.718640] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [2096980.719162] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [2096980.719688] Process kswapd0 (pid: 483, threadinfo ffff88204f43c000, task ffff88204f434ab0) [2096980.720192] Stack: [2096980.720440] ffff88204f43fb70 ffff881e58ee74e8 ffff88204f43fc50 000000000000002e [2096980.720728] ffff88204f43fbb0 ffffffff8124628c ffffffff81ffa740 ffff881e58ee74e8 [2096980.721263] ffff88204f43fbd0 ffffffff811c0a02 ffff881e58ee7700 ffff881e58ee74e8 [2096980.722029] Call Trace: [2096980.722286] [] security_inode_free+0x2c/0x40 [2096980.722547] [] __destroy_inode+0x22/0xa0 [2096980.722806] [] destroy_inode+0x16/0x60 [2096980.723064] [] dispose_list+0xb7/0x120 [2096980.723327] [] shrink_icache_memory+0x274/0x2e0 [2096980.723595] [] shrink_slab+0x146/0x1b0 [2096980.723859] [] balance_pgdat+0x58a/0x820 [2096980.724119] [] ? calculate_pressure_threshold+0x26/0x50 [2096980.724409] [] kswapd+0x134/0x3c0 [2096980.724681] [] ? autoremove_wake_function+0x0/0x40 [2096980.724941] [] ? kswapd+0x0/0x3c0 [2096980.725205] [] kthread+0xa0/0xc0 [2096980.725463] [] child_rip+0x20/0x30 [2096980.725720] [] ? kthread+0x0/0xc0 [2096980.725989] [] ? child_rip+0x0/0x30 [2096980.726258] Code: 49 89 fc 4c 8b a8 c0 00 00 00 49 83 c5 60 4c 89 ef e8 33 d5 30 00 48 8b 53 08 48 8d 43 08 48 39 d0 74 13 48 8b 4b 10 48 89 4a 08 <48> 89 11 48 89 43 08 48 89 43 10 4c 89 e8 66 ff 00 66 66 90 49 [2096980.727328] RIP [] selinux_inode_free_security+0x52/0x90 [2096980.727594] RSP Please contact a vendor of 3rd party module cbsensor for further assistance. Check if issue still persists with module cbsensor being unloaded. There might be a possibility that the memory corruption is involved in 3rd party module. vmcore analysis: KERNEL: /cores/retrace/repos/kernel/x86_64/usr/lib/debug/lib/modules/2.6.32-754.33.1.el6.x86_64/vmlinux DUMPFILE: /cores/retrace/tasks/603978846/crash/vmcore [PARTIAL DUMP] CPUS: 32 DATE: Sun Nov 8 16:30:07 GMT 2020 UPTIME: 24 days, 06:16:45 LOAD AVERAGE: 19.22, 16.92, 20.76 TASKS: 2348 RELEASE: 2.6.32-754.33.1.el6.x86_64 VERSION: #1 SMP Mon Aug 10 10:29:45 EDT 2020 MACHINE: x86_64 (2600 Mhz) MEMORY: 256 GB PANIC: "[2096980.710028] general protection fault: 0000 [#1] SMP " PID: 483 COMMAND: "kswapd0" TASK: ffff88204f434ab0 [THREAD_INFO: ffff88204f43c000] CPU: 28 STATE: TASK_RUNNING (PANIC) DMI: Dell Inc. PowerEdge R720xd/0020HJ, BIOS 2.9.0 12/06/2019 [ 0.109505] CPU0: Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz stepping 04 [ 6.828794] microcode: CPU0 sig=0x306e4, pf=0x1, revision=0x42e [2095622.767550] cbsensor: file-process-tracking.c:149: Fail to delete inode=65798148, pid=773615 from hash table [2095622.782248] cbsensor: file-process-tracking.c:149: Fail to delete inode=65798148, pid=773615 from hash table [2096980.710028] general protection fault: 0000 [#1] SMP [2096980.710543] last sysfs file: /sys/module/ipv6/initstate [2096980.710800] CPU 28 [2096980.710808] Modules linked in: iptable_filter ip_tables tcp_diag inet_diag mpt2sas scsi_transport_sas raid_class mptctl mptbase ipmi_devintf dell_rbu cbsensor(P)(U) sunrpc bonding ipv6 power_meter acpi_ipmi ipmi_si ipmi_msghandler microcode iTCO_wdt iTCO_vendor_support dcdbas joydev sg bnx2x ptp pps_core libcrc32c mdio sb_edac edac_core lpc_ich mfd_core ext4 jbd2 mbcache sd_mod crc_t10dif megaraid_sas wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] [2096980.713072] [2096980.713323] Pid: 483, comm: kswapd0 Tainted: P -- ------------ 2.6.32-754.33.1.el6.x86_64 #1 Dell Inc. PowerEdge R720xd/0020HJ [2096980.713861] RIP: 0010:[] [] selinux_inode_free_security+0x52/0x90 [2096980.714410] RSP: 0018:ffff88204f43fb70 EFLAGS: 00010206 [2096980.714668] RAX: ffff881f20586788 RBX: ffff881f20586780 RCX: 3030303030303064 [2096980.715181] RDX: ffff881f20586470 RSI: ffff881e58ee7700 RDI: ffff88404f50e6a0 [2096980.715718] RBP: ffff88204f43fb90 R08: 0038000000000000 R09: e189191f3b81c007 [2096980.716253] R10: 0000000000000000 R11: 0000000000000000 R12: ffff881e58ee74e8 [2096980.716765] R13: ffff88404f50e6a0 R14: ffffffff81ffa740 R15: ffff881e58ee74f8 [2096980.717266] FS: 0000000000000000(0000) GS:ffff880120f80000(0000) knlGS:0000000000000000 [2096980.717792] CS: 0010 DS: 0018 ES: 0018 CR0: 0000000080050033 [2096980.718144] CR2: 000000000042e110 CR3: 0000000001a8e000 CR4: 00000000001607e0 [2096980.718640] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [2096980.719162] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [2096980.719688] Process kswapd0 (pid: 483, threadinfo ffff88204f43c000, task ffff88204f434ab0) [2096980.720192] Stack: [2096980.720440] ffff88204f43fb70 ffff881e58ee74e8 ffff88204f43fc50 000000000000002e [2096980.720728] ffff88204f43fbb0 ffffffff8124628c ffffffff81ffa740 ffff881e58ee74e8 [2096980.721263] ffff88204f43fbd0 ffffffff811c0a02 ffff881e58ee7700 ffff881e58ee74e8 [2096980.722029] Call Trace: [2096980.722286] [] security_inode_free+0x2c/0x40 [2096980.722547] [] __destroy_inode+0x22/0xa0 [2096980.722806] [] destroy_inode+0x16/0x60 [2096980.723064] [] dispose_list+0xb7/0x120 [2096980.723327] [] shrink_icache_memory+0x274/0x2e0 [2096980.723595] [] shrink_slab+0x146/0x1b0 [2096980.723859] [] balance_pgdat+0x58a/0x820 [2096980.724119] [] ? calculate_pressure_threshold+0x26/0x50 [2096980.724409] [] kswapd+0x134/0x3c0 [2096980.724681] [] ? autoremove_wake_function+0x0/0x40 [2096980.724941] [] ? kswapd+0x0/0x3c0 [2096980.725205] [] kthread+0xa0/0xc0 [2096980.725463] [] child_rip+0x20/0x30 [2096980.725720] [] ? kthread+0x0/0xc0 [2096980.725989] [] ? child_rip+0x0/0x30 [2096980.726258] Code: 49 89 fc 4c 8b a8 c0 00 00 00 49 83 c5 60 4c 89 ef e8 33 d5 30 00 48 8b 53 08 48 8d 43 08 48 39 d0 74 13 48 8b 4b 10 48 89 4a 08 <48> 89 11 48 89 43 08 48 89 43 10 4c 89 e8 66 ff 00 66 66 90 49 [2096980.727328] RIP [] selinux_inode_free_security+0x52/0x90 [2096980.727594] RSP crash> bt PID: 483 TASK: ffff88204f434ab0 CPU: 28 COMMAND: "kswapd0" #0 [ffff88204f43f900] machine_kexec at ffffffff8104179b #1 [ffff88204f43f960] crash_kexec at ffffffff810d7a12 #2 [ffff88204f43fa30] oops_end at ffffffff81560310 #3 [ffff88204f43fa60] die at ffffffff8100f9cb #4 [ffff88204f43fa90] do_general_protection at ffffffff8155fdf2 #5 [ffff88204f43fac0] general_protection at ffffffff8155f235 [exception RIP: selinux_inode_free_security+82] RIP: ffffffff81250892 RSP: ffff88204f43fb70 RFLAGS:
Common User Management Questions
Common User Management Questions FAQ for Red Hat Customer Account Management Questions Note: Only Organization Administrators can manage users on an account. Contents How do I add a new user to my account? How do I manage users and user access in Hybrid Cloud Console(HCC)? Can I add an existing user under a different account to my account? What is auto-user registration (self-service account onboarding)? What are the Customer Portal Roles and Permissions? Can I have a user to see certain subscriptions only? Is there a limit to the number of users I can invite? How do I update or change permissions for an existing user? I am an Organization Administrator. How can I update other users' name/phone number/(email)address? How do I deactivate a user? What is the difference between deactivating and deleting a Red Hat login ID? The Organization Administrator of our company's account is no longer employed with our company. How do I gain access to that account? I have a login ID under my company's account, but when I try to access the Subscriptions/Systems page on the Customer Portal, I get a message that says "Active Subscription Required"/"Subscription Required". Why? I have a login ID under my company's account, but when I try to access the Downloads page for a specific product on the Customer Portal, I encounter an access restriction. Why? I have a login ID under my company's account, but when I try to access the Support cases page on the Customer Portal, I get a message that says "Support subscription Required. The credentials you provided are valid, but you do not have direct support from Red Hat" Why? I have a login ID under my company's account, but when I try to open a support case, I can only see 2 Products(Red Hat Customer Portal and Red Hat Integration-Service Registry) in the list. Why is it? I have a login ID under my company's account, but when I try to access the Download’s page for a specific product on the Customer Portal, I get a message that says I do not have the correct permissions. Why? I created an account for myself on the Customer Portal, but I cannot see my company's existing subscriptions. What's wrong? How do I make an existing user an administrator? How can I be added to my company's existing account? When I try to log into the Customer Portal, I get a message that says my login ID is inactive. What happened? I am an Organization Administrator, can I change other users' passwords? I want to have my login ID deleted. How can I do that? Can I reuse my login ID once it’s deleted? How do I add a new user to my account? Only an Organization Administrator (Org Admin) can invite new users to an account and manage user access. Org Admins can manage existing users, invite new users, and assign access permissions through the Hybrid Cloud Console (HCC). How to invite a new user Sign in to the Hybrid Cloud Console. Navigate to Settings → User Access → Users. Select the option to invite a new user. Enter the email address of the user you want to invite. Assign the appropriate access permissions to the user. Available permissions include Manage Support Cases, which allows users to view, create, and update support cases. Send the invitation. What happens after the invitation is sent? The invited user will receive an invitation email from Red Hat. The invitation email has the subject "You've been invited to join a Red Hat account." and is sent from no-reply@redhat.com. Make sure that emails from no-reply@redhat.com are not blocked by your email system. If the invitation email is not received, check the spam or junk mail folder. The user must follow the instructions in the invitation email to complete the registration process and create a Red Hat login ID, if required. Once registration is complete, the user can sign in to Red Hat Customer Portal using their login ID and the permissions assigned by the Org Admin. Additional information An existing login ID cannot be added to another account or transferred between accounts. If a user with an existing login ID needs access to another account, a new login ID must be created through an invitation from that account's Org Admin. Note: The "Download Software and Updates" permission is no longer required to download software and updates from the Customer Portal. Downloads remain subject to active subscription and export compliance requirements. Back to Top How do I manage users and user access in Hybrid Cloud Console (HCC)? User access in Hybrid Cloud Console is managed separately from Customer Portal user permissions. Organization Administrators can manage user access to Red Hat services and applications through the User Access section in Hybrid Cloud Console. To manage users and their access: Log in to Hybrid Cloud Console. Navigate to Settings > User Access > Users. Select the user whose access you want to manage. Review or modify the user's assigned roles and permissions as appropriate. For more information, refer to the User Access Configuration Guide for Role-based Access Control (RBAC). Back to Top Can I add an existing user under a different account to my account? Login ID cannot be moved to a different account Login ID also cannot be re-used once deleted If the user with a specific login ID already exists under a different account, the same login ID cannot be added. A new login ID must be created. Organization Administrator of the account can Invite New Users from Red Hat Hybrid Cloud Console Back to Top What is auto-user registration (self-service account onboarding)? Auto-user registration is a feature introduced in May 2026 that enables users to join their organization’s Red Hat account without requiring a manual invitation from an Organization Administrator. After an identity provider is integrated, administrators can enable auto-user registration through a dedicated tab and optionally create secure onboarding links. It simplifies access by allowing users to join the account more easily. Once enabled, users who authenticate through the identity provider are automatically granted access to the correct Red Hat account, eliminating the need for admins to manually create accounts or send invitations. This improves the onboarding process, reduces administrative workload, and provides users with faster access using their existing corporate credentials. For further information, please refer to this document What are the Customer Portal Roles and Permissions? Note: Customer Portal permissions and Hybrid Cloud Console user access roles are managed separately. The removal of the "Download Software and Updates" permission requirement does not affect role-based access to services and applications in Hybrid Cloud Console. Red Hat Customer Portal Roles and Permissions Organization Administrator: This is the highest permission level with full access to content and features. This is the only role that can manage users and control their access and permissions
Trending
Solutions
Solve specific problems that has been raised with Red HatThere are no trending items at this time.
Articles
Technical briefs, reference architectures, and early stages of documentationAs a customer how does Red Hat support me when I use third party components?
Policy and support definitions for how Red Hat manages non-Red Hat components/software when customers have issues.
Red Hat Online Learning (ROLE) Technical Support Information
Updating Global Contacts link
Latest discussions in the Red Hat Community
Rootless Podman Guided Exercise: Clarification Needed Regarding Image Builds for Roo...
Ansible Automation Portal Appliance has no network connection
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.