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

Search

Latest resources

Browse the latest published and updated knowledgebase

Vulnerability Acknowledgements for Red Hat online services

Updated on Oct 30, 2026

Vulnerability Acknowledgements for Red Hat online services.

Setting OdhDa­shboa­rdCon­fig.s­pec.n­otebo­okCon­troll­er.pv­cSize does not change default PVC size for new workbenches in RHOAI

VerifiedUpdated on Oct 30, 2026Subscription required

- When attempting to modify the default PVC size under Settings > Cluster Settings > General Settings in the Red Hat OpenShift AI (RHOAI) dashboard, or by directly updating the `OdhDashboardConfig` custom resource's `spec­.note­bookC­ontro­ller.­pvcSi­ze` field, newly created workbenches continue to default to `20 GiB`, disregarding the adjusted setting.

Kdump over NFS fails to generate vmcore on a system with Intel network card with IDPF driver

VerifiedUpdated on Oct 30, 2026

Kdump over NFS fails to generate vmcore on a system with one or more Intel network card(s) that use the `idpf` driver. The network manager times out waiting for a non-existent device; after that it requests a DHCP address, which fails with `no response`. Eventually, kdump is disconnected and fails. ~~~ [6.984406] systemd[1]: Starting nm-wa­it-on­line-­initr­d.ser­vice.­.. [9.433201] idpf 0000:05:00.0: Device HW Reset initiated [10.478322] 4xxx 0000:6b:00.0: Failed to power up the device [10.484005] 4xxx 0000:6b:00.0: Failed to initialize device [10.499766] 4xxx 0000:6b:00.0: Resetting device qat_dev0 [10.612515] 4xxx 0000:6b:00.0: probe with driver 4xxx failed with error-14 [[0m[0;31m* [0m] A start job is running for nm-wa­it-…i­ne-in­itrd.­servi­ce (5s / no limit) [11.626921] 4xxx 0000:e8:00.0: Failed to power up the device [11.632606] 4xxx 0000:e8:00.0: Failed to initialize device [11.649413] 4xxx 0000:e8:00.0: Resetting device qat_dev0 [9.701809] rngd[494]: [jitter]: Enabling JITTER rng support [9.709045] rngd[494]: [jitter]: Initialized [11.757398] 4xxx 0000:e8:00.0: probe with driver 4xxx failed with error-14 After that NM eventually times out waiting for a device: [66.584985] NetworkManager[493]: [1734752025.5989] settings: startup-complete: profile "Wired connection 1" (9014­71d3-­9a88-­3504-­83c2-­693ab­17aba­db) was waiting for non-existing device (with timeout "­;conn­ectio­n.wai­t-dev­ice-t­imeou­t=600­00&qu­ot;).­.. [72.684326] idpf 0000:05:00.0: Transaction timed-out (op 1, 60000ms) [72.721325] idpf 0000:05:00.0: Device HW Reset initiated [71.089973] kdump[649]: Waiting for network to be ready (4s / 10min)... [72.109371] systemd-udevd[657]: Network interface NamePolicy= disabled on kernel command line. [72.119415] NetworkManager[493]: [1734752031.1237] manager: (eth0): new Ethernet device (/org­/free­deskt­op/Ne­twork­Manag­er/De­vices­/2) [72.132189] NetworkManager[493]: [1734752031.1279] device (eth0): state change: unmanaged-> unavailable (reason 'managed', sys-iface-state: '­;exte­rnal&­#039;­) [73.104718] kdump[666]: Waiting for network to be ready (6s / 10min) [73.212226] NetworkManager[493]: [1734752032.2201] device (eth0): carrier: link connected [73.222162] dhclient[668]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0xb41e662) ~~~

Logrotate fails with error "lines must begin with a keyword or a filename (possibly in double quotes)" due to missing log file paths in custom configuration

VerifiedUpdated on Oct 30, 2026Subscription required

- The `logrotate` service fails to execute, or running `logrotate` in dry-run/debug mode produces the following error messages: ~~~ error:: lines must begin with a keyword or a filename (possibly in double quotes) error: found error in file, skipping ~~~

Login or sudo su - fails after Leapp upgrade from RHEL 7.9 to 9.4/9.6 with errors: /opt/­rh/rh­-pyth­on38/­enabl­e: No such file, Can't read /etc/­scl/c­onf/r­h-pos­tgres­ql10

VerifiedUpdated on Oct 30, 2026Subscription required

- After performing a Leapp upgrade from RHEL 7.9 to RHEL 8.10 and finally to RHEL 9.6/RHEL 9.4, switching to the root user or any other user using `sudo su-` or `su-` fails with the following errors: ~~~-bash: /opt/­rh/rh­-pyth­on38/­enabl­e: No such file or directory Unable to get file status /etc/­scl/c­onf/r­h-pyt­hon38­: No such file or directory Can't read /etc/­scl/c­onf/r­h-pos­tgres­ql10, rh-postgresql10 is probably not installed ~~~

Ansible-builder fails with a permission denied error

VerifiedUpdated on Oct 30, 2026Subscription required

- When building an execution environment with Ansible-builder, the build process fails with a `Interactive authentication required.: Permission denied` error.- I am getting a Permission Denied error when building an execution environment with Ansible-builder.

What is a GFS2 withdrawal in a RHEL Resilient Storage cluster?

Updated on Oct 30, 2026Subscription required

description of gfs2 withdrawals

Why does a system hang on shutdown when a gfs2 filesystem has a withdrawal?

VerifiedUpdated on Oct 30, 2026Subscription required

* Why does a system hang on shutdown when a gfs2 filesystem has a withdrawal?

Latest discussions in the Red Hat Community

Ability to fallback to nouveau driver when NVidia driver fails to load

Started Wednesday, October 14, 2026 at 3:34:53 PM
Red Hat Enterprise Linux

New RHCA Certification paths are a disaster

Started Tuesday, October 13, 2026 at 5:08:59 PM
Other

RHEL 8 httpd PHP directives not working on html file

Started Monday, October 12, 2026 at 8:00:00 PM
Red Hat Enterprise Linux
Meet with other Red Hat users, ask questions, collaborate to solve problems, and connect with our very own Red Hat engineers and moderators - the experts behind our products. Visit our community
Visit our community

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.

Explore the entire customer portal for other resources

Search the entire customer portal