-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
CentOS Stream 9, CentOS Stream 10
-
None
-
No
-
None
-
EasyFix
-
rhel-net-perf
-
ssg_core_services
-
3
-
False
-
False
-
-
None
-
CentOS Stream
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
What is the impact of this issue to you?
Updating bind-chroot always produces error messages due to the use of the `-a` operator in `chroot_fix_devices`.
Please provide the package NVR for which the bug is seen:
bind-chroot-32:9.18.33-3.el10.x86_64
How reproducible is this bug?:
Steps to reproduce
[root@47d925e948c3 /]# dnf reinstall -y bind-chroot ... Running transaction Preparing : 1/1 Reinstalling : bind-chroot-32:9.18.33-3.el10.x86_64 1/2 Running scriptlet: bind-chroot-32:9.18.33-3.el10.x86_64 1/2 stat: cannot statx '/var/named/chroot/dev/null': No such file or directory stat: cannot statx '/var/named/chroot/dev/random': No such file or directory stat: cannot statx '/var/named/chroot/dev/zero': No such file or directory Running scriptlet: bind-chroot-32:9.18.33-3.el10.x86_64 2/2 Cleanup : bind-chroot-32:9.18.33-3.el10.x86_64 2/2 Running scriptlet: bind-chroot-32:9.18.33-3.el10.x86_64 2/2 Reinstalled: bind-chroot-32:9.18.33-3.el10.x86_64 Complete!
Expected results
No error messages should be displayed.
Actual results
Error output when updating bind-chroot.
