Using PXE Boot installer starts loading files but gets stuck during boot process with the message.<br />
dracut-initqueue[902]: RTNETLINK answers: File exists<br />
Please find rdsosreport.txt attached for more info.
↧
0017317: Unable to PXEBoot CentOS 8 Installer
↧
0017257: Remaining debranding on early kernel message
...<br />
[ 0.000000] Kernel command line: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=CentOS-8-i386 console=ttyS0 inst.graphical inst.notmux<br />
[ 0.000000] Specific versions of hardware are certified with Red Hat Enterprise Linux 8. Please see the list of hardware certified with Red Hat Enterprise Linux 8 at <a href="https://access.redhat.com/ecosystem">https://access.redhat.com/ecosystem.</a><br />
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)<br />
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)<br />
[ 0.000000] Initializing CPU#0<br />
...
↧
↧
0017349: [abrt] systemd: udev_device_new_from_subsystem_sysname(): systemd-journald killed by SIGABRT
Version-Release number of selected component:<br />
systemd-219-67.el7_7.2<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (7 frames)<br />
#0 udev_device_new_from_subsystem_sysname at src/libudev/libudev-device.c:965<br />
#1 udev_device_new_from_device_id at src/libudev/libudev-device.c:893<br />
#2 dev_kmsg_record at src/journal/journald-kmsg.c:221<br />
#3 server_read_dev_kmsg at src/journal/journald-kmsg.c:348<br />
#4 source_dispatch at src/libsystemd/sd-event/sd-event.c:2115<br />
#5 sd_event_dispatch at src/libsystemd/sd-event/sd-event.c:2472<br />
#6 sd_event_run at src/libsystemd/sd-event/sd-event.c:2501
↧
0016730: httpd landing page not accessible.
After installing httpd, the centos 8 apache landing page is not accessible.
↧
0015970: [abrt] gnome-shell: g_type_check_instance_is_fundamentally_a(): gnome-shell killed by SIGSEGV
Version-Release number of selected component:<br />
gnome-shell-3.28.3-6.el7<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (10 frames)<br />
#0 g_type_check_instance_is_fundamentally_a at gtype.c:4025<br />
#1 g_object_ref at gobject.c:3206<br />
#2 st_theme_get_custom_stylesheets at ../src/st/st-theme.c:311<br />
#3 ffi_call_unix64 at ../src/x86/unix64.S:76<br />
#4 ffi_call at ../src/x86/ffi64.c:522<br />
#5 gjs_invoke_c_function at gi/function.cpp:1088<br />
#6 function_call at gi/function.cpp:1408<br />
#7 CallJSNative at /usr/src/debug/firefox-52.9.0esr/js/src/jscntxtinlines.h:239<br />
#8 js::InternalCallOrConstruct at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:447<br />
#9 CallFromStack at /usr/src/debug/firefox-52.9.0esr/js/src/vm/Interpreter.cpp:510
↧
↧
0017350: Enable some more netfilter modules
It would be nice to have the 'time' and 'u32' packet filter options available. Atm they are disabled:<br />
<br />
# CONFIG_NETFILTER_XT_MATCH_TIME is not set<br />
# CONFIG_NETFILTER_XT_MATCH_U32 is not set<br />
<br />
I do not use 'IPCOMP', 'L2TP' and 'NFACCT', but do not see a reason not to enable them too.
↧
0017351: libvirtd starts before lvm activation
Hi everyone!<br />
The datastore is connected to the server using the iSCSI protocol + multipath + lvm. Two pools have been added through virsh and everyone has the startup option. Once the system is restarted, one pool is not available because libvirtd is loaded before it is initialized by the system.<br />
/var/log/messages (Pay attention to the time!)<br />
<br />
May 10 14:33:37 mlxvm01 libvirtd[5665]: 2020-05-10 11:33:37.481+0000: 5821: error : virStorageBackendLogicalMatchPoolSource:662 : unsupported configuration: cannot find logical volume group name 'dcomp_vol2'<br />
May 10 14:33:37 mlxvm01 libvirtd[5665]: 2020-05-10 11:33:37.481+0000: 5821: error : storageDriverAutostartCallback:189 : internal error: Failed to autostart storage pool 'DCOMP-VOL2': unsupported configuration: cannot find logical volume group name 'dcomp_vol2' <br />
<br />
A Secunda later<br />
<br />
May 10 14:33:38 mlxvm01 lvm[6546]: pvscan[6546] PV /dev/mapper/dcomp_vol2 online, VG dcomp_vol2 is complete.<br />
May 10 14:33:38 mlxvm01 lvm[6546]: pvscan[6546] VG dcomp_vol2 run autoactivation. <br />
<br />
The solution is to restart libvirtd after booting the system, or to run libvirtd by timer, which is not convenient.<br />
<br />
I think it would be better to run libvirtd after activating all physical and logical volumes.<br />
<br />
Sorry about the mistakes, I 'm writing through a translator. I thank for attention)
↧
0017352: GnuTLS error: Internal error in memory allocation.
GnuTLS can't establish a connection; dies with cryptic error.
↧
0017353: [abrt] yum: grabber.py:551::EOFError: EOF read where object expected
Version-Release number of selected component:<br />
yum-3.4.3-161.el7.centos<br />
<br />
Truncated backtrace:<br />
#1 <module> in /usr/lib/python2.7/site-packages/urlgrabber/grabber.py:551<br />
#2 <module> in /usr/lib/python2.7/site-packages/urlgrabber/__init__.py:55<br />
#3 <module> in /usr/lib/python2.7/site-packages/yum/parser.py:4<br />
#4 <module> in /usr/lib/python2.7/site-packages/yum/config.py:30<br />
#5 <module> in /usr/lib/python2.7/site-packages/yum/__init__.py:59<br />
#6 <module> in /usr/bin/yum:4
↧
↧
0017354: Error: Unable to find a match: libcgroup-devel
yum install libcgroup-devel -y<br />
<br />
Error: Unable to find a match: libcgroup-devel
↧
0017339: on the second load of the mlx4_core kernel module panic
on boot the mlx4_core kernel module propoerly finds a Mellanox connectx-2 VPD device. The device is not connected to the kernel module the first time as per the syslog message:<br />
[ 62.792147] mlx4_core 0000:05:00.0: command 0x4 timed out (go bit not cleared)<br />
[ 62.792150] mlx4_core 0000:05:00.0: device is going to be reset<br />
[ 62.798085] mlx4_core 0000:05:00.0: crdump: FW doesn't support health buffer access, skipping<br />
[ 63.799505] mlx4_core 0000:05:00.0: device was reset successfully<br />
[ 63.805637] mlx4_core 0000:05:00.0: QUERY_FW command failed, aborting<br />
[ 63.812112] mlx4_core 0000:05:00.0: Failed to init fw, aborting.<br />
[ 64.819389] mlx4_core: probe of 0000:05:00.0 failed with error -5<br />
[ 64.833322] pps_core: LinuxPPS API ver. 1 registered<br />
<br />
after removing the mlx4_core module and modprobe causes a kernel panic
↧
0017355: dnf --showduplicates list kernel-devel (e.g.) does only list one kernel version, RHEL8 lists all of them
Hi,<br />
<br />
```<br />
dnf install kernel-devel-4.18.0-147.3.1.el8_1.x86_64<br />
Last metadata expiration check: 0:15:55 ago on Mon 11 May 2020 09:18:17 AM CEST.<br />
No match for argument: kernel-devel-4.18.0-147.3.1.el8_1.x86_64<br />
Error: Unable to find a match: kernel-devel-4.18.0-147.3.1.el8_1.x86_64<br />
```<br />
while on RHEL8<br />
```<br />
sudo dnf install kernel-devel-4.18.0-147.3.1.el8_1.x86_64<br />
Dependencies resolved.<br />
=====================================================================================================================================================================================<br />
Package Architecture Version Repository Size<br />
=====================================================================================================================================================================================<br />
Installing:<br />
kernel-devel x86_64 4.18.0-147.3.1.el8_1 rhel-8-for-x86_64-baseos-rpms 13 M<br />
<br />
Transaction Summary<br />
=====================================================================================================================================================================================<br />
Install 1 Package<br />
```<br />
I found issues like this for CentOS7 already, partially it was mentioned as a feature, but in fact in all my CentOS7 installation I was able to pin to specific/old version.<br />
<br />
I want to install a old kernel version, to build kernel modules for it. I am pretty sure this worked some time ago, maybe this issue showed up with the latest dnf update?
↧
0016614: No Centos 8 AMIs
I'd like to request Centos 8 AMI images. You currently provide them for Centos 6 and 7, but not 8:<br />
<br />
<a href="https://wiki.centos.org/Cloud/AWS">https://wiki.centos.org/Cloud/AWS</a><br />
<a href="https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f34-1b0f377efe89">https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f34-1b0f377efe89</a><br />
<br />
The ZFS on Linux project uses Centos AMIs for our automated testing. We currently can't release Centos 8 ZFS RPMs, since we have no way to test them without the AMIs:<br />
<br />
<a href="https://github.com/zfsonlinux/zfs/issues/9287">https://github.com/zfsonlinux/zfs/issues/9287</a>
↧
↧
0017301: GNOME crashes several times a day -- clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
We have a touch screen application running from a "kiosk" user that is well locked down.<br />
<br />
UI runs an angular app in google-chrome in full screen mode.<br />
<br />
Several times throughout the day we are getting crashes across multiple systems. Was hoping that the latest kernel upgrade might fix however it did not.<br />
The following example is what we see in /var/log/messages indicating the event.<br />
<br />
Apr 28 19:21:17 5041-15219-7a2f7243 kernel: perf: interrupt took too long (4984 > 4943), lowering kernel.perf_event_max_sample_rate to 40000<br />
Apr 28 19:21:23 5041-15219-7a2f7243 journal: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed<br />
Apr 28 19:21:23 5041-15219-7a2f7243 journal: JS ERROR: TypeError: this._trackedWindows.get(...) is <a href="mailto:undefined#012_onWindowActorRemoved@resource">undefined#012_onWindowActorRemoved@resource</a>:///org/gnome/shell/ui/panel.js:841:<a href="mailto:9#012wrapper@resource">9#012wrapper@resource</a>:///org/gnome/gjs/modules/_legacy.js:82:22<br />
Apr 28 19:21:23 5041-15219-7a2f7243 journal: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed<br />
Apr 28 19:21:23 5041-15219-7a2f7243 kernel: gnome-shell[27294]: segfault at 244 ip 00007f93cab7d540 sp 00007ffcb1ca1128 error 4 in libmutter-2.so.0.0.0[7f93caac3000+16d000]<br />
Apr 28 19:21:23 5041-15219-7a2f7243 abrt-hook-ccpp: Process 27294 (gnome-shell) of user 1001 killed by SIGSEGV - dumping core<br />
Apr 28 19:21:28 5041-15219-7a2f7243 gnome-session-binary[1908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11<br />
Apr 28 19:21:28 5041-15219-7a2f7243 gnome-session: gnome-session-binary[1908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11<br />
Apr 28 19:21:28 5041-15219-7a2f7243 abrtd: Size of '/var/spool/abrt' >= 5000 MB (MaxCrashReportsSize), deleting old directory 'ccpp-2020-04-28-18:31:54-2110'
↧
0016947: glibc32 should not be shipped
There is glibc32.x86_64 which simulates glibc.i686 in Red Hat Brew as during building of packages it is impossible to access other-arch packages. But glibc32.x86_64 makes no sense to ship as users should use glibc.i686 instead. It even messes up everything.
↧
0017326: Please add virt8s-ovirt-44 related tags in community build system
A soname bump (dpdk.x86_64 18.11.2-3.el8 AppStream vs dpdk.x86_64 19.11-4.el8 Stream-AppStream) broke openvswitch package on CentOS Stream.<br />
We needs different tags both for the buildroot, and to deliver out to the mirrors.<br />
Looking at existing tags I think we can use something like:<br />
<br />
- virt8s-ovirt-44-candidate<br />
- virt8s-ovirt-44-testing<br />
- virt8s-ovirt-44-release<br />
- virt8s-ovirt-44-el8s-build<br />
<br />
Looking at <a href="https://buildlogs.centos.org/centos/">https://buildlogs.centos.org/centos/</a> I think this will require to add there an 8-stream directory tree for the testing packages.
↧
0017356: [abrt] gnome-screenshot: poll_for_event(): gnome-screenshot killed by SIGABRT
Version-Release number of selected component:<br />
gnome-screenshot-3.26.0-1.el7<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (7 frames)<br />
#4 poll_for_event at xcb_io.c:260<br />
#5 poll_for_response at xcb_io.c:278<br />
#7 XPending at Pending.c:55<br />
#8 gdk_event_source_prepare at gdkeventsource.c:269<br />
#10 g_main_context_prepare at gmain.c:3473<br />
#12 g_main_context_iteration at gmain.c:3962<br />
#13 g_application_run at gapplication.c:2470
↧
↧
0017357: Samba on Glusterfs via vfs
I see either reintroduction of - <a href="https://bugzilla.samba.org/show_bug.cgi?id=13585">https://bugzilla.samba.org/show_bug.cgi?id=13585</a> - (I'd have filed it at Samba's directly bug have no account over there) or something very similar in:<br />
<br />
samba-4.10.4-10.el7.x86_64<br />
glusterfs-server-6.9-1.el7.x86_64<br />
<br />
Not being a developer I think the code from patches for <4.10 versions are now in the upstream(or Centos') trunk(certainly are not in patches). I took a look at what's in the patch(es) for <4.10v and to me(not a developer!) it seems that, that code(from Centos'rpm.src) is patched in already(as oppose to in external patches)<br />
<br />
So now, after yesterday's update to Centos 7.8, samba+gluster render the same old:<br />
<br />
"The file '<%1 NULL:NameDest>' is too large for the destination file system.'<br />
<br />
regards, L
↧
0017358: /var/spool/anacron/cron.* get created with incorrect permissions
In 7.8-2003 the anacron files get created with permissions 0644. The RPM-specified values are 0600. This is an issue when we need to perform security validation using 'rpm -V'. The files are properly created using 7.7-1908. <br />
<br />
Both systems are created with the minimal package group with the same kickstart file. The cronie-anacron package version seems to be the same in both releases.
↧
0015560: [abrt] control-center: mem_error(): gnome-control-center killed by SIGABRT
Version-Release number of selected component:<br />
control-center-3.28.1-4.el7<br />
<br />
Truncated backtrace:<br />
Thread no. 1 (10 frames)<br />
#2 mem_error at gslice.c:1472<br />
#3 slab_allocator_free_chunk at gslice.c:1354<br />
#4 magazine_cache_trim at gslice.c:679<br />
#5 magazine_cache_push_magazine at gslice.c:710<br />
#6 thread_memory_magazine2_unload at gslice.c:809<br />
#7 g_slice_free_chain_with_offset at gslice.c:1199<br />
#8 g_slist_free at gslist.c:137<br />
#9 pango_layout_clear_lines at ../pango/pango-layout.c:2858<br />
#10 pango_layout_set_attributes at ../pango/pango-layout.c:614<br />
#11 gtk_label_update_layout_attributes at gtklabel.c:3536
↧