From Jan.Hebler at vodafone.com Thu Apr 1 09:49:37 2021 From: Jan.Hebler at vodafone.com (Hebler, Jan, Vodafone DE) Date: Thu, 1 Apr 2021 09:49:37 +0000 Subject: AW: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20200312! In-Reply-To: <20210330074811.24f788ae@suse.cz> References: <604ba655abd7_1f52ac84304a61068927@a6d1af99e82b.mail> <2E6C12D7-AF89-4438-9475-491A0B8958BB@suse.com>

<20210330074811.24f788ae@suse.cz> Message-ID: Hi Josef Thanks a lot for the Support, Option one did the Trick. Regards, Jan C2 General -----Urspr?ngliche Nachricht----- Von: josef Reidinger Gesendet: Dienstag, 30. M?rz 2021 07:48 An: sle-beta at lists.suse.com Cc: Hebler, Jan, Vodafone DE ; Vincent Moutoussamy Betreff: Re: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20200312! CYBER SECURITY WARNING: This email is from an external source - be careful of attachments and links. Please follow the Cyber Code and report suspicious emails. On Mon, 29 Mar 2021 10:16:51 +0000 "Hebler, Jan, Vodafone DE" wrote: > Great, thank you ? > > The Problem is already solved, there was an typo: https://bugzilla.suse.com/show_bug.cgi?id=1183352. However, the fixed package is part of the initrd and needs to be replaced there and that's beyond my knowledge. What I've tried was to create an yum-repo with the fixed package and offer the repo as an installer-update, but autoyast refuses them and even if I get the repo fixed, autoyast loads the installer-repo AFTER the rules file. So it seems that I need an updated initrd. > Hi, I know basically about three ways how to proceed for you. 1. if it is single rpm, then place rpm to some place like ftp server and you can pass on kernel command line `dud=ftp:///` and it will be used before autoyast start. 2. if there are more rpms, then there is a tool mkdud https://github.com/openSUSE/mkdud with that tool you create driver update with rpms you need and pass it same as in 1, just use dud file instead of rpm. 3. create modified iso, so you do not need to modify kernel boot parameters. create dud as in 2 and use mksusecd. See more at https://github.com/openSUSE/mksusecd#1-update-a-package-that-is-used-in-the-installation-system I hope that it helps. If you have more questions just ask. Josef > Regards, Jan > > > C2 General > > -----Urspr?ngliche Nachricht----- > Von: Vincent Moutoussamy > Gesendet: Montag, 29. M?rz 2021 12:05 > An: Hebler, Jan, Vodafone DE > Cc: sle-beta at lists.suse.com > Betreff: Re: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20200312! > > CYBER SECURITY WARNING: This email is from an external source - be careful of attachments and links. Please follow the Cyber Code and report suspicious emails. > > Hi, > > Ok, could you please tell me which issues you are facing with autoyast? Did you create any bugs? > I would like to get a more detailed view on your issues to investigate what we could do to unblock you. > > Thanks, > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program Manager > JeOS Technical Project Manager > Paris, France > > > On 29 Mar 2021, at 11:55, Hebler, Jan, Vodafone DE wrote: > > > > Hi > > > > Unfortunally, im not aware of any workaround. There is an updated autoyast-rpm, but that doesn't helm me much as I'm not aware how to integrate that in the autoyast-process. There is an installer-update step, but these step comes AFTER the evaluation of the rules file, so that doesn?t help much. > > > > Regards, Jan > > > > > > C2 General > > > > -----Urspr?ngliche Nachricht----- > > Von: Vincent Moutoussamy > > Gesendet: Montag, 29. M?rz 2021 11:52 > > An: Hebler, Jan, Vodafone DE > > Cc: sle-beta at lists.suse.com > > Betreff: Re: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20200312! > > > > CYBER SECURITY WARNING: This email is from an external source - be careful of attachments and links. Please follow the Cyber Code and report suspicious emails. > > > > Hi, > > > > The next refresh of our ISOs is scheduled for the Public Release Candidate in April 30 (https://suse.com/betaprogram/sle-beta/#releases). > > I might be mistaken but I think there is some possible workaround for you to proceed with autoyast without a refreshed ISOs? > > > > Have a nice day, > > > > Regards, > > -- > > Vincent Moutoussamy > > SUSE Beta Program Manager > > JeOS Technical Project Manager > > Paris, France > > > >> On 27 Mar 2021, at 07:04, Hebler, Jan, Vodafone DE wrote: > >> > >> Hi > >> > >> Are the iso-images get?ts an update too? I still struggle with errors in autoyast located in the initrd. > >> > >> Regards, Jan > >> > >> > >> C2 General > >> Von: sle-beta > >> Im > >> Auftrag von SUSE Beta Program > >> Gesendet: Freitag, 12. M?rz 2021 18:35 > >> An: sle-beta at lists.suse.com > >> Betreff: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20200312! > >> > >> CYBER SECURITY WARNING: This email is from an external source - be careful of attachments and links. Please follow the Cyber Code and report suspicious emails. > >> Having trouble viewing this email? Please check the plain text version of this email. > >> > >> <~WRD0000.jpg><~WRD0000.jpg> > >> We are happy to announce Weekly Updates 20200312 for SUSE Linux Enterprise 15 Service Pack 3! > >> > >> Download > >> SLED / Workstation Extension: Warning for dual-boot with Windows > >> when using Secure Boot > >> > >> Due to Boothole2 security fixes present in SLE 15 SP3 Public Beta build, you might be unable to use dual-boot to boot Windows from grub2, if secure boot is enabled. > >> > >> The issue should only affect SLED and Workstation extension users using dual-boot and with UEFI Secure boot enabled. > >> > >> We are working on a bugfix for grub2. Until this fix is released, you can disable Secure Boot as a workaround. > >> > >> Updates available since Public Beta > >> > >> Since SLE 15 SP2 Public Beta Program we are releasing weekly updates through our online channels during our SLE Public Beta Program. Please refer to our FAQ for more information. This week we are providing the following: > >> > >> Added packages > >> > >> ? go1.16 1.16-1.3.1 > >> ? go1.16-doc 1.16-1.3.1 > >> ? go1.16-race 1.16-1.3.1 > >> ? mumps_5_3_5-gnu-{mpich-hpc-devel,mpich-hpc-doc,mpich-hpc-examples,mvapich2-hpc-devel,mvapich2-hpc-doc,mvapich2-hpc-examples,openmpi3-hpc-devel,openmpi3-hpc-doc,openmpi3-hpc-examples,openmpi4-hpc-devel,openmpi4-hpc-doc,openmpi4-hpc-examples} 5.3.5-1.1 > >> ? petsc_3_14_4-gnu-{mpich-hpc-devel,mvapich2-hpc-devel,openmpi3-hpc-devel,openmpi4-hpc-devel} 3.14.4-1.7 > >> ? pnetcdf_1_12_2-gnu-{mpich-hpc,mpich-hpc-devel,mvapich2-hpc,mvapich2-hpc-devel,openmpi3-hpc,openmpi3-hpc-devel,openmpi4-hpc,openmpi4-hpc-devel} 1.12.2-1.1 > >> ? pnetcdf_1_12_2-hpc-doc 1.12.2-1.2 > >> ? scap-security-guide 0.1.54-1.4.1 > >> ? scap-security-guide-debian 0.1.54-1.4.1 > >> ? scap-security-guide-redhat 0.1.54-1.4.1 > >> ? scap-security-guide-ubuntu 0.1.54-1.4.1 Updated Kernel > >> > >> ? kernel-source: 5.3.18-47.7 => 5.3.18-48.1 Updated packages > >> (selection) > >> > >> ? arpwatch: 2.1a15-5.6.1 => 2.1a15-5.9.1 > >> ? audit: 2.8.5-2.25 => 2.8.5-3.1 > >> ? autoyast2: 4.3.68-1.3 => 4.3.70-1.1 > >> ? bcache-tools: 1.1-3.9.1 => 1.1-3.12.2 > >> ? bcm43xx-firmware: 20180314-19.31 => 20180314-20.2 > >> ? cloud-init: 20.2-8.36.1 => 20.2-8.39.8 > >> ? coreutils: 8.29-2.12 => 8.32-1.1 > >> ? cross-nvptx-gcc7: 7.5.0+r278197-4.22.1 => 7.5.0+r278197-4.25.1 > >> ? cyrus-sasl-bdb: 2.1.27-1.15 => 2.1.27-2.1 > >> ? dracut: 049.1+suse.183.g7282fe92-3.18.2 => 049.1+suse.185.g9324648a-3.21.1 > >> ? fio: 3.4-4.2.4 => 3.23-4.5.1 > >> ? freeradius-server: 3.0.21-3.3.1 => 3.0.21-3.6.1 > >> ? gcc7: 7.5.0+r278197-4.22.1 => 7.5.0+r278197-4.25.1 > >> ? glibc: 2.31-4.17 => 2.31-5.4 > >> ? gnuplot: 5.2.2-3.3.29 => 5.2.2-3.6.1 > >> ? gpg2: 2.2.5-12.10 => 2.2.27-1.1 > >> ? grub2: 2.04-14.1 => 2.04-16.2 > >> ? hawk2: 2.4.0+git.1611141202.2fe6369e-3.21.1 => 2.6.0+git.1613486511.51b6e37d-3.24.1 > >> ? java-1_8_0-ibm: 1.8.0_sr6.20-3.47.1 => 1.8.0_sr6.25-3.50.1 > >> ? java-1_8_0-openjdk: 1.8.0.275-3.45.1 => 1.8.0.282-3.48.1 > >> ? kmod: 28-1.15 => 28-2.1 > >> ? libreoffice: 7.1.0.3-1.4 => 7.1.1.2-1.2 > >> ? libvirt: 7.0.0-3.3 => 7.1.0-1.2 > >> ? mksusecd: 1.77-3.5.1 => 1.78-1.1 > >> ? MozillaFirefox: 78.7.1-8.29.1 => 78.8.0-8.32.2 > >> ? MozillaThunderbird: 78.7.1-8.12.1 => 78.8.0-8.15.4 > >> ? netpbm: 10.80.1-3.8.2 => 10.80.1-3.11.1 > >> ? nodejs12: 12.20.1-4.10.1 => 12.21.0-4.13.2 > >> ? nodejs14: 14.15.4-5.6.1 => 14.16.0-5.9.1 > >> ? perl-Sys-Virt: 7.0.0-1.26 => 7.1.0-1.2 > >> ? pipewire: 0.3.6-3.6.1 => 0.3.22-1.1 > >> ? postfix: 3.5.9-1.6 => 3.5.9-2.1 > >> ? postgresql10: 10.15-8.25.1 => 10.16-8.29.1 > >> ? postgresql12: 12.5-8.13.1 => 12.6-8.16.1 > >> ? postgresql13: 13.1-5.3.15 => 13.2-5.6.1 > >> ? pulseaudio: 14.2-2.10 => 14.2-3.1 > >> ? qemu: 5.2.0-7.1 => 5.2.0-8.3 > >> ? qpdf: 9.0.2-1.36 => 10.3.0-1.1 > >> ? raspberrypi-eeprom: 0.0~2020.09.03.65~gb9c255d-2.10 => 0.0~2020.09.03.75~g3129546-1.2 > >> ? raspberrypi-firmware-config: 2021.01.21-2.10 => 2021.01.21-3.1 > >> ? raspberrypi-firmware-dt: 2021.01.22-1.10 => 2021.01.22-2.1 > >> ? raspberrypi-firmware: 2021.01.21-2.10 => 2021.01.21-3.1 > >> ? redfish-finder: 0.4-2.30 => 0.4-3.2 > >> ? redis: 6.0.8-1.3.1 => 6.0.10-1.7.1 > >> ? rpm: 4.14.1-28.17 => 4.14.1-29.5 > >> ? shadow: 4.8.1-1.5 => 4.8.1-2.4 > >> ? shim: 15+git47-9.13 => 15+git47-10.1 > >> ? stunnel: 5.57-3.5.1 => 5.57-3.8.1 > >> ? supportutils: 3.1.14-2.2 => 3.1.14-3.1 > >> ? systemd-default-settings: 0.5-1.30 => 0.7-1.1 > >> ? tboot: 20170711_1.9.8-15.6.1 => 20170711_1.9.8-15.9.1 > >> ? tcl: 8.6.7-7.3.1 => 8.6.7-7.6.1 > >> ? tk: 8.6.7-3.3.1 => 8.6.7-3.6.3 > >> ? transactional-update: 3.1.4-1.4 => 3.2.0-1.2 > >> ? u-boot-rpiarm64: 2021.01-1.1 => 2021.01-2.1 > >> ? util-linux: 2.36.1-1.3 => 2.36.2-1.4 > >> ? util-linux-systemd: 2.36.1-1.2 => 2.36.2-1.1 > >> ? wicked: 0.6.64-3.3.4 => 0.6.65-1.1 > >> ? yast2-* > >> Removed packages > >> > >> ? go1.15 > >> ? go1.15-doc > >> ? go1.15-race > >> ? libmumps_5_2_1-gnu-{mpich-hpc,mvapich2-hpc,openmpi3-hpc,openmpi4-hpc} > >> ? libpetsc_3_14_1-gnu-{mpich-hpc,mvapich2-hpc,openmpi3-hpc,openmpi4-hpc} > >> ? libpnetcdf_1_12_1-gnu-{mpich-hpc,mvapich2-hpc,openmpi3-hpc,openmpi4-hpc} > >> ? mumps_5_2_1-gnu-{mpich-hpc-devel,mpich-hpc-doc,mpich-hpc-examples,mvapich2-hpc-devel,mvapich2-hpc-doc,mvapich2-hpc-examples,openmpi3-hpc-devel,openmpi3-hpc-doc,openmpi3-hpc-examples,openmpi4-hpc-devel,openmpi4-hpc-doc,openmpi4-hpc-examples} > >> ? petsc_3_14_1-gnu-{mpich-hpc-devel,mvapich2-hpc-devel,openmpi3-hpc-devel,openmpi4-hpc-devel} > >> ? pnetcdf_1_12_1-gnu-{mpich-hpc,mpich-hpc-devel,mvapich2-hpc,mvapich2-hpc-devel,openmpi3-hpc,openmpi3-hpc-devel,openmpi4-hpc,openmpi4-hpc-devel} > >> ? pnetcdf_1_12_1-hpc-doc > >> More information > >> > >> Schedule > >> Changelog > >> Known issues > >> Questions? > >> > >> If you have any question, please contact us at beta-programs at suse.com. > >> > >> Your SUSE Linux Enterprise team > >> > >> Click here to unsubscribe From beta-programs at suse.com Thu Apr 1 17:02:26 2021 From: beta-programs at suse.com (SUSE Beta Program) Date: Thu, 01 Apr 2021 19:02:26 +0200 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20210401! Message-ID: <6065fca239d69_ad772bc-2a9@MacBouille.local.mail> We are happy to announce Weekly Updates 20210401 for SUSE Linux Enterprise 15 Service Pack 3! This mark an important step toward our upcoming Public Release Candidate[1], since from now on our Release Management team[2] will only accept code submissions for security fixes and bug fixes! Download[3] Updates available since Public Beta Since SLE 15 SP2 Public Beta Program we are releasing weekly updates through our online channels during our SLE Public Beta Program. Please refer to our FAQ[4] for more information. Note that you can even enable the Online Updates Channels during the installation to apply them before booting your system. This week we are providing the following: Added packages - grafana-ha-cluster-dashboards 1.1.0+git.1605027022.a84d536-1.11.1 - grafana-sap-hana-dashboards 1.0.2+git.1600361067.f7c00d1-1.8.2 - grafana-sap-netweaver-dashboards 1.0.3+git.1601889366.9f71957-1.11.2 - grafana-sap-providers 1.1-1.8.1 - nginx-macros 0.0.1-1.1 - yast2-adcommon-python 1.6-3.3.10 Updated Kernel - kernel-source: 5.3.18-51.2 => 5.3.18-52.3 Updated packages (selection) - alsa-utils: 1.2.4-2.28 => 1.2.4-3.1 - autoyast2: 4.3.71-1.1 => 4.3.75-1.1 - bcm43xx-firmware: 20180314-20.2 => 20180314-21.1 - crmsh: 4.2.0+git.1609987436.0d3a9bf5-5.35.1 => 4.3.0+20210305.9db5c9a8-5.42.1 - dehydrated: 0.6.5-9.13 => 0.7.0-11.3.1 - dracut: 049.1+suse.185.g9324648a-3.21.1 => 049.1+suse.186.g320cc3d1-3.24.1 - efivar: 37-6.6.1 => 37-6.9.1 - filesystem: 15.0-9.2 => 15.0-11.3.2 - git: 2.26.2-3.28.2 => 2.26.2-3.31.1 - gnome-shell: 3.34.5-7.33 => 3.34.5-8.1 - gnutls: 3.6.7-14.7.1 => 3.6.7-14.10.2 - go1: 1.16-1.3.1 => 1.16.2-1.8.1 - golang-github-vpenso-prometheus_slurm_exporter: 0.15-1.27 => 0.17-1.3 - grub2: 2.04-17.2 => 2.04-18.4 - hawk2: 2.6.0+git.1613486511.51b6e37d-3.24.1 => 2.6.3+git.1614684118.af555ad9-3.27.1 - hostinfo: 1.0-18.15 => 1.0.6-1.1 - hwdata: 0.343-3.15.1 => 0.345-3.18.1 - kiwi-templates-JeOS: 15.2-24.6 => 15.3-1.1 - libunwind: 1.2.1-4.2.3 => 1.5.0-4.5.1 - libvirt: 7.1.0-1.3 => 7.1.0-2.1 - lua-lmod: 8.4.20-1.3 => 8.4.27-1.1 - multipath-tools: 0.8.5+12+suse.3b0e9ca-1.26 => 0.8.5+29+suse.5dabcd2-1.1 - nginx: 1.16.1-1.21 => 1.19.8-1.1 - openldap2: 2.4.46-9.45.1 => 2.4.46-9.48.1 - openssl-1_0_0: 1.0.2p-3.34.1 => 1.0.2p-3.37.1 - openssl-1_1: 1.1.1d-11.12.1 => 1.1.1d-11.20.1 - perl-DBD-SQLite: 1.54-1.31 => 1.66-1.1 - pipewire: 0.3.22-1.2 => 0.3.24-1.1 - plymouth: 0.9.5+git20190908+3abfab2-2.50 => 0.9.5+git20190908+3abfab2-3.3 - powerpc-utils: 1.3.8-2.18 => 1.3.8-4.1 - psmisc: 23.0-6.10.1 => 23.0-6.13.1 - python3: 3.6.12-3.75.1 => 3.6.13-3.78.1 - python-base: 2.7.17-7.52.2 => 2.7.18-7.55.1 - python: 2.7.17-7.52.2 => 2.7.18-7.55.1 - qemu: 5.2.0-8.5 => 5.2.0-9.4 - raspberrypi-firmware-config: 2021.01.21-3.1 => 2021.03.10-1.1 - raspberrypi-firmware-dt: 2021.01.22-2.1 => 2021.03.15-1.1 - raspberrypi-firmware: 2021.01.21-3.1 => 2021.03.10-1.1 - regionServiceClientConfigEC2: 2.2.1-3.11.1 => 3.0.0-3.14.1 - ruby2: 2.5.8-4.11.1 => 2.5.8-4.14.1 - sca-appliance-agent: 1.3-2.16 => 1.3.1-1.1 - sca-appliance-broker: 1.3-2.16 => 1.3.1-1.1 - sca-appliance-common: 1.3-1.17 => 1.3-10.1 - sca-appliance-patdev: 1.3-1.17 => 1.3.1-1.1 - sca-patterns-sle11: 1.3.1-7.3.1 => 1.3.1-15.1 - sca-patterns-sle12: 1.0.1-7.3.1 => 1.0.2-1.1 - sca-patterns-sle15: 1.0.1-3.3.1 => 1.0.1-11.1 - snapper: 0.8.15-2.1 => 0.8.16-1.1 - spack: 0.16.0-2.1 => 0.16.1-1.1 - stunnel: 5.57-3.8.1 => 5.57-3.11.1 - supportutils: 3.1.14-4.1 => 3.1.14-5.1 - syslinux: 4.04-8.14 => 4.04-15.1 - systemd-presets-common-SUSE: 15-6.10 => 15-8.3.1 - systemd: 246.10-1.10 => 246.11-1.1 - transactional-update: 3.2.0-1.3 => 3.2.2-1.1 - velocity: 1.7-1.74 => 1.7-3.3.1 - wpa_supplicant: 2.9-4.23.1 => 2.9-4.26.1 - xen: 4.14.1_12-1.4 => 4.14.1_14-1.4 - xorg-x11-server: 1.20.3-22.5.16.1 => 1.20.3-22.5.22.1 - yast2-aduc: 1.1+git.7.30eec1d-1.63 => 2.2-3.3.11 - yast2-firewall: 4.3.10-1.3 => 4.3.11-1.1 - yast2-firstboot: 4.3.10-1.24 => 4.3.11-1.1 - yast2-installation: 4.3.34-1.1 => 4.3.36-1.1 - yast2-network: 4.3.57-1.1 => 4.3.63-1.1 - yast2-packager: 4.3.19-1.1 => 4.3.20-1.1 - yast2-pkg-bindings: 4.3.9-1.1 => 4.3.10-1.1 - yast2-ruby-bindings: 4.3.13-1.1 => 4.3.14-1.1 - yast2-security: 4.3.15-1.1 => 4.3.16-1.1 - yast2: 4.3.59-1.1 => 4.3.60-1.1 - yast2-storage-ng: 4.3.48-1.1 => 4.3.50-1.1 - yast2-theme: 4.3.7-1.1 => 4.3.8-1.1 - zstd: 1.4.4-1.3.1 => 1.4.4-1.6.1 Removed packages - redfish-finder - sca-patterns-edir - sca-patterns-filr - sca-patterns-groupwise - sca-patterns-oes Downgraded packages - libyui-doc: 4.0.1-1.1 => 3.9.3-1.46 - libyui-ncurses-doc: 4.0.2-1.1 => 2.54.5-1.57 - libyui-ncurses-pkg-doc: 4.0.1-1.1 => 2.50.7-1.10 - libyui-qt-doc: 4.0.3-1.1 => 2.52.4-1.9 - libyui-qt-graph-doc: 4.0.1-1.1 => 2.46.3-1.9 - libyui-qt-pkg-doc: 4.0.1-1.1 => 2.47.5-3.2.1 More information Schedule[5] Changelog[5] Known issues[6] Questions? If you have any question, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[7] [1]:https://suse.com/betaprogram/sle-beta/#releases [2]:https://www.suse.com/c/how-suse-builds-its-enterprise-lin ux-distribution-part-3/ [3]:https://suse.com/betaprogram/sle-beta/#download [4]:https://suse.com/betaprogram/sle-beta/#faq-reg [5]:https://suse.com/betaprogram/sle-beta/#changelogs [6]:https://suse.com/betaprogram/sle-beta/#knownissues [7]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Partner%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Apr 1 17:19:49 2021 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 1 Apr 2021 17:19:49 +0000 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Weekly Updates 20210401! In-Reply-To: <6065fca239d69_ad772bc-2a9@MacBouille.local.mail> References: <6065fca239d69_ad772bc-2a9@MacBouille.local.mail> Message-ID: <204FC7F3-C1B3-4439-BBFE-E8AC2ED97B7C@suse.com> Hi, Please note that, due to an issue in plymouth (bsc#1184087 - [Build 163.1] openQA test fails in first_boot - system login prompt can not show) causing stuck installed systems on aarch64 and ppc64le we are only shipping 20210401 for the x86_64 and s390x architecture. This is listed in the known issue section but it should have been included in the announcement. My bad and sorry for the inconvenience, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager Paris, France > On 1 Apr 2021, at 19:02, SUSE Public Beta Program wrote: > > Having trouble viewing this email? Please check the plain text version of this email. > > > We are happy to announce Weekly Updates 20210401 for SUSE Linux Enterprise 15 Service Pack 3! > > This mark an important step toward our upcoming Public Release Candidate, since from now on our Release Management team will only accept code submissions for security fixes and bug fixes! > > Download > Updates available since Public Beta > > Since SLE 15 SP2 Public Beta Program we are releasing weekly updates through our online channels during our SLE Public Beta Program. Please refer to our FAQ for more information. Note that you can even enable the Online Updates Channels during the installation to apply them before booting your system. > > This week we are providing the following: > > Added packages > > ? grafana-ha-cluster-dashboards 1.1.0+git.1605027022.a84d536-1.11.1 > ? grafana-sap-hana-dashboards 1.0.2+git.1600361067.f7c00d1-1.8.2 > ? grafana-sap-netweaver-dashboards 1.0.3+git.1601889366.9f71957-1.11.2 > ? grafana-sap-providers 1.1-1.8.1 > ? nginx-macros 0.0.1-1.1 > ? yast2-adcommon-python 1.6-3.3.10 > Updated Kernel > > ? kernel-source: 5.3.18-51.2 => 5.3.18-52.3 > Updated packages (selection) > > ? alsa-utils: 1.2.4-2.28 => 1.2.4-3.1 > ? autoyast2: 4.3.71-1.1 => 4.3.75-1.1 > ? bcm43xx-firmware: 20180314-20.2 => 20180314-21.1 > ? crmsh: 4.2.0+git.1609987436.0d3a9bf5-5.35.1 => 4.3.0+20210305.9db5c9a8-5.42.1 > ? dehydrated: 0.6.5-9.13 => 0.7.0-11.3.1 > ? dracut: 049.1+suse.185.g9324648a-3.21.1 => 049.1+suse.186.g320cc3d1-3.24.1 > ? efivar: 37-6.6.1 => 37-6.9.1 > ? filesystem: 15.0-9.2 => 15.0-11.3.2 > ? git: 2.26.2-3.28.2 => 2.26.2-3.31.1 > ? gnome-shell: 3.34.5-7.33 => 3.34.5-8.1 > ? gnutls: 3.6.7-14.7.1 => 3.6.7-14.10.2 > ? go1: 1.16-1.3.1 => 1.16.2-1.8.1 > ? golang-github-vpenso-prometheus_slurm_exporter: 0.15-1.27 => 0.17-1.3 > ? grub2: 2.04-17.2 => 2.04-18.4 > ? hawk2: 2.6.0+git.1613486511.51b6e37d-3.24.1 => 2.6.3+git.1614684118.af555ad9-3.27.1 > ? hostinfo: 1.0-18.15 => 1.0.6-1.1 > ? hwdata: 0.343-3.15.1 => 0.345-3.18.1 > ? kiwi-templates-JeOS: 15.2-24.6 => 15.3-1.1 > ? libunwind: 1.2.1-4.2.3 => 1.5.0-4.5.1 > ? libvirt: 7.1.0-1.3 => 7.1.0-2.1 > ? lua-lmod: 8.4.20-1.3 => 8.4.27-1.1 > ? multipath-tools: 0.8.5+12+suse.3b0e9ca-1.26 => 0.8.5+29+suse.5dabcd2-1.1 > ? nginx: 1.16.1-1.21 => 1.19.8-1.1 > ? openldap2: 2.4.46-9.45.1 => 2.4.46-9.48.1 > ? openssl-1_0_0: 1.0.2p-3.34.1 => 1.0.2p-3.37.1 > ? openssl-1_1: 1.1.1d-11.12.1 => 1.1.1d-11.20.1 > ? perl-DBD-SQLite: 1.54-1.31 => 1.66-1.1 > ? pipewire: 0.3.22-1.2 => 0.3.24-1.1 > ? plymouth: 0.9.5+git20190908+3abfab2-2.50 => 0.9.5+git20190908+3abfab2-3.3 > ? powerpc-utils: 1.3.8-2.18 => 1.3.8-4.1 > ? psmisc: 23.0-6.10.1 => 23.0-6.13.1 > ? python3: 3.6.12-3.75.1 => 3.6.13-3.78.1 > ? python-base: 2.7.17-7.52.2 => 2.7.18-7.55.1 > ? python: 2.7.17-7.52.2 => 2.7.18-7.55.1 > ? qemu: 5.2.0-8.5 => 5.2.0-9.4 > ? raspberrypi-firmware-config: 2021.01.21-3.1 => 2021.03.10-1.1 > ? raspberrypi-firmware-dt: 2021.01.22-2.1 => 2021.03.15-1.1 > ? raspberrypi-firmware: 2021.01.21-3.1 => 2021.03.10-1.1 > ? regionServiceClientConfigEC2: 2.2.1-3.11.1 => 3.0.0-3.14.1 > ? ruby2: 2.5.8-4.11.1 => 2.5.8-4.14.1 > ? sca-appliance-agent: 1.3-2.16 => 1.3.1-1.1 > ? sca-appliance-broker: 1.3-2.16 => 1.3.1-1.1 > ? sca-appliance-common: 1.3-1.17 => 1.3-10.1 > ? sca-appliance-patdev: 1.3-1.17 => 1.3.1-1.1 > ? sca-patterns-sle11: 1.3.1-7.3.1 => 1.3.1-15.1 > ? sca-patterns-sle12: 1.0.1-7.3.1 => 1.0.2-1.1 > ? sca-patterns-sle15: 1.0.1-3.3.1 => 1.0.1-11.1 > ? snapper: 0.8.15-2.1 => 0.8.16-1.1 > ? spack: 0.16.0-2.1 => 0.16.1-1.1 > ? stunnel: 5.57-3.8.1 => 5.57-3.11.1 > ? supportutils: 3.1.14-4.1 => 3.1.14-5.1 > ? syslinux: 4.04-8.14 => 4.04-15.1 > ? systemd-presets-common-SUSE: 15-6.10 => 15-8.3.1 > ? systemd: 246.10-1.10 => 246.11-1.1 > ? transactional-update: 3.2.0-1.3 => 3.2.2-1.1 > ? velocity: 1.7-1.74 => 1.7-3.3.1 > ? wpa_supplicant: 2.9-4.23.1 => 2.9-4.26.1 > ? xen: 4.14.1_12-1.4 => 4.14.1_14-1.4 > ? xorg-x11-server: 1.20.3-22.5.16.1 => 1.20.3-22.5.22.1 > ? yast2-aduc: 1.1+git.7.30eec1d-1.63 => 2.2-3.3.11 > ? yast2-firewall: 4.3.10-1.3 => 4.3.11-1.1 > ? yast2-firstboot: 4.3.10-1.24 => 4.3.11-1.1 > ? yast2-installation: 4.3.34-1.1 => 4.3.36-1.1 > ? yast2-network: 4.3.57-1.1 => 4.3.63-1.1 > ? yast2-packager: 4.3.19-1.1 => 4.3.20-1.1 > ? yast2-pkg-bindings: 4.3.9-1.1 => 4.3.10-1.1 > ? yast2-ruby-bindings: 4.3.13-1.1 => 4.3.14-1.1 > ? yast2-security: 4.3.15-1.1 => 4.3.16-1.1 > ? yast2: 4.3.59-1.1 => 4.3.60-1.1 > ? yast2-storage-ng: 4.3.48-1.1 => 4.3.50-1.1 > ? yast2-theme: 4.3.7-1.1 => 4.3.8-1.1 > ? zstd: 1.4.4-1.3.1 => 1.4.4-1.6.1 > Removed packages > > ? redfish-finder > ? sca-patterns-edir > ? sca-patterns-filr > ? sca-patterns-groupwise > ? sca-patterns-oes > Downgraded packages > > ? libyui-doc: 4.0.1-1.1 => 3.9.3-1.46 > ? libyui-ncurses-doc: 4.0.2-1.1 => 2.54.5-1.57 > ? libyui-ncurses-pkg-doc: 4.0.1-1.1 => 2.50.7-1.10 > ? libyui-qt-doc: 4.0.3-1.1 => 2.52.4-1.9 > ? libyui-qt-graph-doc: 4.0.1-1.1 => 2.46.3-1.9 > ? libyui-qt-pkg-doc: 4.0.1-1.1 => 2.47.5-3.2.1 > More information > > Schedule > Changelog > Known issues > Questions? > > If you have any question, please contact us at beta-programs at suse.com. > > Your SUSE Linux Enterprise team > > Click here to unsubscribe From Kevin.Salisbury at twinmro.com Mon Apr 5 11:51:31 2021 From: Kevin.Salisbury at twinmro.com (Kevin Salisbury) Date: Mon, 05 Apr 2021 07:51:31 -0400 Subject: Latest beta - chronyd / FIPS mode issue (resend to mail list) Message-ID: <606AF9C3020000C10043A3E7@mail.twinmro.com> I have confirmation of a carryover chronyd bug from SP2 into SP3 (bugzilla number 1173760). Steps to reproduce; - Built a new x86_64 SLES15 SP3 Beta box and updated. - Setup an internal time source for chronyd on install both manually and with autoyast - no issues. Time is fine. - Install FIPS pattern, and set grub bootloader kernel boot option 'fips=1' and restart - chronyd fails to load with internal time source. If a public time source is used for chronyd, it seems to load fine (but of course, one can't use a public source if servers are not supposed to see the internet or are "air gapped"). We suspect there needs to be something else done on the internal time source, or a local configuration change not documented for FIPS systems; we've tried several different internal time clock sources and manual edits of chronyd configurations -- nothing seems to work. The issue does not exist on SLES 12 systems. Curious to know if others in FIPS environments have seen this behavior with SLE 15 and if there's a workaround...(it seems that we are missing something very simple, admittedly we are not experts with chronyd yet, but so far SUSE support can replicate the issue - but has no solution for us either). This post is FYI only. This is a known issue, although not documented in the readme, it's going to limit deployment in many regulated environments... Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- NOTICE: This communication constitutes an electronic communication as defined within the Electronic Communication Privacy Act (ECPA). The entire contents of this email, including any attachments, are privileged, confidential and may contain technical data subject to Export Administration Regulations (EAR) or International Traffic in Arms Regulations (ITAR). This communication is for the intended viewer(s) only and may not be copied or disseminated without the written consent of TWIN MRO. If you are not the intended recipient, please contact the sender by return email and delete all copies of this communication. From malcolmlewis at cableone.net Mon Apr 5 12:41:47 2021 From: malcolmlewis at cableone.net (Malcolm) Date: Mon, 5 Apr 2021 07:41:47 -0500 Subject: Latest beta - chronyd / FIPS mode issue (resend to mail list) In-Reply-To: <606AF9C3020000C10043A3E7@mail.twinmro.com> References: <606AF9C3020000C10043A3E7@mail.twinmro.com> Message-ID: <20210405074147.2f180775@grover.homelinux.org> On Mon, 05 Apr 2021 07:51:31 -0400 "Kevin Salisbury" wrote: > I have confirmation of a carryover chronyd bug from SP2 into SP3 > (bugzilla number 1173760). > > Steps to reproduce; > - Built a new x86_64 SLES15 SP3 Beta box and updated. > - Setup an internal time source for chronyd on install both manually > and with autoyast - no issues. Time is fine. > - Install FIPS pattern, and set grub bootloader kernel boot option > 'fips=1' and restart > - chronyd fails to load with internal time source. If a public time > source is used for chronyd, it seems to load fine (but of course, one > can't use a public source if servers are not supposed to see the > internet or are "air gapped"). > > We suspect there needs to be something else done on the internal time > source, or a local configuration change not documented for FIPS > systems; we've tried several different internal time clock sources > and manual edits of chronyd configurations -- nothing seems to work. > The issue does not exist on SLES 12 systems. Curious to know if > others in FIPS environments have seen this behavior with SLE 15 and > if there's a workaround...(it seems that we are missing something > very simple, admittedly we are not experts with chronyd yet, but so > far SUSE support can replicate the issue - but has no solution for us > either). > > This post is FYI only. This is a known issue, although not documented > in the readme, it's going to limit deployment in many regulated > environments... > > Kevin > Hi Not a chrony expert or FIPS user either, but am using the aarch64 (RPi3) SLES 15 SP3 for a local time source with gps/pps/rtc which is working great. Have you run makestep, is the time in use UTC, timedatectrl looks good, cmos battery ok, are the pools disabled (/etc/chrony.d/pool.conf? Changed the stratum level? -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20210330 | GNOME Shell 3.38.3 | 5.11.6-1-default Intel DQ77MK | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/AMD/Nvidia up 9:20, 2 users, load average: 0.94, 1.12, 0.83 From Kevin.Salisbury at twinmro.com Mon Apr 5 14:22:55 2021 From: Kevin.Salisbury at twinmro.com (Kevin Salisbury) Date: Mon, 05 Apr 2021 10:22:55 -0400 Subject: Latest beta - chronyd / FIPS mode issue (resend to mail list) In-Reply-To: <20210405074147.2f180775@grover.homelinux.org> References: <606AF9C3020000C10043A3E7@mail.twinmro.com> <20210405074147.2f180775@grover.homelinux.org> Message-ID: <606B1D3F020000C10043A40C@mail.twinmro.com> Hi Malcolm, It's been a while, trust all is well. Yes unfortunately, everything works great until the system is placed into FIPS mode, then chronyd fails to run/start. My team just found out (as I was typing this reply) that if we create a new SLE 15 chronyd local timesource server on the network and we point the SLE 15 FIPS/chronyd clients to the new local chronyd server, the client chronyd loads properly and runs! But we can't run the actual chronyd time server system in FIPS mode even with a public source - so it is still a problem but we can work with this (one system being out of compliance instead of all systems being out of compliance). This is our workaround at the moment. It seems SLES15 chronyd clients can not speak to SLES 12 ntp local time clocks if the SLE15 chronyd system/kernel is running in FIPS mode... Kevin >>> On 4/5/2021 at 8:41 AM, wrote: On Mon, 05 Apr 2021 07:51:31 -0400 "Kevin Salisbury" wrote: > I have confirmation of a carryover chronyd bug from SP2 into SP3 > (bugzilla number 1173760). > > Steps to reproduce; > - Built a new x86_64 SLES15 SP3 Beta box and updated. > - Setup an internal time source for chronyd on install both manually > and with autoyast - no issues. Time is fine. > - Install FIPS pattern, and set grub bootloader kernel boot option > 'fips=1' and restart > - chronyd fails to load with internal time source. If a public time > source is used for chronyd, it seems to load fine (but of course, one > can't use a public source if servers are not supposed to see the > internet or are "air gapped"). > > We suspect there needs to be something else done on the internal time > source, or a local configuration change not documented for FIPS > systems; we've tried several different internal time clock sources > and manual edits of chronyd configurations -- nothing seems to work. > The issue does not exist on SLES 12 systems. Curious to know if > others in FIPS environments have seen this behavior with SLE 15 and > if there's a workaround...(it seems that we are missing something > very simple, admittedly we are not experts with chronyd yet, but so > far SUSE support can replicate the issue - but has no solution for us > either). > > This post is FYI only. This is a known issue, although not documented > in the readme, it's going to limit deployment in many regulated > environments... > > Kevin > Hi Not a chrony expert or FIPS user either, but am using the aarch64 (RPi3) SLES 15 SP3 for a local time source with gps/pps/rtc which is working great. Have you run makestep, is the time in use UTC, timedatectrl looks good, cmos battery ok, are the pools disabled (/etc/chrony.d/pool.conf? Changed the stratum level? -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20210330 | GNOME Shell 3.38.3 | 5.11.6-1-default Intel DQ77MK | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/AMD/Nvidia up 9:20, 2 users, load average: 0.94, 1.12, 0.83 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Tue Apr 6 08:18:23 2021 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 6 Apr 2021 08:18:23 +0000 Subject: Latest beta - chronyd / FIPS mode issue (resend to mail list) In-Reply-To: <606B1D3F020000C10043A40C@mail.twinmro.com> References: <606AF9C3020000C10043A3E7@mail.twinmro.com> <20210405074147.2f180775@grover.homelinux.org> <606B1D3F020000C10043A40C@mail.twinmro.com> Message-ID: Hi Kevin, Thanks a lot for this details report, could you please create a bug report with all the information you already shared here? Then I?ll link your bug to "bsc#1173760 - FIPS: chrony aborts in FIPS mode due to MD5" and I?ll ask for setting a new priority to your bug. Thanks again and have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager Paris, France > On 5 Apr 2021, at 16:22, Kevin Salisbury wrote: > > Hi Malcolm, > > It's been a while, trust all is well. > > Yes unfortunately, everything works great until the system is placed into FIPS mode, then chronyd fails to run/start. > > My team just found out (as I was typing this reply) that if we create a new SLE 15 chronyd local timesource server on the network and we point the SLE 15 FIPS/chronyd clients to the new local chronyd server, the client chronyd loads properly and runs! But we can't run the actual chronyd time server system in FIPS mode even with a public source - so it is still a problem but we can work with this (one system being out of compliance instead of all systems being out of compliance). This is our workaround at the moment. > > It seems SLES15 chronyd clients can not speak to SLES 12 ntp local time clocks if the SLE15 chronyd system/kernel is running in FIPS mode... > > Kevin > > > >>> On 4/5/2021 at 8:41 AM, wrote: > On Mon, 05 Apr 2021 07:51:31 -0400 > "Kevin Salisbury" wrote: > > > I have confirmation of a carryover chronyd bug from SP2 into SP3 > > > (bugzilla number 1173760). > > > > > > Steps to reproduce; > > > - Built a new x86_64 SLES15 SP3 Beta box and updated. > > > - Setup an internal time source for chronyd on install both manually > > > and with autoyast - no issues. Time is fine. > > > - Install FIPS pattern, and set grub bootloader kernel boot option > > > 'fips=1' and restart > > > - chronyd fails to load with internal time source. If a public time > > > source is used for chronyd, it seems to load fine (but of course, one > > > can't use a public source if servers are not supposed to see the > > > internet or are "air gapped"). > > > > > > We suspect there needs to be something else done on the internal time > > > source, or a local configuration change not documented for FIPS > > > systems; we've tried several different internal time clock sources > > > and manual edits of chronyd configurations -- nothing seems to work. > > > The issue does not exist on SLES 12 systems. Curious to know if > > > others in FIPS environments have seen this behavior with SLE 15 and > > > if there's a workaround...(it seems that we are missing something > > > very simple, admittedly we are not experts with chronyd yet, but so > > > far SUSE support can replicate the issue - but has no solution for us > > > either). > > > > > > This post is FYI only. This is a known issue, although not documented > > > in the readme, it's going to limit deployment in many regulated > > > environments... > > > > > > Kevin > > > > > Hi > Not a chrony expert or FIPS user either, but am using the aarch64 (RPi3) > SLES 15 SP3 for a local time source with gps/pps/rtc which is working > great. > > Have you run makestep, is the time in use UTC, timedatectrl looks good, > cmos battery ok, are the pools disabled (/etc/chrony.d/pool.conf? > > Changed the stratum level? > > -- > Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) > Tumbleweed 20210330 | GNOME Shell 3.38.3 | 5.11.6-1-default > Intel DQ77MK | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/AMD/Nvidia > up 9:20, 2 users, load average: 0.94, 1.12, 0.83 From LarsHendrik.Bussmann at Bertelsmann.de Tue Apr 6 16:49:16 2021 From: LarsHendrik.Bussmann at Bertelsmann.de (Bussmann, Lars Hendrik, NMD-I2.1) Date: Tue, 6 Apr 2021 16:49:16 +0000 Subject: systemd obsolete / legacy warnigns Message-ID: Hi, we start testing with SP3 and we noticed some systemd obsolete / legacy warnings. Apr 6 17:21:43 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/grub2-once.service:13: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Apr 6 18:13:17 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Apr 6 18:13:17 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/chronyd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/chronyd.pid ? /run/chronyd.pid; please update the unit file accordingly. Apr 6 18:16:55 sles15sp3vm systemd[1]: /usr/lib/systemd/system/vmtoolsd.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/vmtoolsd.pid ? /run/vmtoolsd.pid; please update the unit file accordingly. I created one bug for chrony ( #1184400 ) but I am unsure if this is the right approach as it looks like an general issue. When I search through all units of the basesystem and Server-Applications packages if found over 30 further units with the old syntax. e.g. /usr/lib/systemd/system/ipmievd.service /usr/lib/systemd/system/nfs-blkmap.service /usr/lib/systemd/system/rpc-statd.service /usr/lib/systemd/system/fancontrol.service /usr/lib/systemd/system/sssd.service Maybe there is an build option for systemd or it is possible create an "affects multiple packages" bug? Kind Regards, Lars From beta-programs at suse.com Fri Apr 9 06:45:43 2021 From: beta-programs at suse.com (SUSE Beta Program) Date: Fri, 09 Apr 2021 08:45:43 +0200 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Online Updates 20210409! Message-ID: <606ff81754f32_56402bc-247@MacBouille.local.mail> We are happy to announce Online Updates 20210409 for SUSE Linux Enterprise 15 Service Pack 3! This mark an important step toward our upcoming Public Release Candidate[1], since from now on our Release Management team[2] will only accept code submissions for security fixes and bug fixes! Download[3] Updates available since Public Beta Since SLE 15 SP2 Public Beta Program we are releasing updates through our online channels during our SLE Public Beta Program. Please refer to our FAQ[4] for more information. Note that you can even enable the Online Updates Channels during the installation to apply them before booting your system. This week we are providing the following: Kernel Application Binary Interface (kABI) freeze >From now on there won't be any changes regarding the set of in-kernel symbols used by drivers and other kernel modules (i.e kABI). Added packages - sapstartsrv-resource-agents 0.9.0+git.1615189486.815e798-1.3.1 Updated Kernel - kernel-source: 5.3.18-52.3 => 5.3.18-53.3 Updated packages (selection) - apache2-mod_security2: 2.9.2-1.34 => 2.9.2-3.3.1 - azure-cli-command-modules-nspkg: 2.0.1-3.3.3 => 2.0.3-6.4.1 - azure-cli-core: 2.0.45-6.3.3 => 2.14.2-6.7.1 - azure-cli-nspkg: 3.0.2-4.22 => 3.0.4-6.4.1 - azure-cli: 2.0.45-4.22 => 2.14.2-6.4.1 - azure-cli-telemetry: 1.0.0-1.31 => 1.0.6-3.4.1 - blog: 2.18-4.11 => 2.20-1.1 - clamsap: 0.99.25-2.37 => 0.101.9-4.3.1 - cloud-init: 20.2-8.39.8 => 20.2-8.42.1 - cloud-regionsrv: 8.0.1-2.16 => 8.0.5-4.5.2 - curl: 7.66.0-4.11.1 => 7.66.0-4.14.1 - fwupd: 1.5.3-1.43 => 1.5.8-1.2 - glibc: 2.31-6.5 => 2.31-7.7 - hwloc: 2.4.0-1.6 => 2.4.1-1.1 - irqbalance: 1.4.0-10.50 => 1.4.0-12.3.1 - kdump: 0.9.0-11.3.1 => 0.9.0-15.1 - libvirt: 7.1.0-2.1 => 7.1.0-3.1 - mdadm: 4.1-21.20 => 4.1-22.1 - MozillaFirefox: 78.8.0-8.32.2 => 78.9.0-8.35.1 - multipath-tools: 0.8.5+29+suse.5dabcd2-1.1 => 0.8.5+30+suse.633836e-1.1 - numactl: 2.0.11-2.18 => 2.0.11-11.1 - OpenIPMI: 2.0.25-5.27 => 2.0.25-7.3.1 - ovmf: 202008-7.16 => 202008-8.1 - PackageKit: 1.1.13-4.17.6 => 1.1.13-4.20.1 - parted: 3.2-11.14.1 => 3.2-19.1 - pesign-obs-integration: 10.1-10.22 => 10.1-11.1 - plymouth: 0.9.5+git20190908+3abfab2-3.3 => 0.9.5+git20190908+3abfab2-4.2 - powerpc-utils: 1.3.8-4.1 => 1.3.8-5.1 - scap-security-guide: 0.1.54-1.4.1 => 0.1.54-1.7.2 - sed: 4.4-2.11 => 4.4-11.2 - spack: 0.16.1-1.1 => 0.16.1-2.1 - squashfs: 4.3-1.29 => 4.4-1.1 - systemd: 246.11-1.1 => 246.13-1.2 - tomcat: 9.0.36-3.21.1 => 9.0.36-3.24.1 - util-linux: 2.36.2-1.12 => 2.36.2-2.5 - util-linux-systemd: 2.36.2-1.2 => 2.36.2-2.1 - wireguard-tools: 1.0.20200513-5.3.1 => 1.0.20200827-5.6.5 Removed packages - libreiserfs-0_3-0 - libreiserfs-devel More information Schedule[5] Changelog[5] Known issues[6] Questions? If you have any question, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[7] [1]:https://suse.com/betaprogram/sle-beta/#releases [2]:https://www.suse.com/c/how-suse-builds-its-enterprise-lin ux-distribution-part-3/ [3]:https://suse.com/betaprogram/sle-beta/#download [4]:https://suse.com/betaprogram/sle-beta/#faq-reg [5]:https://suse.com/betaprogram/sle-beta/#changelogs [6]:https://suse.com/betaprogram/sle-beta/#knownissues [7]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Partner%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Apr 15 14:13:08 2021 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 15 Apr 2021 14:13:08 +0000 Subject: systemd obsolete / legacy warnigns In-Reply-To: References: Message-ID: Hi, So bsc#1184400 was marked as resolved fixed, but I recommend to create a dedicated bug for the systemd obsolete / legacy warnings, this will allow us to assign the bug directly to our systemd maintainer. Anyway in the meantime, I?ll still try to find someone to help you here. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager Paris, France On 6 Apr 2021, at 18:49, Bussmann, Lars Hendrik, NMD-I2.1 > wrote: Hi, we start testing with SP3 and we noticed some systemd obsolete / legacy warnings. Apr 6 17:21:43 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/grub2-once.service:13: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Apr 6 18:13:17 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. Apr 6 18:13:17 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/chronyd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/chronyd.pid ? /run/chronyd.pid; please update the unit file accordingly. Apr 6 18:16:55 sles15sp3vm systemd[1]: /usr/lib/systemd/system/vmtoolsd.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/vmtoolsd.pid ? /run/vmtoolsd.pid; please update the unit file accordingly. I created one bug for chrony ( #1184400 ) but I am unsure if this is the right approach as it looks like an general issue. When I search through all units of the basesystem and Server-Applications packages if found over 30 further units with the old syntax. e.g. /usr/lib/systemd/system/ipmievd.service /usr/lib/systemd/system/nfs-blkmap.service /usr/lib/systemd/system/rpc-statd.service /usr/lib/systemd/system/fancontrol.service /usr/lib/systemd/system/sssd.service Maybe there is an build option for systemd or it is possible create an "affects multiple packages" bug? Kind Regards, Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: From dick.waite at ostiasolutions.com Thu Apr 15 15:16:48 2021 From: dick.waite at ostiasolutions.com (Ostia) Date: Thu, 15 Apr 2021 17:16:48 +0200 Subject: systemd obsolete / legacy warnigns In-Reply-To: References:

Message-ID: <20210415151648.5636183.34260.2600@ostiasolutions.com> An HTML attachment was scrubbed... URL: From beta-programs at suse.com Fri Apr 16 07:54:29 2021 From: beta-programs at suse.com (SUSE Beta Program) Date: Fri, 16 Apr 2021 09:54:29 +0200 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Online Updates 20210416! Message-ID: <607942b574cf8_fb42bc-2ed@MacBouille.local.mail> We are happy to announce Online Updates 20210416 for SUSE Linux Enterprise 15 Service Pack 3! This mark an important step toward our upcoming Public Release Candidate[1], since from now on our Release Management team[2] will only accept code submissions for security fixes and bug fixes! Download[3] Updates available since Public Beta Since SLE 15 SP2 Public Beta Program we are releasing updates through our online channels during our SLE Public Beta Program. Please refer to our FAQ[4] for more information. Note that you can even enable the Online Updates Channels during the installation to apply them before booting your system. This week we are providing the following: Kernel Application Binary Interface (kABI) freeze Since 20210409 there won't be any changes regarding the set of in-kernel symbols used by drivers and other kernel modules (i.e kABI). Added packages - petsc_3_14_5-{gnu-mpich-hpc,gnu-openmpi4-hpc,gnu-mvapich2-hpc ,gnu-openmpi3-hpc} 3.14.5-1.6 - trilinos_13_0_1-{gnu-mpich-hpc-devel,gnu-openmpi4-hpc-devel,g nu-mvapich2-hpc-devel,gnu-openmpi3-hpc-devel,hpc-doc} Updated Kernel - kernel-source: 5.3.18-53.3 => 5.3.18-54.2 Updated packages (selection) - 389-ds: 1.4.4.13~git0.6841d693f-1.6 => 1.4.4.14~git0.37dc95673-1.1 - autoyast2: 4.3.75-1.1 => 4.3.77-1.1 - btrfsprogs: 4.19.1-15.20 => 4.19.1-16.1 - ca-certificates: 2+git20210309.21162a6-1.2 => 2+git20210309.21162a6-2.1 - csync2: 2.0+git.1461714863.10636a4-4.3.1 => 2.0+git.1600444747.83b3644-1.1 - cups: 2.2.7-3.20.1 => 2.2.7-3.23.1 - dehydrated: 0.7.0-11.3.1 => 0.7.0-11.6.1 - ebtables: 2.0.10.4-11.39 => 2.0.11-1.1 - firewalld: 0.7.5-1.49 => 0.9.3-1.1 - fwupdate: 12-11.5.1 => 12-11.8.2 - ganglia-web: 3.7.4-1.56 => 3.7.5-1.1 - gdb: 10.1-8.21.2 => 10.1-8.24.1 - grub2: 2.04-18.8 => 2.04-19.2 - gssproxy: 0.8.2-3.3.2 => 0.8.2-3.6.1 - gzip: 1.10-3.3.1 => 1.10-3.8.1 - iptables: 1.8.3-1.36 => 1.8.7-1.1 - kdump: 0.9.0-15.1 => 0.9.0-16.1 - kiwi-templates-JeOS: 15.3-1.1 => 15.3-2.1 - libvirt: 7.1.0-3.1 => 7.1.0-4.1 - lua-lmod: 8.4.27-1.1 => 8.4.28-1.1 - nftables: 0.8.2-7.121 => 0.9.8-1.2 - numactl: 2.0.11-11.1 => 2.0.14-1.1 - open-iscsi: 2.1.3-29.12 => 2.1.4-30.1 - powerpc-utils: 1.3.8-5.1 => 1.3.8-6.1 - rmt-server: 2.6.6-1.2 => 2.6.8-1.1 - sapconf: 5.0.0-7.12.2 => 5.0.2-7.15.1 - sca-patterns-sle15: 1.0.1-11.1 => 1.0.1-12.1 - slurm: 20.11.4-1.3 => 20.11.5-1.2 - smartmontools: 7.0-1.52 => 7.0-6.1 - sssd: 1.16.1-20.68 => 1.16.1-21.1 - systemd: 246.13-1.2 => 246.13-2.1 - tpm2-tss-engine: 1.0.1-2.8 => 1.0.1-4.3.1 - umoci: 0.4.4-4.3.1 => 0.4.6-3.9.1 - wicked: 0.6.65-1.2 => 0.6.65-2.1 - xdm: 1.1.11-13.6.1 => 1.1.11-13.9.1 - yast2-network: 4.3.63-1.1 => 4.3.64-1.1 - yast2-packager: 4.3.20-1.1 => 4.3.21-1.1 - yast2-schema: 4.3.21-1.2 => 4.3.22-1.1 Removed packages - petsc_3_14_4-{gnu-mpich-hpc-devel,gnu-openmpi4-hpc-devel,gnu- mvapich2-hpc-devel,gnu-openmpi3-hpc-devel} - trilinos_13_0_0-{gnu-mpich-hpc-devel,gnu-openmpi4-hpc-devel,g nu-mvapich2-hpc-devel,gnu-openmpi3-hpc-devel,hpc-doc} Downgraded packages - sssd-32bit: 1.16.1-20.68 => 1.16.1-15.32 More information Schedule[5] Changelog[5] Known issues[6] Questions? If you have any question, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[7] [1]:https://suse.com/betaprogram/sle-beta/#releases [2]:https://www.suse.com/c/how-suse-builds-its-enterprise-lin ux-distribution-part-3/ [3]:https://suse.com/betaprogram/sle-beta/#download [4]:https://suse.com/betaprogram/sle-beta/#faq-reg [5]:https://suse.com/betaprogram/sle-beta/#changelogs [6]:https://suse.com/betaprogram/sle-beta/#knownissues [7]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Partner%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at suse.com Thu Apr 22 15:42:57 2021 From: beta-programs at suse.com (SUSE Beta Program) Date: Thu, 22 Apr 2021 15:42:57 +0000 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Online Updates 20210422! Message-ID: <608199819678b_1082ae8bceee60073049@4402e8b3144f.mail> We are happy to announce Online Updates 20210422 for SUSE Linux Enterprise 15 Service Pack 3! This mark an important step toward our upcoming Public Release Candidate[1], since from now on our Release Management team[2] will only accept code submissions for security fixes and bug fixes! Download[3] Updates available since Public Beta Since SLE 15 SP2 Public Beta Program we are releasing updates through our online channels during our SLE Public Beta Program. Please refer to our FAQ[4] for more information. Note that you can even enable the Online Updates Channels during the installation to apply them before booting your system. This week we are providing the following: Kernel Application Binary Interface (kABI) freeze Since 20210409 there won't be any changes regarding the set of in-kernel symbols used by drivers and other kernel modules (i.e kABI). Updated Kernel - kernel-source: 5.3.18-54.2 => 5.3.18-55.1 Updated packages (selection) - cifs-utils: 6.9-5.6.1 => 6.9-5.9.1 - clamav: 0.103.0-3.23.1 => 0.103.2-3.26.1 - crash: 7.2.8-20.76 => 7.2.9-21.2 - crmsh: 4.3.0+20210305.9db5c9a8-5.42.1 => 4.3.0+20210315.5d07d43e-5.45.1 - irqbalance: 1.4.0-12.3.1 => 1.4.0-12.6.1 - libreoffice: 7.1.1.2-1.13 => 7.1.2.2-1.2 - lifecycle-data-sle-module-live-patching: 15-4.48.1 => 15-4.51.1 - makedumpfile: 1.6.7-4.1 => 1.6.7-9.1 - MozillaThunderbird: 78.8.0-8.15.4 => 78.9.1-8.20.1 - openldap2: 2.4.46-9.48.1 => 2.4.46-9.51.1 - opensc: 0.19.0-1.14 => 0.19.0-3.7.1 - perl-Bootloader: 0.933-1.2 => 0.934-1.1 - procps: 3.3.15-7.13.2 => 3.3.15-7.16.1 - raspberrypi-firmware-config: 2021.03.10-1.1 => 2021.03.10-2.1 - raspberrypi-firmware-dt: 2021.03.15-1.1 => 2021.03.15-2.1 - s390-tools: 2.15.1-5.13 => 2.15.1-6.1 - salt: 3002.2-4.3 => 3002.2-5.1 - sblim-sfcb: 1.4.9-5.3.1 => 1.4.9-5.6.1 - spamassassin: 3.4.2-12.5.1 => 3.4.5-12.10.1 - systemd: 246.13-2.1 => 246.13-3.1 - u-boot-rpiarm64: 2021.01-2.1 => 2021.01-4.1 - vsftpd: 3.0.3-7.7.9 => 3.0.3-7.16.1 - wpa_supplicant: 2.9-4.26.1 => 2.9-4.29.1 - xorg-x11-server: 1.20.3-22.5.22.1 => 1.20.3-22.5.25.1 - yast2-installation: 4.3.36-1.1 => 4.3.37-1.1 More information Schedule[5] Changelog[5] Known issues[6] Questions? If you have any question, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[7] [1]:https://suse.com/betaprogram/sle-beta/#releases [2]:https://www.suse.com/c/how-suse-builds-its-enterprise-lin ux-distribution-part-3/ [3]:https://suse.com/betaprogram/sle-beta/#download [4]:https://suse.com/betaprogram/sle-beta/#faq-reg [5]:https://suse.com/betaprogram/sle-beta/#changelogs [6]:https://suse.com/betaprogram/sle-beta/#knownissues [7]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Partner%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at suse.com Thu Apr 29 14:42:00 2021 From: beta-programs at suse.com (SUSE Beta Program) Date: Thu, 29 Apr 2021 16:42:00 +0200 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP3 Public Release Candidate is out! Message-ID: <608ac5b893022_92362bc-2ed@MacBouille.local.mail> We are happy to announce Public Release Candidate for SUSE Linux Enterprise 15 Service Pack 3! This is an important milestone towards our official release! It is without saying that now our Release Management team[1] will only accept code submissions for security fixes and the most important bug fixes! Everything else will be considered for Maintenance Updates post-release or to be integrated in the future Service Pack 4. Download[2] What happened since Public Beta In less than 2 months since the Public Beta, we have updated 383 packages, added 136 new ones and removed a grant total of 26 packages. All of these were provided to you as updates through our online channels, but now we have respinned our Installation Media which are available for download[3]. Please refer to our FAQ[3] for more information on our Update Channels. You can check out our complete changelog files[4] for more information, but be aware that these files are huge and contain a lot of information. Thus we recommend you to look for specific package entries or to check out our updated Release Notes[5] for a more general and abstracted source of information. Kernel Application Binary Interface (kABI) freeze Since Online Update 20210409 there won't be any changes regarding the set of in-kernel symbols used by drivers and other kernel modules (i.e kABI). Updated Kernel - kernel-source: 5.3.18-56.2 Updated packages (selection) - 389-ds: 1.4.4.14~git0.37dc95673-1.1 - autoyast2 4.3.77-1.1 - MozillaFirefox: 78.10.0-8.38.1 - MozillaThunderbird: 78.10.0-8.23.1 - gcc10: 10.2.1+git583-1.3.4 - gcc7: 7.5.0+r278197-4.25.1 - git: 2.26.2-3.31.1 - gnome-shell: 3.34.5-8.1 - go1.16: 1.16.2-1.8.1 - nginx: 1.19.8-1.1 - nodejs14: 14.16.0-5.9.1 - openldap2: 2.4.46-9.51.1 - openssl-1_0_0: 1.0.2p-3.37.1 - openssl-1_1: 1.1.1d-11.20.1 - mariadb: 10.5.8-1.5 - postgresql13: 13.2-5.6.1 - python39: 3.9.0-3.21 - qemu: 5.2.0-9.16 - redis: 6.0.10-1.7.1 - rmt-server: 2.6.8-1.1 - ruby2: 2.5.8-4.14.1 - s390-tools: 2.15.1-6.4 - salt: 3002.2-6.1 - scap-security-guide: 0.1.54-1.7.2 - shim: 15.4-1.2 - slurm: 20.11.5-bp153.1.2 - systemd: 246.13-4.2 - transactional-update: 3.2.2-1.1 - wicked: 0.6.65-2.1 openSUSE Leap 15.3 RC Since openSUSE Leap and SUSE Linux Enterprise are developed in sync, openSUSE Leap 15.3 is also entering the Release Candidate phase[6]. One more thing William Brown from our 389-ds team taped an awesome video about Migrating to 389-ds from openldap2[7] on YouTube. Please check it out and we would be happy to hear about your migration test with SLES 15 SP3. More information Schedule[8] Changelog[9] Known issues[9] Questions? If you have any questions, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[10] [1]:https://www.suse.com/c/how-suse-builds-its-enterprise-lin ux-distribution-part-3/ [2]:https://suse.com/betaprogram/sle-beta/#download [3]:https://suse.com/betaprogram/sle-beta/#faq-reg [4]:https://suse.com/betaprogram/sle-beta/#changelogs [5]:https://suse.com/betaprogram/sle-beta/#releasenotes [6]:https://news.opensuse.org/2021/04/28/opensuse-leap-153-en ters-rc-phase/ [7]:https://youtu.be/qrbtWOXOhtA [8]:https://suse.com/betaprogram/sle-beta/#releases [9]:https://suse.com/betaprogram/sle-beta/#knownissues [10]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from %20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SL E%20Public%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: