From meissner at suse.de Tue Oct 1 00:30:22 2019 From: meissner at suse.de (Marcus Meissner) Date: Tue, 1 Oct 2019 08:30:22 +0200 Subject: [sle-beta] SLES 12 SP5 Support for Python 2.7 In-Reply-To: References: Message-ID: <20191001063022.GE9734@suse.de> Hi, On Tue, Oct 01, 2019 at 01:00:33AM +0000, Jay Nitikman wrote: > According to https://pythonclock.org/ official support for Python 2.7 will end just as SLES 12 SP5 is released. > > What does this mean as far as security fixes for Python 2.7 in SLES 12 SP5? SUSE supports all packages until the EOL of the respective Service Pack or Product they are contained in. Even if upstream discontinues support. So we will continue to support python 2.7 there basically until the EOL of SLE12. In SLE15 we have moved Python2 to the "Python2" module with SP1 in preparation for an earlier EOL. Ciao, Marcus From beta-programs at lists.suse.com Thu Oct 3 03:41:37 2019 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Thu, 03 Oct 2019 11:41:37 +0200 Subject: [sle-beta] [ANNOUNCE] SLE 12 SP5 Product Family RC 2 is available! Message-ID: <5d95c251a2662_1af2b28d61a25f034111@zourite.lab.gb.mail> We are happy to announce Release Candidate 2 for SUSE Linux Enterprise 12 Service Pack 5: - SUSE Linux Enterprise Server (SLES), - SUSE Linux Enterprise Server for SAP (SLES for SAP), - SUSE Linux Enterprise Just Enough Operating System (JeOS), - SUSE Linux Enterprise High Availability (SLEHA and SLEHA GEO), - SUSE Linux Enterprise Workstation Extension (SLEWE), - SUSE Linux Enterprise for High Performance Computing (SLEHPC). Download ?[1] Changelogs ?[2] Important Notice - SUSE Linux Enterprise 12 Service Pack 5 (SLE 12 SP5) is the last Service Pack of the SUSE Linux Enterprise Server 12 (SLE 12) code stream. - This Service Pack 5 is a consolidation Service Pack release. - No Desktop product for SLE 12 SP5: -- SUSE Linux Enterprise Desktop (SLED) 12 End Of Life is on Dec 31st 2019[3], and thus we will not deliver SLED 12 SP5. Customers are kindly ask to use either SUSE Linux Enterprise Server 12 SP5 with the Workstation Extension or migrate to SLED 15 SP1. - Kernel used for SLE 12 SP5 is the same as SLE 15 SP1, - Beta Registration Codes are available to get access to the Online Channels through SCC, SMT, RMT or SUSE Manager. Please request your Beta Registration Codes at beta-programs at lists.suse.com[4]. Notable Changes NEW Added SLES 12 SP5 Vagrant images: - Vagrant[5] is a tool that provides a unified workflow for the creation, deployment and management of virtual development environments. - We now provide SLES Vagrant boxes for x86_64 and aarch64. The x86_64 boxes support the libvirt and Virtualbox provider, the aarch64 box only the libvirt provider. Updated Packages - curl 7.60.0-9.5 - drbd 9.0.14+git.62f906cf-9.3 - drbd-utils 9.4.0-7.2 - libpgp-error 1.29 - libvirt 5.1.0-11.3 (bsc#1149100) - mokutil 0.2.0-21.1 - samba 4.10.5+git.116 - sles-manuals_* packages got updated and translated, except sled-manuals_zh_TW - wicked 0.6.57 - xen 4.12.1_04 - yast2-cluster 3.4.1 - yast2-country 3.2.18 - yast2-storage 3.2.22 Downgraded Packages - python-python-daemon 2.1.2 Package was downgraded to sync version across product portfolio More information SLE Beta Page ?[6] Release Notes ?[7] Known issues ?[8] Have fun beta testing! Your SUSE Linux Enterprise Team Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe.[9] [1]:https://www.suse.com/betaprogram/sle-beta/#download [2]:https://www.suse.com/betaprogram/sle-beta/#changelogs [3]:https://www.suse.com/lifecycle/ [4]:mailto:beta-programs at lists.suse.com?subject=Beta%20Regist ration%20Code%20Request%20for%20SLE%2012%20SP5 [5]:https://www.vagrantup.com/ [6]:https://www.suse.com/betaprogram/sle-beta [7]:https://www.suse.com/betaprogram/sle-beta/#releasenotes [8]:https://www.suse.com/betaprogram/sle-beta/#knownissues [9]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe%2 0from%20SLE%20Beta&body=Unsubscribe%20from%20SLE%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Mon Oct 7 07:08:49 2019 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Mon, 07 Oct 2019 15:08:49 +0200 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 11 enablement on SUSE Customer Center Message-ID: <5d9b38e132f50_33e22aee7764e610280ee@zourite.lab.gb.mail> Dear customer, we need your assistance! As you might be aware, SUSE? separated from Micro Focus?[1] earlier this year. While the legal separation has been completed in March, there are technical aspects of the separation still ahead of us. As of today, updates for SUSE Linux Enterprise 11 are delivered through the Novell Customer Center, and as this is going to remain with Micro Focus, effective February 2020, we need to redirect all customers still relying on SLE 11 to the SUSE Customer Center. Two beta test scenarios If you have a running SLE 11 system that currently connects directly to the Novell Customer Center (i.e., does not connect to an instance of SMT or SUSE Manager) and would be willing to help, you can follow this How To[2] which gives guidance on what to do in two scenarios: - Automatic migration[3], we developed a patch to make the transition for our customers as seamless as possible, and would kindly ask for your support in trying it out before we roll it out to everyone. - Manual activation[4], we focused on Manual activation of a SUSE Linux Enterprise Server 11 directly to SCC. Please note that SLE 11 systems connected to SMT/RMT and SUSE Manager are NOT part of this beta test but will be covered for the official enablement. How To ?[5] We are thankful for your support in trying this out and we welcome your feedback. As usual you can contact us at beta-programs at lists.suse.com Have fun beta testing! Your SUSE Linux Enterprise and SUSE Customer Center Team Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe.[5] [1]:https://www.suse.com/c/news/suse-completes-move-to-indepe ndence-reaffirms-commitment-to-customers-partners-and-open-so urce-communities-as-industrys-largest-independent-open-source -company/ [2]:https://www.suse.com/betaprogram/scc-enablement-sle11/ [3]:https://www.suse.com/betaprogram/scc-enablement-sle11/#au tomatic [4]:https://www.suse.com/betaprogram/scc-enablement-sle11/#ma nual [5]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe%2 0from%20SLE%20Beta&body=Unsubscribe -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Sat Oct 26 03:19:15 2019 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Sat, 26 Oct 2019 11:19:15 +0200 Subject: [sle-beta] [ANNOUNCE] SLE 12 SP5 Product Family GMC is available! Message-ID: <5db40f931c157_4c2c2af983c5e5fc317ec@zourite.lab.gb.mail> We are happy to announce Gold Master Candidate for SUSE Linux Enterprise 12 Service Pack 5: - SUSE Linux Enterprise Server (SLES), - SUSE Linux Enterprise Server for SAP (SLES for SAP), - SUSE Linux Enterprise Just Enough Operating System (JeOS), - SUSE Linux Enterprise High Availability (SLEHA and SLEHA GEO), - SUSE Linux Enterprise Workstation Extension (SLEWE), - SUSE Linux Enterprise for High Performance Computing (SLEHPC). Download ?[1] Changelogs ?[2] Important Notice - SUSE Linux Enterprise 12 Service Pack 5 (SLE 12 SP5) is the last Service Pack of the SUSE Linux Enterprise Server 12 (SLE 12) code stream. - This Service Pack 5 is a consolidation Service Pack release. - No Desktop product for SLE 12 SP5: -- SUSE Linux Enterprise Desktop (SLED) 12 End Of Life is on Dec 31st 2019[3], and thus we will not deliver SLED 12 SP5. Customers are kindly ask to use either SUSE Linux Enterprise Server 12 SP5 with the Workstation Extension or migrate to SLED 15 SP1. - Kernel used for SLE 12 SP5 is the same as SLE 15 SP1, Notable Changes NEW Added SLES 12 SP5 Vagrant images: - Vagrant[4] is a tool that provides a unified workflow for the creation, deployment and management of virtual development environments. - We now provide SLES Vagrant boxes for x86_64 and aarch64. The x86_64 boxes support the libvirt and Virtualbox provider, the aarch64 box only the libvirt provider. We did further polishing and bug fixing to gain higher quality with our Gold Master Candidate More information SLE Beta Page ?[5] Release Notes ?[6] Known issues ?[7] Have fun beta testing! Your SUSE Linux Enterprise Team Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe.[8] [1]:https://www.suse.com/betaprogram/sle-beta/#download [2]:https://www.suse.com/betaprogram/sle-beta/#changelogs [3]:https://www.suse.com/lifecycle/ [4]:https://www.vagrantup.com/ [5]:https://www.suse.com/betaprogram/sle-beta [6]:https://www.suse.com/betaprogram/sle-beta/#releasenotes [7]:https://www.suse.com/betaprogram/sle-beta/#knownissues [8]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe%2 0from%20SLE%20Beta&body=Unsubscribe%20from%20SLE%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Oct 31 05:26:59 2019 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 31 Oct 2019 11:26:59 +0000 Subject: [sle-beta] [Request For Comment] - bsc#1151302 blkdiscard on KVM guest VM is not working as expected Message-ID: Hi everyone, We would like to know if any of you experienced the issue below or if you have any means to reproduce this one. Internal only bug - bsc#1151302 - blkdiscard on KVM guest VM is not working as expected But here is the description of the bug: > KVM : SLES15SP1 > > 0. Install SLES12SP5 RC1 build > 1. Add one scsi device > 2. Create a partition on the device and ext4 file system on it > 3. mount the ext4 partition > 4. Run blkdiscard on the the thin device > > Observation 1 : > ------------ > > # blkdiscard -v /dev/sda > /dev/sda: Discarded 1073741824 bytes from the offset 0 > > # fdisk -l /dev/sda > Disk /dev/sda: 1 GiB, 1073741824 bytes, 2097152 sectors > Disk model: QEMU HARDDISK > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: gpt > Disk identifier: D37C1387-D72C-374F-9844-3F1F9922DF47 > > Device Start End Sectors Size Type > /dev/sda1 2048 2097118 2095071 1023M Linux filesystem > > > Sysfs details : > > # cat /sys/block/sda/queue/discard_max_hw_bytes > 1073741824 > # cat /sys/block/sda/queue/discard_max_bytes > 1073741824 > # cat /sys/block/sda/queue/discard_granularity > 4096 > # cat /sys/block/sda/queue/discard_ > discard_granularity discard_max_bytes discard_max_hw_bytes discard_zeroes_data > # cat /sys/block/sda/queue/max_discard_segments > 1 > > > Observation 2: > -------------- > > 1. sg lba status command shows "bad field" when executed on a thin device > # sg_get_lba_status /dev/sda > Get LBA Status command: bad field in cdb > > # lsscsi > [0:0:0:1] disk QEMU QEMU HARDDISK 2.5+ /dev/sda > > > # sg_vpd -a /dev/sda | grep -i "provisioning type" > Provisioning type: 2 > > > Expectation: > ------------ > 1. blkdiscard should discard properly > 2. sg lba status should be functioning. Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager