October 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1042037] Apache upgrade runs /usr/share/apache2/apache-22-24-upgrade and issues a2enmod: command not found
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1042037 http://bugzilla.suse.com/show_bug.cgi?id=1042037#c11 --- Comment #11 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1042037) was mentioned in https://build.opensuse.org/request/show/530969 Factory / apache2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1058686] devel:languages:php/php7: Feature request: php7-embedded / libphp7.so
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1058686 http://bugzilla.suse.com/show_bug.cgi?id=1058686#c5 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Petr Gajdos <pgajdos(a)suse.com> --- Nevermind, php7 with php7-embed binary package is on its way to factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1060551] openSUSE fails to boot after installation, when dmraid is used to support SATA RAID controllers 2
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1060551 http://bugzilla.suse.com/show_bug.cgi?id=1060551#c4 --- Comment #4 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- Created attachment 742921 --> http://bugzilla.suse.com/attachment.cgi?id=742921&action=edit udev db dump of failed boot -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1060551] openSUSE fails to boot after installation, when dmraid is used to support SATA RAID controllers 2
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1060551 http://bugzilla.suse.com/show_bug.cgi?id=1060551#c3 --- Comment #3 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- Created attachment 742920 --> http://bugzilla.suse.com/attachment.cgi?id=742920&action=edit journalctl of failed boot -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1060551] openSUSE fails to boot after installation, when dmraid is used to support SATA RAID controllers 2
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1060551 http://bugzilla.suse.com/show_bug.cgi?id=1060551#c2 Andrei Borzenkov <arvidjaar(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers(a)suse.de --- Comment #2 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- Adding systemd guys as this is not YaST issue *except* the very first boot where initrd inherits wrong symlink from installation system. I guess this requires separate bug report (unless there is already one). I was able to setup dmraid in VM (it is capable of creating isw metadata) and reproduced this issue. I attach journalctl and udevadm db dump from failed boot in emergency mode. I think I now understand what happens. As udev scans devices it finds the same filesystem on each individual partition and on dmraid device: P: /devices/pci0000:00/0000:00:03.0/virtio1/host5/target5:0:0/5:0:0:0/block/sda/sda3 ... S: disk/by-uuid/2a92d892-b6db-4e24-a758-f3d0a0bd7005 ... E: ID_FS_TYPE=btrfs E: ID_FS_USAGE=filesystem ... E: TAGS=:systemd: P: /devices/pci0000:00/0000:00:03.0/virtio1/host5/target5:0:1/5:0:1:0/block/sdb/sdb3 ... S: disk/by-uuid/2a92d892-b6db-4e24-a758-f3d0a0bd7005 ... E: ID_FS_TYPE=btrfs E: ID_FS_USAGE=filesystem ... E: TAGS=:systemd: P: /devices/virtual/block/dm-3 ... S: disk/by-uuid/2a92d892-b6db-4e24-a758-f3d0a0bd7005 ... E: ID_FS_TYPE=btrfs E: ID_FS_USAGE=filesystem ... E: TAGS=:systemd: So we have *THREE* different devices each defining the same UUID link and none setting SYSTEMD_READY=0. So *any* of those devices satisfies systemd requirement for /dev/disk/by-uuid/2a92d892-b6db-4e24-a758-f3d0a0bd7005; as soon as *any* of those devices is detected by udev, systemd starts mount units waiting for UUID. Which explains Oct 03 20:23:48 linux-3l98 mount[958]: mount: /dev/sda3 is already mounted or /var/lib/pgsql busy Whether it is sda3 or sdb3 is random (race condition) and I also had swapping and /boot (on the first partition) failed just as well for the same reason. Of course when we get chance to log into the system and examine current state all devices had already been processed so the last one (dmraid devices) already overwrote links which now appear correct. Bummer. Fixing it properly requires us to skip probing partitions of dmraid disk members: N: sda E: ID_FS_TYPE=isw_raid_member E: ID_FS_USAGE=raid we already import parent ID_* in 60-persistent-storage.rules. Is there any situation where we *want* process individual partition even though it is known to be part of dmraid? Oh, and BTW I expect mdraid to have the same issue for external metadata/partitioned raid as well ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1052268] 42.3 Won't Shut Down
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1052268 http://bugzilla.suse.com/show_bug.cgi?id=1052268#c8 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #8 from Franck Bui <fbui(a)suse.com> --- No feedback have been provided since more than 1 month... closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042037] Apache upgrade runs /usr/share/apache2/apache-22-24-upgrade and issues a2enmod: command not found
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1042037 http://bugzilla.suse.com/show_bug.cgi?id=1042037#c10 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Petr Gajdos <pgajdos(a)suse.com> --- Tumbleweed: I have removed apache-22-24-upgrade entirely. If there is someone migrating from 2.2, the configuration with old modules in APACHE_MODULES will just fail. This will force a user to think about there can be another configuration bits to be amended as well. Wrt missing authn_core or authz_core in APACHE_MODULES, we could perhaps implement warning or error-out directly in start_apache2, if demand will arise. Leap: Call a2enmod with full path, this should solve the original problem. If not, please reopen the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1052006] grub2-install fails to find /dev/btrfs
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1052006 http://bugzilla.suse.com/show_bug.cgi?id=1052006#c7 --- Comment #7 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2017:2634-1: An update that has two recommended fixes can now be installed. Category: recommended (low) Bug References: 1039712,1052006 CVE References: Sources used: SUSE Linux Enterprise Server 12-SP3 (src): yast2-bootloader-3.2.24-2.3.8 SUSE Linux Enterprise Desktop 12-SP3 (src): yast2-bootloader-3.2.24-2.3.8 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1053595] Could not set limit: mkfs.btrfs died abnormally
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1053595 http://bugzilla.suse.com/show_bug.cgi?id=1053595#c8 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #8 from Franck Bui <fbui(a)suse.com> --- Thanks to Markos, I finally reproduced the issue locally and it appears that a fix already exist for this since v230: https://github.com/systemd/systemd/commit/579afbea21f6439e97c141160ed1f7dd7… I backported it to v228 (SLE12-SP2 and greater) and now when mkfs.btrfs is not installed, machinectl should emit a coherent error: # machinectl set-limit 16G Could not set limit: Cannot set up /var/lib/machines, mkfs.btrfs is missing Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1057778] Users and groups crashes module crashes with ruby errors.
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1057778 http://bugzilla.suse.com/show_bug.cgi?id=1057778#c5 Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mxl(a)nmcl.no) --- Comment #5 from Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> --- No problem Mikael. Unfortunately, I've been unable to reproduce your problem. We could try to run the module with the debugging messages enabled. Could you, please, try to run this command (as root)? Y2DEBUG=1 /sbin/yast2 users After the module crashes, just please attach the logs again (using save_y2logs). Thanks in advance! -- You are receiving this mail because: You are on the CC list for the bug.

1 0