From fcrozat at suse.com Tue May 2 05:20:38 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 02 May 2017 13:20:38 +0200 Subject: [sle-beta] SLES12 SP3 kernel source. In-Reply-To: <7baa34ed9e234a3ca0e0f5eb966d7f4e@vrtsxchclupin12.community.veritas.com> References: <7baa34ed9e234a3ca0e0f5eb966d7f4e@vrtsxchclupin12.community.veritas.com> Message-ID: <1493724038.5094.9.camel@suse.com> Le mardi 02 mai 2017 ? 08:58 +0000, Anil Dhaneshwar a ?crit?: > Hi, > ? > I need kernel source package of 4.4.59-1 kernel. I checked the SLES12 > SP3 DVD2 but I am not able to find the package into it. > ? > #:~/sles12sp3.dvd2 # mount SLE-12-SP2-Server-DVD-x86_64-GM-DVD2.iso > /mnt You are looking as SP2 GM iso, not SP3 Beta1 iso.. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Anil.Dhaneshwar at veritas.com Tue May 2 05:38:31 2017 From: Anil.Dhaneshwar at veritas.com (Anil Dhaneshwar) Date: Tue, 2 May 2017 11:38:31 +0000 Subject: [sle-beta] SLES12 SP3 kernel source. In-Reply-To: <1493724038.5094.9.camel@suse.com> References: <7baa34ed9e234a3ca0e0f5eb966d7f4e@vrtsxchclupin12.community.veritas.com> <1493724038.5094.9.camel@suse.com> Message-ID: <514505ad72ae4feba576cd596e320a0c@vrtsxchclupin12.community.veritas.com> -----Original Message----- From: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] On Behalf Of Frederic Crozat Sent: Tuesday, May 02, 2017 4:51 PM To: sle-beta at lists.suse.com Subject: Re: [sle-beta] SLES12 SP3 kernel source. Le mardi 02 mai 2017 ? 08:58 +0000, Anil Dhaneshwar a ?crit?: > Hi, > ? > I need kernel source package of 4.4.59-1 kernel. I checked the SLES12 > SP3 DVD2 but I am not able to find the package into it. > ? > #:~/sles12sp3.dvd2 # mount SLE-12-SP2-Server-DVD-x86_64-GM-DVD2.iso > /mnt You are looking as SP2 GM iso, not SP3 Beta1 iso.. Thanks for your quick help ! Where can I find git repository of the suse kernel (e.g 4.4.59-1-default) ? Thanks, Anil -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta From fcrozat at suse.com Tue May 2 05:53:29 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 02 May 2017 13:53:29 +0200 Subject: [sle-beta] SLES12 SP3 kernel source. In-Reply-To: <514505ad72ae4feba576cd596e320a0c@vrtsxchclupin12.community.veritas.com> References: <7baa34ed9e234a3ca0e0f5eb966d7f4e@vrtsxchclupin12.community.veritas.com> <1493724038.5094.9.camel@suse.com> <514505ad72ae4feba576cd596e320a0c@vrtsxchclupin12.community.veritas.com> Message-ID: <1493726009.5094.11.camel@suse.com> Le mardi 02 mai 2017 ? 11:38 +0000, Anil Dhaneshwar a ?crit?: > > -----Original Message----- > From: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists. > suse.com] On Behalf Of Frederic Crozat > Sent: Tuesday, May 02, 2017 4:51 PM > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] SLES12 SP3 kernel source. > > Le mardi 02 mai 2017 ? 08:58 +0000, Anil Dhaneshwar a ?crit?: > > > > Hi, > > ? > > I need kernel source package of 4.4.59-1 kernel. I checked the > > SLES12 > > SP3 DVD2 but I am not able to find the package into it. > > ? > > #:~/sles12sp3.dvd2 # mount SLE-12-SP2-Server-DVD-x86_64-GM-DVD2.iso > > /mnt > > You are looking as SP2 GM iso, not SP3 Beta1 iso.. > > Thanks for your quick help ! > > Where can I find git repository of the suse kernel (e.g 4.4.59-1- > default)??? SUSE Kernel sources are available at?http://kernel.suse.com/ -- Frederic Crozat Enterprise Desktop Release Manager SUSE From beta-programs at lists.suse.com Thu May 4 10:38:55 2017 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Thu, 04 May 2017 18:38:55 +0200 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 12 SP3 Beta 2 is available! Message-ID: <590b591fbf67e_55bf59531c810c1@par-dod7.mail> == [ANNOUNCE] SUSE Linux Enterprise 12 SP3 Beta 1 is available! We are happy to announce SUSE Linux Enterprise 12 SP3 Beta 1: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Just Enough Operating System (JeOS), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLEHA), SUSE Linux Enterprise Workstation Extension (SLEWE), and SUSE Linux Enterprise Software Development Kit (SLESDK). Download[2] We are thankful for your support in trying out our beta products and we welcome your feedback. == More informations SLE Beta Page[1] Release Notes[3] Known Issues[4] Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, 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. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/ [2]https://www.suse.com/betaprogram/sle-beta/#download [3]https://www.suse.com/betaprogram/sle-beta/#releasenotes [4]https://www.suse.com/betaprogram/sle-beta/#knownissues -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Thu May 4 23:24:49 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 5 May 2017 05:24:49 +0000 Subject: [sle-beta] SLES12-SP-3 Beta3 - Bug 1033202 Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010282D8BA@daeexmbx1.eur.ad.sag> Grand Morning, Ran a Beta2 update on a VMware SLES12-SP-3 Beta1 machine. Looks grand bar Bug 1033202 is still with us. Have a very good day. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Thu May 4 23:26:07 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 5 May 2017 05:26:07 +0000 Subject: [sle-beta] SLES12-SP-3 Beta2 - Bug 1033202 Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010282D962@daeexmbx1.eur.ad.sag> Sorry Beta2 update... __R ________________________________ From: Waite, Dick (External) Sent: 05 May 2017 07:24 To: sle-beta at lists.suse.com Subject: SLES12-SP-3 Beta3 - Bug 1033202 Grand Morning, Ran a Beta2 update on a VMware SLES12-SP-3 Beta1 machine. Looks grand bar Bug 1033202 is still with us. Have a very good day. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Fri May 5 08:14:11 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 5 May 2017 16:14:11 +0200 Subject: [sle-beta] Changelogs between Beta 1 and Beta 2 Message-ID: <37A3EF21-9FDB-475E-9FEC-C466AE3977CB@suse.com> Hi, I have added the changelogs between SLE 12 SP3 Beta 1 and Beta 2 at: https://www.suse.com/betaprogram/sle-beta/#changelogs I would also like to remind you that we are open to feedback on https://www.suse.com/betaprogram/sle-beta/ or on any informations you feel like missing for this beta. Have a nice (beta testing) week-end, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From lukas.ocilka at suse.com Tue May 9 07:31:02 2017 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Tue, 9 May 2017 15:31:02 +0200 Subject: [sle-beta] SLES12-SP-3 Beta2 - Bug 1033202 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010282D962@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010282D962@daeexmbx1.eur.ad.sag> Message-ID: <6ac01c76-21ba-abdd-e357-ee151ffdf545@suse.com> Dne 5.5.2017 v 07:26 Dick (External) Waite napsal(a): > Sorry Beta2 update... Hi, Thanks for checking again. The team is currently taking a look at the issue. We'll keep you updated in the bug itself. Have a nice day Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux Sent from my Zarma Haka 3.0 From lukas.ocilka at suse.com Wed May 10 04:55:22 2017 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Wed, 10 May 2017 12:55:22 +0200 Subject: [sle-beta] SLES12-SP-3 Beta2 - Bug 1033202 In-Reply-To: <6ac01c76-21ba-abdd-e357-ee151ffdf545@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D010282D962@daeexmbx1.eur.ad.sag> <6ac01c76-21ba-abdd-e357-ee151ffdf545@suse.com> Message-ID: Dne 9.5.2017 v 15:31 Lukas Ocilka napsal(a): > Dne 5.5.2017 v 07:26 Dick (External) Waite napsal(a): >> Sorry Beta2 update... > > Hi, > > Thanks for checking again. The team is currently taking a look at the > issue. We'll keep you updated in the bug itself. Just for the record, this bug has been fixed and the fix will be available in the very next release. The change itself was actually really minimal, see https://github.com/openSUSE/gfxboot/pull/24/files but knowing what to change and where was a bigger task. Thanks for testing! Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux Sent from my Zarma Haka 3.0 From Dick.Waite at softwareag.com Thu May 11 08:51:55 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Thu, 11 May 2017 14:51:55 +0000 Subject: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> Grand Day, I found the message at the bottom from Vincent to ?lists.suse.com? on Tuesday. He feels it should not need the ?test repo? any more. He asked if I?d try it out and post my output for comments on this list. I used a VMware Workstation machine. I had SP-3 Beta1 running on the machine. I took a check point and the did an update with Yast2 and the Beta2 .iso file. That ran grand and I took another check point. I?m not too familiar with the good ?zipper? but it does what I want, so if I should have given it more options or used other command, please speak up. The machine is running with a Beta SCC code. So here we are at the Beta2 check point, my simple IVP ran Okay (not shown). # We are at a running SP-3 Beta2 migrated system rjw02-12-1-2:~ # cat /etc/issue Welcome to SUSE Linux Enterprise Server 12 SP3 Beta2 (x86_64) - Kernel \r (\l). rjw02-12-1-2:~ # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+----------------------------------------------------------------------------------------------+----------------------------------------------+---------+-----------+-------- 1 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Pool | SLE-Module-Legacy12-Debuginfo-Pool | No | ---- | ---- 2 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Updates | SLE-Module-Legacy12-Debuginfo-Updates | No | ---- | ---- 3 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Pool | SLE-Module-Legacy12-Pool | Yes | (r ) Yes | No 4 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Source-Pool | SLE-Module-Legacy12-Source-Pool | No | ---- | ---- 5 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Updates | SLE-Module-Legacy12-Updates | Yes | (r ) Yes | Yes 6 | SLES12-SP3-12.3-0 | SLES12-SP3-12.3-0 | No | ---- | ---- 7 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Pool | SLES12-SP3-Debuginfo-Pool | No | ---- | ---- 8 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Updates | SLES12-SP3-Debuginfo-Updates | No | ---- | ---- 9 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Pool | SLES12-SP3-Pool | Yes | (r ) Yes | No 10 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Source-Pool | SLES12-SP3-Source-Pool | No | ---- | ---- 11 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Updates | SLES12-SP3-Updates | Yes | (r ) Yes | Yes 12 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Pool | SLE-SDK12-SP3-Debuginfo-Pool | No | ---- | ---- 13 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Updates | SLE-SDK12-SP3-Debuginfo-Updates | No | ---- | ---- 14 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Pool | SLE-SDK12-SP3-Pool | Yes | (r ) Yes | No 15 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Source-Pool | SLE-SDK12-SP3-Source-Pool | No | ---- | ---- 16 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Updates | SLE-SDK12-SP3-Updates | Yes | (r ) Yes | Yes 17 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Pool | SLE-Module-Web-Scripting12-Debuginfo-Pool | No | ---- | ---- 18 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Updates | SLE-Module-Web-Scripting12-Debuginfo-Updates | No | ---- | ---- 19 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | Yes | (r ) Yes | No 20 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Source-Pool | SLE-Module-Web-Scripting12-Source-Pool | No | ---- | ---- 21 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | Yes | (r ) Yes | Yes rjw02-12-1-2:~ # ###################################### So going back to the "Before Beta2 check point" ........ rjw02-12-1-2:~ # cat /etc/issue Welcome to SUSE Linux Enterprise Server 12 SP3 Beta1 (x86_64) - Kernel \r (\l). The Beta1 check point?.. rjw02-12-1-2:~ # # we are now back at Beta1 rjw02-12-1-2:~ # rjw02-12-1-2:~ # rjw02-12-1-2:~ # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+----------------------------------------------------------------------------------------------+----------------------------------------------+---------+-----------+-------- 1 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Pool | SLE-Module-Legacy12-Debuginfo-Pool | No | ---- | ---- 2 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Updates | SLE-Module-Legacy12-Debuginfo-Updates | No | ---- | ---- 3 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Pool | SLE-Module-Legacy12-Pool | Yes | (r ) Yes | No 4 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Source-Pool | SLE-Module-Legacy12-Source-Pool | No | ---- | ---- 5 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Updates | SLE-Module-Legacy12-Updates | Yes | (r ) Yes | Yes 6 | SLES12-SP3-12.3-0 | SLES12-SP3-12.3-0 | Yes | (r ) Yes | No 7 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Pool | SLES12-SP3-Debuginfo-Pool | No | ---- | ---- 8 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Updates | SLES12-SP3-Debuginfo-Updates | No | ---- | ---- 9 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Pool | SLES12-SP3-Pool | Yes | (r ) Yes | No 10 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Source-Pool | SLES12-SP3-Source-Pool | No | ---- | ---- 11 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Updates | SLES12-SP3-Updates | Yes | (r ) Yes | Yes 12 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Pool | SLE-SDK12-SP3-Debuginfo-Pool | No | ---- | ---- 13 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Updates | SLE-SDK12-SP3-Debuginfo-Updates | No | ---- | ---- 14 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Pool | SLE-SDK12-SP3-Pool | Yes | (r ) Yes | No 15 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Source-Pool | SLE-SDK12-SP3-Source-Pool | No | ---- | ---- 16 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Updates | SLE-SDK12-SP3-Updates | Yes | (r ) Yes | Yes 17 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Pool | SLE-Module-Web-Scripting12-Debuginfo-Pool | No | ---- | ---- 18 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Updates | SLE-Module-Web-Scripting12-Debuginfo-Updates | No | ---- | ---- 19 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | Yes | (r ) Yes | No 20 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Source-Pool | SLE-Module-Web-Scripting12-Source-Pool | No | ---- | ---- 21 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | Yes | (r ) Yes | Yes rjw02-12-1-2:~ # # These are the repositories I can see rjw02-12-1-2:~ # rjw02-12-1-2:~ # zypper info zypper-migration-plugin Refreshing service 'Legacy_Module_12_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64'. Refreshing service 'Web_and_Scripting_Module_12_x86_64'. Loading repository data... Reading installed packages... Information for package zypper-migration-plugin: ------------------------------------------------ Repository : SLES12-SP3-Pool Name : zypper-migration-plugin Version : 0.10-12.4 Arch : noarch Vendor : SUSE LLC Support Level : Level 3 Installed Size : 16.7 KiB Installed : Yes Status : up-to-date Source package : zypper-migration-plugin-0.10-12.4.src Summary : Zypper subcommand for online migration Description : Zypper subcommand for online migration to new service pack. rjw02-12-1-2:~ # # we do have a zypper-migration-plugin and it's up-2-date ????? rjw02-12-1-2:~ # rjw02-12-1-2:~ # # so lets try a migration from SP-3 Beta1 to Beta2 rjw02-12-1-2:~ # rjw02-12-1-2:~ # zypper migration --help Usage: zypper migration [options] --[no-]allow-vendor-change Allow vendor change -v, --[no-]verbose Increase verbosity -q, --[no-]quiet Suppress normal output, print only error messages -n, --non-interactive Do not ask anything, use default answers automatically --query Query available migration options and exit --disable-repos Disable obsolete repositories without asking --migration N Select migration option N --from REPO Restrict upgrade to specified repository -r, --repo REPO Load only the specified repository -l, --auto-agree-with-licenses Automatically say 'yes' to third party license confirmation prompt --debug-solver Create solver test case for debugging --recommends Install also recommended packages --no-recommends Do not install recommended packages --replacefiles Install the packages even if they replace files from other packages --details Show the detailed installation summary --download MODE Set the download-install mode --download-only Replace repositories and download the packages, do not install. WARNING: Upgrade with 'zypper dist-upgrade' as soon as possible. rjw02-12-1-2:~ # # just cheking what "help" will show us... rjw02-12-1-2:~ # zypper migration --query Executing 'zypper refresh' Repository 'SLE-Module-Legacy12-Pool' is up to date. Repository 'SLE-Module-Legacy12-Updates' is up to date. Repository 'SLES12-SP3-12.3-0' is up to date. Retrieving repository 'SLES12-SP3-Pool' metadata ............................................................................................................................[done] Building repository 'SLES12-SP3-Pool' cache .................................................................................................................................[done] Repository 'SLES12-SP3-Updates' is up to date. Retrieving repository 'SLE-SDK12-SP3-Pool' metadata .........................................................................................................................[done] Building repository 'SLE-SDK12-SP3-Pool' cache ..............................................................................................................................[done] Repository 'SLE-SDK12-SP3-Updates' is up to date. Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --no-refresh patch-check --updatestack-only' Loading repository data... Reading installed packages... Considering 0 out of 1 applicable patches: 0 patches needed (0 security patches) No migration available. rjw02-12-1-2:~ # # It's saying "No migration available." rjw02-12-1-2:~ # # do we push on.... This is running on a VMware Workstation and I do have a check point at a good Beta2 level... rjw02-12-1-2:~ # zypper migration Executing 'zypper refresh' Repository 'SLE-Module-Legacy12-Pool' is up to date. Repository 'SLE-Module-Legacy12-Updates' is up to date. Repository 'SLES12-SP3-12.3-0' is up to date. Repository 'SLES12-SP3-Pool' is up to date. Repository 'SLES12-SP3-Updates' is up to date. Repository 'SLE-SDK12-SP3-Pool' is up to date. Repository 'SLE-SDK12-SP3-Updates' is up to date. Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --no-refresh patch-check --updatestack-only' Loading repository data... Reading installed packages... Considering 0 out of 1 applicable patches: 0 patches needed (0 security patches) No migration available. Not a surprising result ;o) rjw02-12-1-2:~ # # Ummmm the same message.... So it seems to run the command Okay but does not ?migrate from Beta1 to beta2? Should I have given it more commands or options to commands ???? Your input very welcome?. __R ############################################################# original post ###################################################### [sles-beta] [ANNOUNCE] Online Migration from SLES12 to SLES12-SP1 Beta Vincent Moutoussamy vmoutoussamy at suse.com Thu Sep 17 08:21:18 MDT 2015 Good news everyone, The tools for the Service Pack Online Migration between SLES 12 GA and SLES 12 SP1 Beta is now available for beta testing. The online migration between service packs allows to migrate a system to a new service pack while the system is still running. It is not necessary to download a new DVD and boot from that for an upgrade. == Requirements == In order to do an online update, the following requirements must be met : - SLES 12 as base system, - SLES 12 subscribed to : - SCC : Please use the registration key sent to you for the SLES 12 SP1 Beta Program. For more information please check our last communication about these keys: [ANNOUNCE] Beta test Subscription key for SLE 12 SP1 Beta. For any issue about the subscription, please contact us at beta-programs at lists.suse.com. - SMT : SMT needs to be the one from the update channel of SLES12 SP1 Beta3. == Run an Online Migration == 1) Add the repository with the beta migration tools : # zypper ar -f http://beta.suse.com/private/SLE12/SP1-BETA/SUSE:SLE-12:MigrationTest.repo You should now see something like that : # zypper lr # | Alias | Name | Enabled | GPG Check | Refresh --+-----------------------------------------------------------------+------------------------------------------------------------------------+---------+-----------+-------- 1 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Debuginfo-Pool | SLES12-Debuginfo-Pool | No | ---- | No 2 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Debuginfo-Updates | SLES12-Debuginfo-Updates | No | ---- | Yes 3 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Pool | SLES12-Pool | Yes | (r ) Yes | No 4 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Updates | SLES12-Updates | Yes | (r ) Yes | Yes 5 | SUSE_SLE-12_MigrationTest | testing project for backporting online migration to SLE 12 GA (SLE_12) | Yes | ( p) Yes | Yes 2) Update everything from the new added repository # zypper dup --from SUSE_SLE-12_MigrationTest 3) Install the migration tools (only one of them is necessary, based on your preference) # zypper in yast2-migration zypper-migration-plugin 4) Perform the migration itself In SLE11, the migration tool was known as wagon (or YaST wagon module), it?s now call simply ?migration" a) via YaST: run 'yast2 migration' and follow the work-flow b) via zypper: run 'zypper migration' and follow the instructions you get via your terminal. To see all options, run 'zypper migration --help' If the migration is aborted, the system needs to be (manually) re-registered with the old products via SUSEConnect; in future versions, this will be handled automatically. Thank you for your feedback, Your SUSE Linux Enterprise Team -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Thu May 11 21:31:47 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 12 May 2017 03:31:47 +0000 Subject: [sle-beta] [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag>, <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010289AAFA@daeexmbx1.eur.ad.sag> Grand New Friday, By default the good migration service works on SP-n to SP-n+1 So are we not looking for a "flag" to tell Migration we are now in Beta / RC / GMC / GM mode ? I tried to get some more output, words from others would be very welcome.... Have the "Migration Team" access to the forum ? rjw02-12-1-2:~ # zypper migration --query Executing 'zypper refresh' Repository 'SLE-Module-Legacy12-Pool' is up to date. Repository 'SLE-Module-Legacy12-Updates' is up to date. Repository 'SLES12-SP3-12.3-0' is up to date. Repository 'SLES12-SP3-Pool' is up to date. Repository 'SLES12-SP3-Updates' is up to date. Repository 'SLE-SDK12-SP3-Pool' is up to date. Repository 'SLE-SDK12-SP3-Updates' is up to date. Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --no-refresh patch-check --updatestack-only' Loading repository data... Reading installed packages... Considering 0 out of 1 applicable patches: 0 patches needed (0 security patches) No migration available. rjw02-12-1-2:~ # zypper migration --help Usage: zypper migration [options] --[no-]allow-vendor-change Allow vendor change -v, --[no-]verbose Increase verbosity -q, --[no-]quiet Suppress normal output, print only error messages -n, --non-interactive Do not ask anything, use default answers automatically --query Query available migration options and exit --disable-repos Disable obsolete repositories without asking --migration N Select migration option N --from REPO Restrict upgrade to specified repository -r, --repo REPO Load only the specified repository -l, --auto-agree-with-licenses Automatically say 'yes' to third party license confirmation prompt --debug-solver Create solver test case for debugging --recommends Install also recommended packages --no-recommends Do not install recommended packages --replacefiles Install the packages even if they replace files from other packages --details Show the detailed installation summary --download MODE Set the download-install mode --download-only Replace repositories and download the packages, do not install. WARNING: Upgrade with 'zypper dist-upgrade' as soon as possible. rjw02-12-1-2:~ # zypper migration --details Executing 'zypper refresh' Repository 'SLE-Module-Legacy12-Pool' is up to date. Repository 'SLE-Module-Legacy12-Updates' is up to date. Repository 'SLES12-SP3-12.3-0' is up to date. Repository 'SLES12-SP3-Pool' is up to date. Repository 'SLES12-SP3-Updates' is up to date. Repository 'SLE-SDK12-SP3-Pool' is up to date. Repository 'SLE-SDK12-SP3-Updates' is up to date. Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --no-refresh patch-check --updatestack-only' Loading repository data... Reading installed packages... Considering 0 out of 1 applicable patches: 0 patches needed (0 security patches) No migration available. rjw02-12-1-2:~ # zypper lp Refreshing service 'Legacy_Module_12_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64'. Refreshing service 'Web_and_Scripting_Module_12_x86_64'. Loading repository data... Reading installed packages... Repository | Name | Category | Severity | Interactive | Status | Summary -------------------+---------------------------------+-------------+----------+-------------+--------+------------------------------ SLES12-SP3-Updates | SUSE-SLE-SERVER-12-SP3-2017-734 | recommended | low | --- | needed | Recommended update for hwinfo Found 1 applicable patch: 1 patch needed (0 security patches) rjw02-12-1-2:~ # zypper patch Refreshing service 'Legacy_Module_12_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64'. Refreshing service 'Web_and_Scripting_Module_12_x86_64'. Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW patch is going to be installed: SUSE-SLE-SERVER-12-SP3-2017-734 The following package is going to be upgraded: hwinfo 1 package to upgrade. Overall download size: 720.1 KiB. Already cached: 0 B. After the operation, additional 27.2 KiB will be used. Continue? [y/n/...? shows all options] (y): Retrieving package hwinfo-21.45-1.1.x86_64 (1/1), 720.1 KiB ( 3.0 MiB unpacked) Retrieving: hwinfo-21.45-1.1.x86_64.rpm .......................................................................................................[done] Checking for file conflicts: ..................................................................................................................[done] (1/1) Installing: hwinfo-21.45-1.1.x86_64 .....................................................................................................[done] rjw02-12-1-2:~ # rjw02-12-1-2:~ # rjw02-12-1-2:~ # zypper migration --query Executing 'zypper refresh' Repository 'SLE-Module-Legacy12-Pool' is up to date. Repository 'SLE-Module-Legacy12-Updates' is up to date. Repository 'SLES12-SP3-12.3-0' is up to date. Repository 'SLES12-SP3-Pool' is up to date. Repository 'SLES12-SP3-Updates' is up to date. Repository 'SLE-SDK12-SP3-Pool' is up to date. Repository 'SLE-SDK12-SP3-Updates' is up to date. Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --no-refresh patch-check --updatestack-only' Loading repository data... Reading installed packages... 0 patches needed (0 security patches) No migration available. rjw02-12-1-2:~ # SUSEConnect --status-text Installed Products: ------------------------------------------ Legacy Module (sle-module-legacy/12/x86_64) Registered ------------------------------------------ SUSE Linux Enterprise Software Development Kit 12 (sle-sdk/12.3/x86_64) Registered ------------------------------------------ Web and Scripting Module (sle-module-web-scripting/12/x86_64) Registered ------------------------------------------ SUSE Linux Enterprise Server 12 SP3 (SLES/12.3/x86_64) Registered Subscription: Regcode: Starts at: 2017-04-06 00:00:00 UTC Expires at: 2017-09-03 00:00:00 UTC Status: ACTIVE Type: test ------------------------------------------ rjw02-12-1-2:~ # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+----------------------------------------------------------------------------------------------+----------------------------------------------+---------+-----------+-------- 1 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Pool | SLE-Module-Legacy12-Debuginfo-Pool | No | ---- | ---- 2 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Updates | SLE-Module-Legacy12-Debuginfo-Updates | No | ---- | ---- 3 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Pool | SLE-Module-Legacy12-Pool | Yes | (r ) Yes | No 4 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Source-Pool | SLE-Module-Legacy12-Source-Pool | No | ---- | ---- 5 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Updates | SLE-Module-Legacy12-Updates | Yes | (r ) Yes | Yes 6 | SLES12-SP3-12.3-0 | SLES12-SP3-12.3-0 | Yes | (r ) Yes | No 7 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Pool | SLES12-SP3-Debuginfo-Pool | No | ---- | ---- 8 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Updates | SLES12-SP3-Debuginfo-Updates | No | ---- | ---- 9 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Pool | SLES12-SP3-Pool | Yes | (r ) Yes | No 10 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Source-Pool | SLES12-SP3-Source-Pool | No | ---- | ---- 11 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Updates | SLES12-SP3-Updates | Yes | (r ) Yes | Yes 12 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Pool | SLE-SDK12-SP3-Debuginfo-Pool | No | ---- | ---- 13 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Updates | SLE-SDK12-SP3-Debuginfo-Updates | No | ---- | ---- 14 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Pool | SLE-SDK12-SP3-Pool | Yes | (r ) Yes | No 15 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Source-Pool | SLE-SDK12-SP3-Source-Pool | No | ---- | ---- 16 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Updates | SLE-SDK12-SP3-Updates | Yes | (r ) Yes | Yes 17 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Pool | SLE-Module-Web-Scripting12-Debuginfo-Pool | No | ---- | ---- 18 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Updates | SLE-Module-Web-Scripting12-Debuginfo-Updates | No | ---- | ---- 19 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | Yes | (r ) Yes | No 20 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Source-Pool | SLE-Module-Web-Scripting12-Source-Pool | No | ---- | ---- 21 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | Yes | (r ) Yes | Yes rjw02-12-1-2:~ # zypper ls # | Alias | Name | Enabled | GPG Check | Refresh | Type --+--------------------------------------------------------------+--------------------------------------------------------------+---------+-----------+---------+------ 1 | Legacy_Module_12_x86_64 | Legacy_Module_12_x86_64 | Yes | ---- | Yes | ris 2 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64 | Yes | ---- | Yes | ris 3 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64 | Yes | ---- | Yes | ris 4 | Web_and_Scripting_Module_12_x86_64 | Web_and_Scripting_Module_12_x86_64 | Yes | ---- | Yes | ris 5 | SLES12-SP3-12.3-0 | SLES12-SP3-12.3-0 | Yes | (r ) Yes | No | yast2 rjw02-12-1-2:~ # rjw02-12-1-2:~ # rjw02-12-1-2:~ # zypper migration --help Usage: zypper migration [options] --[no-]allow-vendor-change Allow vendor change -v, --[no-]verbose Increase verbosity -q, --[no-]quiet Suppress normal output, print only error messages -n, --non-interactive Do not ask anything, use default answers automatically --query Query available migration options and exit --disable-repos Disable obsolete repositories without asking --migration N Select migration option N --from REPO Restrict upgrade to specified repository -r, --repo REPO Load only the specified repository -l, --auto-agree-with-licenses Automatically say 'yes' to third party license confirmation prompt --debug-solver Create solver test case for debugging --recommends Install also recommended packages --no-recommends Do not install recommended packages --replacefiles Install the packages even if they replace files from other packages --details Show the detailed installation summary --download MODE Set the download-install mode --download-only Replace repositories and download the packages, do not install. WARNING: Upgrade with 'zypper dist-upgrade' as soon as possible. rjw02-12-1-2:~ # zypper migration --query --help Usage: zypper migration [options] --[no-]allow-vendor-change Allow vendor change -v, --[no-]verbose Increase verbosity -q, --[no-]quiet Suppress normal output, print only error messages -n, --non-interactive Do not ask anything, use default answers automatically --query Query available migration options and exit --disable-repos Disable obsolete repositories without asking --migration N Select migration option N --from REPO Restrict upgrade to specified repository -r, --repo REPO Load only the specified repository -l, --auto-agree-with-licenses Automatically say 'yes' to third party license confirmation prompt --debug-solver Create solver test case for debugging --recommends Install also recommended packages --no-recommends Do not install recommended packages --replacefiles Install the packages even if they replace files from other packages --details Show the detailed installation summary --download MODE Set the download-install mode --download-only Replace repositories and download the packages, do not install. WARNING: Upgrade with 'zypper dist-upgrade' as soon as possible. rjw02-12-1-2:~ # zypper migration -v --query Executing 'zypper --verbose refresh' Verbosity: 1 Initializing Target Specified repositories: Skipping disabled repository 'SLE-Module-Legacy12-Debuginfo-Pool' Skipping disabled repository 'SLE-Module-Legacy12-Debuginfo-Updates' Checking whether to refresh metadata for SLE-Module-Legacy12-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Legacy12-Pool' is up to date. Skipping disabled repository 'SLE-Module-Legacy12-Source-Pool' Checking whether to refresh metadata for SLE-Module-Legacy12-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Legacy12-Updates' is up to date. Checking whether to refresh metadata for SLES12-SP3-12.3-0 Repository 'SLES12-SP3-12.3-0' is up to date. Skipping disabled repository 'SLES12-SP3-Debuginfo-Pool' Skipping disabled repository 'SLES12-SP3-Debuginfo-Updates' Checking whether to refresh metadata for SLES12-SP3-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLES12-SP3-Pool' is up to date. Skipping disabled repository 'SLES12-SP3-Source-Pool' Checking whether to refresh metadata for SLES12-SP3-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLES12-SP3-Updates' is up to date. Skipping disabled repository 'SLE-SDK12-SP3-Debuginfo-Pool' Skipping disabled repository 'SLE-SDK12-SP3-Debuginfo-Updates' Checking whether to refresh metadata for SLE-SDK12-SP3-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-SDK12-SP3-Pool' is up to date. Skipping disabled repository 'SLE-SDK12-SP3-Source-Pool' Checking whether to refresh metadata for SLE-SDK12-SP3-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-SDK12-SP3-Updates' is up to date. Skipping disabled repository 'SLE-Module-Web-Scripting12-Debuginfo-Pool' Skipping disabled repository 'SLE-Module-Web-Scripting12-Debuginfo-Updates' Checking whether to refresh metadata for SLE-Module-Web-Scripting12-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Skipping disabled repository 'SLE-Module-Web-Scripting12-Source-Pool' Checking whether to refresh metadata for SLE-Module-Web-Scripting12-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --verbose --no-refresh patch-check --updatestack-only' Verbosity: 1 Autorefresh disabled. Initializing Target Loading repository data... Reading installed packages... Force resolution: No 0 patches needed (0 security patches) Installed products: sle-module-legacy/12/x86_64 sle-sdk/12.3/x86_64 sle-module-web-scripting/12/x86_64 SLES/12.3/x86_64 No migration available. rjw02-12-1-2:~ # zypper migration -v --migration beta2 /usr/lib/zypper/commands/zypper-migration:196:in `
': invalid argument: --migration beta2 (OptionParser::InvalidArgument) '/usr/lib/zypper/commands/zypper-migration' exited with status 1 rjw02-12-1-2:~ # zypper migration -v --migration 2 Executing 'zypper --verbose refresh' Verbosity: 1 Initializing Target Specified repositories: Skipping disabled repository 'SLE-Module-Legacy12-Debuginfo-Pool' Skipping disabled repository 'SLE-Module-Legacy12-Debuginfo-Updates' Checking whether to refresh metadata for SLE-Module-Legacy12-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Legacy12-Pool' is up to date. Skipping disabled repository 'SLE-Module-Legacy12-Source-Pool' Checking whether to refresh metadata for SLE-Module-Legacy12-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Legacy12-Updates' is up to date. Checking whether to refresh metadata for SLES12-SP3-12.3-0 Repository 'SLES12-SP3-12.3-0' is up to date. Skipping disabled repository 'SLES12-SP3-Debuginfo-Pool' Skipping disabled repository 'SLES12-SP3-Debuginfo-Updates' Checking whether to refresh metadata for SLES12-SP3-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLES12-SP3-Pool' is up to date. Skipping disabled repository 'SLES12-SP3-Source-Pool' Checking whether to refresh metadata for SLES12-SP3-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLES12-SP3-Updates' is up to date. Skipping disabled repository 'SLE-SDK12-SP3-Debuginfo-Pool' Skipping disabled repository 'SLE-SDK12-SP3-Debuginfo-Updates' Checking whether to refresh metadata for SLE-SDK12-SP3-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-SDK12-SP3-Pool' is up to date. Skipping disabled repository 'SLE-SDK12-SP3-Source-Pool' Checking whether to refresh metadata for SLE-SDK12-SP3-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-SDK12-SP3-Updates' is up to date. Skipping disabled repository 'SLE-Module-Web-Scripting12-Debuginfo-Pool' Skipping disabled repository 'SLE-Module-Web-Scripting12-Debuginfo-Updates' Checking whether to refresh metadata for SLE-Module-Web-Scripting12-Pool Retrieving: media ........................................................................................................................................................[done] Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Web-Scripting12-Pool' is up to date. Skipping disabled repository 'SLE-Module-Web-Scripting12-Source-Pool' Checking whether to refresh metadata for SLE-Module-Web-Scripting12-Updates Retrieving: repomd.xml ...................................................................................................................................................[done] Repository 'SLE-Module-Web-Scripting12-Updates' is up to date. All repositories have been refreshed. Executing 'zypper --verbose --no-refresh patch-check --updatestack-only' Verbosity: 1 Autorefresh disabled. Initializing Target Loading repository data... Reading installed packages... Force resolution: No 0 patches needed (0 security patches) Installed products: sle-module-legacy/12/x86_64 sle-sdk/12.3/x86_64 sle-module-web-scripting/12/x86_64 SLES/12.3/x86_64 No migration available. rjw02-12-1-2:~ # Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Thu May 11 22:48:50 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 12 May 2017 04:48:50 +0000 Subject: [sle-beta] SLES12-SP-3 Beta2 - Bug 1033202 In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76D010282D962@daeexmbx1.eur.ad.sag> <6ac01c76-21ba-abdd-e357-ee151ffdf545@suse.com>, Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010289ABBB@daeexmbx1.eur.ad.sag> Many Thanks for the update Lukas. So the release on the 18th May, I'll make a note to check my UK/GB flags ;o) __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Lukas Ocilka [lukas.ocilka at suse.com] Sent: 10 May 2017 12:55 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] SLES12-SP-3 Beta2 - Bug 1033202 Dne 9.5.2017 v 15:31 Lukas Ocilka napsal(a): > Dne 5.5.2017 v 07:26 Dick (External) Waite napsal(a): >> Sorry Beta2 update... > > Hi, > > Thanks for checking again. The team is currently taking a look at the > issue. We'll keep you updated in the bug itself. Just for the record, this bug has been fixed and the fix will be available in the very next release. The change itself was actually really minimal, see https://github.com/openSUSE/gfxboot/pull/24/files but knowing what to change and where was a bigger task. Thanks for testing! Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux Sent from my Zarma Haka 3.0 _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From fcrozat at suse.com Fri May 12 01:50:28 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 12 May 2017 09:50:28 +0200 Subject: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> Message-ID: <1494575428.5094.107.camel@suse.com> Le jeudi 11 mai 2017 ? 14:51 +0000, Waite, Dick (External) a ?crit?: > So it seems to run the command Okay but does not ?migrate from Beta1 > to beta2? Should I have given it more commands or options to commands > ???? zypper migration is only to be used to migrate from a service pack to another. Update between beta is not in scope of zypper migration. Migration between beta/RC/GMC milestones is not supported but if you want to try, you should run "zypper dup".? -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Fri May 12 02:22:53 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 12 May 2017 08:22:53 +0000 Subject: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <1494575428.5094.107.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag>, <1494575428.5094.107.camel@suse.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010289AD8E@daeexmbx1.eur.ad.sag> Many Thanks for the update Frederic. I will try your suggestion, being able to avoid the download of the *.iso update would be very welcome. __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Frederic Crozat [fcrozat at suse.com] Sent: 12 May 2017 09:50 To: sle-beta at lists.suse.com' Subject: Re: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration Le jeudi 11 mai 2017 ? 14:51 +0000, Waite, Dick (External) a ?crit : > So it seems to run the command Okay but does not ?migrate from Beta1 > to beta2? Should I have given it more commands or options to commands > ???? zypper migration is only to be used to migrate from a service pack to another. Update between beta is not in scope of zypper migration. Migration between beta/RC/GMC milestones is not supported but if you want to try, you should run "zypper dup". -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Dick.Waite at softwareag.com Sat May 13 08:46:48 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sat, 13 May 2017 14:46:48 +0000 Subject: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010289AD8E@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag>, <1494575428.5094.107.camel@suse.com>, <46AC8C81C10B8C48820201DF2AE1D76D010289AD8E@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E84E2AD@daeexmbx1.eur.ad.sag> Grand Saturday Frederic, Just the job... I now have eight VMware virtual machine saying they are running SP-3 Beta3 ;o) not sure if that is the "real" Beta3 (May 18th) but the zypper DUP runs look grand. I used this on both SP-3 Beta1 and Beta2 level machines. Now sure I would do it on physical machine, but then I don't have many of those around now. 1) take a "checkpoint" 2) zypper refresh 3) zypper dup plus some options sometimes 4) cat /etc/issue If issues: back to the checkpoint 1) SUSEConnect --cleanup 2) SUSEConnect -r nnnnnnnnnnn 3) yast2 4) register what's needed 5) SUSEConnect --status-text 6) shutdown -h now 7) take new checkpoint 8) zypper refresh 9) zypper DUP ..... 10) cat /etc/issue The virtual machines that got switched between physical machines often need a --cleanup So now I think I can spend more time checking Adabas on the Beta's than getting the Beta's ready to run. With "migration" looking good for SPn to SPn+1 and DUP for the Beta/RC/GM's life is looking good... As I said I'm getting Beta3 output after the DUP from /etc/issue ??? I'll run a few more tomorrow, while listening to what looks to be a grand F1 race... Tuesday in SAG I'll try this on a s390x. It's a "virtual machine" running a z/VM, just taking the "checkpoint" needs a little VM/CMS knowledge. The "Migration" on s390 from SP-2 to SP-3 ran well on four s390x, the only issues was a self inflected one so I think the DUP has a very good chance of running. After all, Linux is Linux is Linux no mater what the hardware might be.... Just the thought, the DUP is a "migration". Maybe one could have an option to say this is not SP to SP+n but a Beta to Beta/RC/GMC/GM Many Thanks. __R ________________________________________ From: Waite, Dick (External) Sent: 12 May 2017 10:22 To: Frederic Crozat; sle-beta at lists.suse.com' Subject: RE: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration Many Thanks for the update Frederic. I will try your suggestion, being able to avoid the download of the *.iso update would be very welcome. __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Frederic Crozat [fcrozat at suse.com] Sent: 12 May 2017 09:50 To: sle-beta at lists.suse.com' Subject: Re: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration Le jeudi 11 mai 2017 ? 14:51 +0000, Waite, Dick (External) a ?crit : > So it seems to run the command Okay but does not ?migrate from Beta1 > to beta2? Should I have given it more commands or options to commands > ???? zypper migration is only to be used to migrate from a service pack to another. Update between beta is not in scope of zypper migration. Migration between beta/RC/GMC milestones is not supported but if you want to try, you should run "zypper dup". -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From fcrozat at suse.com Mon May 15 01:56:48 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 15 May 2017 09:56:48 +0200 Subject: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E84E2AD@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> ,<1494575428.5094.107.camel@suse.com> ,<46AC8C81C10B8C48820201DF2AE1D76D010289AD8E@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E84E2AD@daeexmbx1.eur.ad.sag> Message-ID: <1494835008.23457.14.camel@suse.com> Le samedi 13 mai 2017 ? 14:46 +0000, Waite, Dick (External) a ?crit?: > Grand Saturday Frederic, > > Just the job... I now have eight VMware virtual machine saying they > are running SP-3 Beta3 ;o) not sure if that is the "real" Beta3 (May > 18th) but the zypper DUP runs look grand. Channels available through SCC for the SLE12 SP3 Beta were updated to a snapshot of Beta between Beta2 and what will become Beta3. This is NOT Beta3, it is an interim release, so please do not try to use channels until SLE12 SP3 Beta3 is officially announced. Sorry for this. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Mon May 15 02:21:01 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 15 May 2017 08:21:01 +0000 Subject: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration In-Reply-To: <1494835008.23457.14.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D010289967D@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A78A@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010289A833@daeexmbx1.eur.ad.sag> ,<1494575428.5094.107.camel@suse.com> ,<46AC8C81C10B8C48820201DF2AE1D76D010289AD8E@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E84E2AD@daeexmbx1.eur.ad.sag>, <1494835008.23457.14.camel@suse.com> Message-ID: <20170515082100.5357653.1441.27443@softwareag.com> Understood. I was more interested in the process. I'll run again after the iso is available. I need to check a bug is fixed using the iso. __R Sent from my BlackBerry 10 smartphone. Original Message From: Frederic Crozat Sent: Monday, 15 May 2017 09:57 To: sle-beta at lists.suse.com' Subject: Re: [sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration Le samedi 13 mai 2017 ? 14:46 +0000, Waite, Dick (External) a ?crit : > Grand Saturday Frederic, > > Just the job... I now have eight VMware virtual machine saying they > are running SP-3 Beta3 ;o) not sure if that is the "real" Beta3 (May > 18th) but the zypper DUP runs look grand. Channels available through SCC for the SLE12 SP3 Beta were updated to a snapshot of Beta between Beta2 and what will become Beta3. This is NOT Beta3, it is an interim release, so please do not try to use channels until SLE12 SP3 Beta3 is officially announced. Sorry for this. -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Thomas.Eggers at araneaCONSULT.de Mon May 15 03:55:20 2017 From: Thomas.Eggers at araneaCONSULT.de (Thomas Eggers) Date: Mon, 15 May 2017 11:55:20 +0200 Subject: [sle-beta] sssd configuration via autoast References: <590B5A610200009000001189@smtp.araneaconsult.de> <59189E53020000610000FB64@smtp.araneaconsult.de> <59197B08020000610000FB6E@smtp.araneaconsult.de> Message-ID: <59197B08020000610000FB6E@smtp.araneaconsult.de> Hi, since SLES 12 SP2 I'm not be able to configure the sssd service over autoyast. In SLES 12 SP1 it was a separate point in yast and with SLES 12 SP2 it moves to user and authentication. I think that broke autoyast. Only with I get is: false true yast2-auth-client sssd sssd-tools sssd-ldap 100 /home -1 true /bin/bash /etc/skel 022 All the options about ldap server and other settings are gone, Thomas -- araneaCONSULT GmbH, Rudolf-Breitscheid-Stra?e 185-189, 14482 Potsdam E-Mail: info at araneaCONSULT.de Internet: www.araneaCONSULT.de Gesch?ftsf?hrer: Martina Huster, Gerald Bock, Dirk Feddersen, Thomas Eggers Telefon: +49 331 55035-0, Telefax: +49 331 55035-29 Deutsche Bank, BLZ 120 700 24, Kto. 4978284 Amtsgericht Potsdam, HRB 21666 P, USt-IdNr. DE 2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Tue May 16 03:08:52 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 16 May 2017 11:08:52 +0200 Subject: [sle-beta] =?utf-8?q?=5BVideo=5D_New_features_in_Hawk_2_=E2=80=93?= =?utf-8?q?_SLEHA_12_SP3_Beta?= Message-ID: <55350599-E318-416D-B738-181D3BF5DDF2@suse.com> Hi, Just a quick announcement about the Youtube video we have made for "New features in Hawk 2 ? SLEHA 12 SP3 Beta?. You can find the video link at: https://www.suse.com/communities/blog/video-new-features-hawk-2-sleha-12-sp3-beta/ Any comments or questions are welcome. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From beta-programs at lists.suse.com Wed May 17 09:42:35 2017 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Wed, 17 May 2017 17:42:35 +0200 Subject: [sle-beta] SLE 12 SP3 Beta 3 is on track Message-ID: <591c6f6b58d2a_513041132453976@boucane.mail> We are preparing and cooking all the ingredients for Beta 3 and we should be able to take it out of the oven and serve it on time. More seriously, Beta 3 is on his way for being released on time according to our initial schedule[1], i.e 18th May or maybe 19th if there is any surprise. Video: New features in Hawk2 Here is an appetizer, a video presenting the new features of our SUSE Linux Enterprise High Availability 12 SP3 Web UI: Hawk2. You can find it at https://youtu.be/MyenIdX8k4U Stay tuned for the release of SLE 12 SP3 Beta 3, Your SUSE Linux Enterprise Team [1] https://www.suse.com/betaprogram/sle-beta/#releases -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Thu May 18 08:16:49 2017 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Thu, 18 May 2017 16:16:49 +0200 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 12 SP3 Beta 3 is available! Message-ID: <591dacd1a0f9e_696810bd320121@boucane.mail> == [ANNOUNCE] SUSE Linux Enterprise 12 SP3 Beta 3 is available! We are happy to announce SUSE Linux Enterprise 12 SP3 Beta 3: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Just Enough Operating System (JeOS), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLEHA), SUSE Linux Enterprise Workstation Extension (SLEWE), and SUSE Linux Enterprise Software Development Kit (SLESDK). Download[2] We are thankful for your support in trying out our beta products and we welcome your feedback. == More informations SLE Beta Page[1] Release Notes[3] Known Issues[4] Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, 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. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/ [2]https://www.suse.com/betaprogram/sle-beta/#download [3]https://www.suse.com/betaprogram/sle-beta/#releasenotes [4]https://www.suse.com/betaprogram/sle-beta/#knownissues -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Thu May 18 08:24:33 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Thu, 18 May 2017 14:24:33 +0000 Subject: [sle-beta] SLES12-SP-3 Beta3 - Bug 1033202 -- Fixed Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E85B7B9@daeexmbx1.eur.ad.sag> Grand Afternoon, I can confirm using the Beta-3 ISO we get UK == UK Many Thanks __R ________________________________ From: Waite, Dick (External) Sent: 05 May 2017 07:24 To: sle-beta at lists.suse.com Subject: SLES12-SP-3 Beta3 - Bug 1033202 Grand Morning, Ran a Beta2 update on a VMware SLES12-SP-3 Beta1 machine. Looks grand bar Bug 1033202 is still with us. Have a very good day. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu May 18 09:27:31 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 18 May 2017 17:27:31 +0200 Subject: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E857407@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010E853474@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E8534A7@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E856362@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E857407@daeexmbx1.eur.ad.sag> Message-ID: <67AE3A81-2CA6-4277-868E-161CF085FA8C@suse.com> Hi, This should now work with Beta 3. But please remember that updating/upgrading/migrating from Beta version to Beta version is not supported! This should work but we highly recommend to do a fresh install of your server. _However_ upgrading/migrating from SLE 12 SP2 to SLE 12 SP3 BetaX is ?supported? in a sense that in this specific scenario we can consider the SLE 12 SP3 BetaX as SLE 12 SP3. Thus any findings or bugs could be considered as a bug that could occur with the final version of SLE 12 SP3. Hope you understand, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 15 May 2017, at 16:39, Waite, Dick (External) wrote: > > Ummmm seems it's not just +ve wave thoughts... > > On DALI157 I checked the status, Beta-1 > > I then tried a DUP and was told no work needed... > > I then tried a migration --query > > I was told no migration available or simular... > > I then tried a DUP and glory be.... Off we went to update to pre-Beta-3 > > I did try the with DALI158 and got the same... > > So it seem a MIGRATION rattles the bits and bit and then a DUP finds it does have some work... > > What a grand afternoon, all I have to do tomorrow is a few IPL's > > Bye > > __R > > From: Waite, Dick (External) > Sent: 15 May 2017 15:16 > To: sle-beta at lists.suse.com > Subject: RE: SLE-Beta SLES12-SP3 Beta Migration - S390x > > Grand Sunny Monday, > > What a difference some sunshine makes. Yesterday I tried to DUP update a SP-3 Beta-1 s390x machine and it said "nothing to do" > > Today we have sun, and I thought, let's try again with all this +ve wave thoughts... > > There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs. > dali111:~ # cat /etc/issue > > Welcome to SUSE Linux Enterprise Server 12 SP3 Beta3 (s390x) - Kernel \r (\l). > > To quote from a grand film: > > > Always with the negative waves Moriarty, ALWAYS with the negative waves! > Oh, man. Don't hit me with those negative waves so early in the morning. > So with a little sunshine and +ve wave thoughts our DAL111 has gone from SP-3 Beta-1 to a pre-Beta-3. > > Who says computing is not a little magic.... > > Bye Y'all > > __R > > From: Waite, Dick (External) > Sent: 14 May 2017 07:50 > To: sle-beta at lists.suse.com > Subject: FW: SLE-Beta SLES12-SP3 Beta Migration - S390x > > Grand Sunday, > > We had a maint slot on the IBM M/F yesterday. My dali's were newly ipl'ed so I thought, lets give one a try, I can fix it on Tuesday if has a real bad hair day. > > So the log follows: > > I think it went quite well. DALI111 is running SLES12 SP-3 at Beta-1. I ran the DUP and it's reply was: > > Nothing to do. > > An honest machine, it's running Okay but why doesn't it update to at least Beta-2 ? > > Have a very good day Y'all > > __R > > > > > > > > login as: root > +--------------------------------------------------------------------+ > ? ? MobaXterm 9.4 ? ? > ? (SSH client, X-server and networking tools) ? > ? ? > ? ? SSH session to root at dali111.eur.ad.sag ? > ? ? SSH compression : ? ? > ? ? SSH-browser : ? ? > ? ? X11-forwarding : ? (remote display is forwarded through SSH) ? > ? ? DISPLAY : ? (automatically set on remote server) ? > ? ? > ? ? For more info, ctrl+click on help or visit our website ? > +--------------------------------------------------------------------+ > > Last login: Wed May 10 16:16:45 2017 from 10.20.200.118 > /SAG/specific.login: No such file or directory. > root has logged on pts/0 from 10.20.252.37. > dali111::root 51 => bash > dali111:~ # SUSEConnect --status-text > Installed Products: > ------------------------------------------ > > Toolchain Module > (sle-module-toolchain/12/s390x) > > Registered > > ------------------------------------------ > > SUSE Linux Enterprise Software Development Kit 12 > (sle-sdk/12.3/s390x) > > Registered > > ------------------------------------------ > > Web and Scripting Module > (sle-module-web-scripting/12/s390x) > > Registered > > ------------------------------------------ > > SUSE Linux Enterprise Server 12 SP3 > (SLES/12.3/s390x) > > Registered > > Subscription: > > Regcode: 04bff........... > Starts at: 2017-04-29 06:01:23 UTC > Expires at: 2017-10-26 06:01:23 UTC > Status: ACTIVE > Type: test > > > ------------------------------------------ > > Legacy Module > (sle-module-legacy/12/s390x) > > Registered > > ------------------------------------------ > > dali111:~ # cat /etc/issue > > Welcome to SUSE Linux Enterprise Server 12 SP3 Beta1 (s390x) - Kernel \r (\l). > > > dali111:~ # zypper lp > Refreshing service 'Legacy_Module_12_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x'. > Refreshing service 'Toolchain_Module_12_s390x'. > Refreshing service 'Web_and_Scripting_Module_12_s390x'. > Retrieving repository 'SLES12-SP3-Updates' metadata .....................................................................................................................................................[done] > Building repository 'SLES12-SP3-Updates' cache ..........................................................................................................................................................[done] > Retrieving repository 'SLE-SDK12-SP3-Updates' metadata ..................................................................................................................................................[done] > Building repository 'SLE-SDK12-SP3-Updates' cache .......................................................................................................................................................[done] > Loading repository data... > Reading installed packages... > > Repository | Name | Category | Severity | Interactive | Status | Summary > -------------------+---------------------------------+-------------+----------+-------------+--------+------------------------------ > SLES12-SP3-Updates | SUSE-SLE-SERVER-12-SP3-2017-734 | recommended | low | --- | needed | Recommended update for hwinfo > > Found 1 applicable patch: > 1 patch needed (0 security patches) > > dali111:~ # zypper patch > Refreshing service 'Legacy_Module_12_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x'. > Refreshing service 'Toolchain_Module_12_s390x'. > Refreshing service 'Web_and_Scripting_Module_12_s390x'. > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > The following NEW patch is going to be installed: > SUSE-SLE-SERVER-12-SP3-2017-734 > > The following package is going to be upgraded: > hwinfo > > 1 package to upgrade. > Overall download size: 615.9 KiB. Already cached: 0 B. After the operation, additional 27.2 KiB will be used. > Continue? [y/n/...? shows all options] (y): > Retrieving package hwinfo-21.44-3.1.s390x (1/1), 615.9 KiB ( 2.7 MiB unpacked) > Retrieving: hwinfo-21.44-3.1.s390x.rpm ....................................................................................................................................................[done (288.0 KiB/s)] > Checking for file conflicts: ............................................................................................................................................................................[done] > (1/1) Installing: hwinfo-21.44-3.1.s390x ................................................................................................................................................................[done] > dali111:~ # zypper lp > Refreshing service 'Legacy_Module_12_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x'. > Refreshing service 'Toolchain_Module_12_s390x'. > Refreshing service 'Web_and_Scripting_Module_12_s390x'. > Loading repository data... > Reading installed packages... > No updates found. > > dali111:~ # zypper ls > # | Alias | Name | Enabled | GPG Check | Refresh | Type > --+-------------------------------------------------------------+-------------------------------------------------------------+---------+-----------+---------+------ > 1 | Legacy_Module_12_s390x | Legacy_Module_12_s390x | Yes | ---- | Yes | ris > 2 | SUSE_Linux_Enterprise_Server_12_SP3_s390x | SUSE_Linux_Enterprise_Server_12_SP3_s390x | Yes | ---- | Yes | ris > 3 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x | Yes | ---- | Yes | ris > 4 | Toolchain_Module_12_s390x | Toolchain_Module_12_s390x | Yes | ---- | Yes | ris > 5 | Web_and_Scripting_Module_12_s390x | Web_and_Scripting_Module_12_s390x | Yes | ---- | Yes | ris > 6 | SLES12-SP1-12.1-0 | SLES12-SP1-12.1-0 | No | ---- | ---- | yast2 > dali111:~ # zypper lr > Repository priorities are without effect. All enabled repositories share the same priority. > > # | Alias | Name | Enabled | GPG Check | Refresh > ---+---------------------------------------------------------------------------------------------+----------------------------------------------+---------+-----------+-------- > 1 | Legacy_Module_12_s390x:SLE-Module-Legacy12-Debuginfo-Pool | SLE-Module-Legacy12-Debuginfo-Pool | No | ---- | ---- > 2 | Legacy_Module_12_s390x:SLE-Module-Legacy12-Debuginfo-Updates | SLE-Module-Legacy12-Debuginfo-Updates | No | ---- | ---- > 3 | Legacy_Module_12_s390x:SLE-Module-Legacy12-Pool | SLE-Module-Legacy12-Pool | Yes | (r ) Yes | No > 4 | Legacy_Module_12_s390x:SLE-Module-Legacy12-Source-Pool | SLE-Module-Legacy12-Source-Pool | No | ---- | ---- > 5 | Legacy_Module_12_s390x:SLE-Module-Legacy12-Updates | SLE-Module-Legacy12-Updates | Yes | (r ) Yes | Yes > 6 | SLES12-SP1-12.1-0 | SLES12-SP1-12.1-0 | No | ---- | ---- > 7 | SUSE_Linux_Enterprise_Server_12_SP3_s390x:SLES12-SP3-Debuginfo-Pool | SLES12-SP3-Debuginfo-Pool | No | ---- | ---- > 8 | SUSE_Linux_Enterprise_Server_12_SP3_s390x:SLES12-SP3-Debuginfo-Updates | SLES12-SP3-Debuginfo-Updates | No | ---- | ---- > 9 | SUSE_Linux_Enterprise_Server_12_SP3_s390x:SLES12-SP3-Pool | SLES12-SP3-Pool | Yes | (r ) Yes | No > 10 | SUSE_Linux_Enterprise_Server_12_SP3_s390x:SLES12-SP3-Source-Pool | SLES12-SP3-Source-Pool | No | ---- | ---- > 11 | SUSE_Linux_Enterprise_Server_12_SP3_s390x:SLES12-SP3-Updates | SLES12-SP3-Updates | Yes | (r ) Yes | Yes > 12 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x:SLE-SDK12-SP3-Debuginfo-Pool | SLE-SDK12-SP3-Debuginfo-Pool | No | ---- | ---- > 13 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x:SLE-SDK12-SP3-Debuginfo-Updates | SLE-SDK12-SP3-Debuginfo-Updates | No | ---- | ---- > 14 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x:SLE-SDK12-SP3-Pool | SLE-SDK12-SP3-Pool | Yes | (r ) Yes | No > 15 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x:SLE-SDK12-SP3-Source-Pool | SLE-SDK12-SP3-Source-Pool | No | ---- | ---- > 16 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x:SLE-SDK12-SP3-Updates | SLE-SDK12-SP3-Updates | Yes | (r ) Yes | Yes > 17 | Toolchain_Module_12_s390x:SLE-Module-Toolchain12-Debuginfo-Pool | SLE-Module-Toolchain12-Debuginfo-Pool | No | ---- | ---- > 18 | Toolchain_Module_12_s390x:SLE-Module-Toolchain12-Debuginfo-Updates | SLE-Module-Toolchain12-Debuginfo-Updates | No | ---- | ---- > 19 | Toolchain_Module_12_s390x:SLE-Module-Toolchain12-Pool | SLE-Module-Toolchain12-Pool | Yes | (r ) Yes | No > 20 | Toolchain_Module_12_s390x:SLE-Module-Toolchain12-Updates | SLE-Module-Toolchain12-Updates | Yes | (r ) Yes | Yes > 21 | Web_and_Scripting_Module_12_s390x:SLE-Module-Web-Scripting12-Debuginfo-Pool | SLE-Module-Web-Scripting12-Debuginfo-Pool | No | ---- | ---- > 22 | Web_and_Scripting_Module_12_s390x:SLE-Module-Web-Scripting12-Debuginfo-Updates | SLE-Module-Web-Scripting12-Debuginfo-Updates | No | ---- | ---- > 23 | Web_and_Scripting_Module_12_s390x:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | Yes | (r ) Yes | No > 24 | Web_and_Scripting_Module_12_s390x:SLE-Module-Web-Scripting12-Source-Pool | SLE-Module-Web-Scripting12-Source-Pool | No | ---- | ---- > 25 | Web_and_Scripting_Module_12_s390x:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | Yes | (r ) Yes | Yes > dali111:~ # zypper dup --help > dist-upgrade (dup) [options] > > Perform a distribution upgrade. > > Command options: > > --from Restrict upgrade to specified repository. > -r, --repo Load only the specified repository. > -l, --auto-agree-with-licenses > Automatically say 'yes' to third party license > confirmation prompt. > See man zypper for more details. > --debug-solver Create solver test case for debugging > --no-recommends Do not install recommended packages, only required. > --recommends Install also recommended packages in addition > to the required. > --replacefiles Install the packages even if they replace files from other, > already installed, packages. Default is to treat file conflicts > as an error. --download-as-needed disables the fileconflict check. > -D, --dry-run Test the upgrade, do not actually upgrade > --details Show the detailed installation summary. > --download Set the download-install mode. Available modes: > only, in-advance, in-heaps, as-needed > -d, --download-only Only download the packages, do not install. > -y, --no-confirm Don't require user interaction. Alias for the --non-interactive global option. > > Expert options: > > --allow-downgrade > --no-allow-downgrade Whether to allow downgrading installed resolvables. > --allow-name-change > --no-allow-name-change Whether to allow changing the names of installed resolvables. > --allow-arch-change > --no-allow-arch-change Whether to allow changing the architecture of installed resolvables. > --allow-vendor-change > --no-allow-vendor-change > Whether to allow changing the vendor of installed resolvables. > > dali111:~ # zypper dup --details --auto-agree-with-licenses > Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. > Refreshing service 'Legacy_Module_12_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_s390x'. > Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_s390x'. > Refreshing service 'Toolchain_Module_12_s390x'. > Refreshing service 'Web_and_Scripting_Module_12_s390x'. > Loading repository data... > Reading installed packages... > Computing distribution upgrade... > > Nothing to do. > dali111:~ # cat /etc/issue > > Welcome to SUSE Linux Enterprise Server 12 SP3 Beta1 (s390x) - Kernel \r (\l). > > > dali111:~ # > > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Fri May 19 00:46:27 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 19 May 2017 06:46:27 +0000 Subject: [sle-beta] waiting for shared lock Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> Grand Morning, I'd like to set a flag so that I do not waste a lot of time, on Virtual machine that load-run-drop many times a day. I keep my patch level of the QE/QA machines at the same level. I can understand on physical machines and machines that are ipl'ed once a week or more checking each ipl for updates could make sense, but on machines that are loaded many many times a day it's a PITA. So could we have a flag that says don't run this check please. Many Thanks __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Fri May 19 03:32:34 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 19 May 2017 11:32:34 +0200 Subject: [sle-beta] waiting for shared lock In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> Message-ID: <92818847-6A72-48FE-822D-B0B74D662E81@suse.com> Hi, Sorry I don?t really understand what you meant. Could you elaborate on the ?flag, check and ipl? and how this is related to SLES? Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 19 May 2017, at 08:46, Waite, Dick (External) wrote: > > Grand Morning, > > I'd like to set a flag so that I do not waste a lot of time, on Virtual machine that load-run-drop many times a day. I keep my patch level of the QE/QA machines at the same level. I can understand on physical machines and machines that are ipl'ed once a week or more checking each ipl for updates could make sense, but on machines that are loaded many many times a day it's a PITA. > > So could we have a flag that says don't run this check please. > > Many Thanks > > __R > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Fri May 19 04:18:31 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 19 May 2017 12:18:31 +0200 Subject: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E85B8C0@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010E853474@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E8534A7@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E856362@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E857407@daeexmbx1.eur.ad.sag> <67AE3A81-2CA6-4277-868E-161CF085FA8C@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85B8C0@daeexmbx1.eur.ad.sag> Message-ID: <49577E32-7F10-4A1E-B4FA-A998945ED719@suse.com> Hi, > On 18 May 2017, at 19:07, Waite, Dick (External) wrote: [?] > As a DUP update from beta-n to beta-n+1 is not an official update, SUSE only support a new install from beta-n to Beta-n+1, which from my point of view seems odd. If I have the configuration I want for this virtual machine it seem logical to me that I should be able to "update"... Maybe a few words on why a beta-n to beta-n+1 is an issue, maybe others would like to know too ? Why don?t we support updating/upgrading from SLE beta-n to beta-n+x ? Because we need the flexibility of doing important/disruptive changes to packages, like upgrading/downgrading to different version without taking care of supporting it. So for instance, we can move forward with SLE Beta-n+4 without even think about upgrading SLE Beta-n to SLE Beta-n+4 and take care of all the changes between these versions. At the end of the day we only care about migrating from the previous SLE to SLE Beta-n+4. Changes between SLE Beta might not be like regular updates we make in official SLE SP released. Since our customers might not face this kind of changes with official SLE SP in production it seems useless to take extra care on supporting this for our Beta Phase. And this allow us to focus on more important aspects for the final version of the SLE SP we are preparing during the beta program. Don?t forget that support also means to dedicated QA resources (humans and machines) for various scenarios. I didn't go into much details but I hope you understand our points. > Anyway as you say, I can always run a supported zypper migration from SP-2 GA to each Beta and RC and GMC > > Many thanks to the team, SP-3 has gone very well to-date, lets keep the fingers crossed. Great to hear, thanks! Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: From malcolmlewis at cableone.net Fri May 19 07:52:08 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Fri, 19 May 2017 08:52:08 -0500 Subject: [sle-beta] waiting for shared lock In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E85C155@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> <92818847-6A72-48FE-822D-B0B74D662E81@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85C155@daeexmbx1.eur.ad.sag> Message-ID: <20170519085208.47c22089@grover.homelinux.org> On Fri, 19 May 2017 13:05:25 +0000 "Waite, Dick (External)" wrote: > Grand Afternoon, > > When a SLES machine is started (ipl'ed) without asking SLES starts a > process in that machine to check if there is any outstanding service, > patches. During this time it's not possible to run some commands, you > get the SLES message in the subject. I have SLES machines that "start > (ipl) runs some commands, stop". They can do that a few times an > hour / day / week. I'd like to set a flag in SLES, that the "look for > service / patches" task looks at to see if it's allowed to run. By > default of course it can, but there are times when it's causing > issues. > > Have a grand weekend > > __R > > ________________________________ > From: Vincent Moutoussamy [vmoutoussamy at suse.com] > Sent: 19 May 2017 11:32 > To: Waite, Dick (External) > Cc: sle-beta at lists.suse.com > Subject: Re: waiting for shared lock > > Hi, > > Sorry I don?t really understand what you meant. > Could you elaborate on the ?flag, check and ipl? and how this is > related to SLES? > > Have a nice day, > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > > On 19 May 2017, at 08:46, Waite, Dick (External) > > wrote: > > Grand Morning, > > I'd like to set a flag so that I do not waste a lot of time, on > Virtual machine that load-run-drop many times a day. I keep my patch > level of the QE/QA machines at the same level. I can understand on > physical machines and machines that are ipl'ed once a week or more > checking each ipl for updates could make sense, but on machines that > are loaded many many times a day it's a PITA. > > So could we have a flag that says don't run this check please. > Hi You mean the packagekit systemd service (packagekit-offline-update and packagekit)? -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.62-18.6-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 16 days 10:29, 1 user, load average: 0.33, 0.54, 0.54 From Dick.Waite at softwareag.com Fri May 19 08:28:36 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 19 May 2017 14:28:36 +0000 Subject: [sle-beta] waiting for shared lock In-Reply-To: <20170519085208.47c22089@grover.homelinux.org> References: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> <92818847-6A72-48FE-822D-B0B74D662E81@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85C155@daeexmbx1.eur.ad.sag>, <20170519085208.47c22089@grover.homelinux.org> Message-ID: <20170519142836.5349456.75833.27565@softwareag.com> That does sound about right. Can one stop this service starting? __R Sent from my BlackBerry 10 smartphone. Original Message From: Malcolm Sent: Friday, 19 May 2017 15:52 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] waiting for shared lock On Fri, 19 May 2017 13:05:25 +0000 "Waite, Dick (External)" wrote: > Grand Afternoon, > > When a SLES machine is started (ipl'ed) without asking SLES starts a > process in that machine to check if there is any outstanding service, > patches. During this time it's not possible to run some commands, you > get the SLES message in the subject. I have SLES machines that "start > (ipl) runs some commands, stop". They can do that a few times an > hour / day / week. I'd like to set a flag in SLES, that the "look for > service / patches" task looks at to see if it's allowed to run. By > default of course it can, but there are times when it's causing > issues. > > Have a grand weekend > > __R > > ________________________________ > From: Vincent Moutoussamy [vmoutoussamy at suse.com] > Sent: 19 May 2017 11:32 > To: Waite, Dick (External) > Cc: sle-beta at lists.suse.com > Subject: Re: waiting for shared lock > > Hi, > > Sorry I don?t really understand what you meant. > Could you elaborate on the ?flag, check and ipl? and how this is > related to SLES? > > Have a nice day, > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > > On 19 May 2017, at 08:46, Waite, Dick (External) > > wrote: > > Grand Morning, > > I'd like to set a flag so that I do not waste a lot of time, on > Virtual machine that load-run-drop many times a day. I keep my patch > level of the QE/QA machines at the same level. I can understand on > physical machines and machines that are ipl'ed once a week or more > checking each ipl for updates could make sense, but on machines that > are loaded many many times a day it's a PITA. > > So could we have a flag that says don't run this check please. > Hi You mean the packagekit systemd service (packagekit-offline-update and packagekit)? -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.62-18.6-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 16 days 10:29, 1 user, load average: 0.33, 0.54, 0.54 _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From fcrozat at suse.com Fri May 19 08:34:10 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 19 May 2017 16:34:10 +0200 Subject: [sle-beta] waiting for shared lock In-Reply-To: <20170519142836.5349456.75833.27565@softwareag.com> References: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> <92818847-6A72-48FE-822D-B0B74D662E81@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85C155@daeexmbx1.eur.ad.sag> , <20170519085208.47c22089@grover.homelinux.org> <20170519142836.5349456.75833.27565@softwareag.com> Message-ID: <1495204450.7798.51.camel@suse.com> Le vendredi 19 mai 2017 ? 14:28 +0000, Waite, Dick (External) a ?crit?: > That does sound about right. Can one stop this service starting? systemctl mask?packagekit.service should completely disable the service (but please test to confirm). -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Fri May 19 08:40:15 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 19 May 2017 14:40:15 +0000 Subject: [sle-beta] waiting for shared lock In-Reply-To: <1495204450.7798.51.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> <92818847-6A72-48FE-822D-B0B74D662E81@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85C155@daeexmbx1.eur.ad.sag> , <20170519085208.47c22089@grover.homelinux.org> <20170519142836.5349456.75833.27565@softwareag.com>, <1495204450.7798.51.camel@suse.com> Message-ID: <20170519144015.5349456.90811.27569@softwareag.com> Many Thanks Fred?eric. I'll give it a run round the block in the morning. Beta-3 passing my IVP's. Looking good. These machines are on an internal LAN and I like them all at the same patch level. __R Sent from my BlackBerry 10 smartphone. Original Message From: Frederic Crozat Sent: Friday, 19 May 2017 16:34 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] waiting for shared lock Le vendredi 19 mai 2017 ? 14:28 +0000, Waite, Dick (External) a ?crit : > That does sound about right. Can one stop this service starting? systemctl mask packagekit.service should completely disable the service (but please test to confirm). -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Dick.Waite at softwareag.com Fri May 19 23:14:06 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sat, 20 May 2017 05:14:06 +0000 Subject: [sle-beta] waiting for shared lock In-Reply-To: <1495204450.7798.51.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D010E85BCE6@daeexmbx1.eur.ad.sag> <92818847-6A72-48FE-822D-B0B74D662E81@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85C155@daeexmbx1.eur.ad.sag> , <20170519085208.47c22089@grover.homelinux.org> <20170519142836.5349456.75833.27565@softwareag.com>, <1495204450.7798.51.camel@suse.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E85C8A7@daeexmbx1.eur.ad.sag> Grand Sunny Morning frederic, That's looking good, one can also issue: systemctl status packagekit.service and this shows it has stopped. Many Thanks and a grand weekend. __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Frederic Crozat [fcrozat at suse.com] Sent: 19 May 2017 16:34 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] waiting for shared lock Le vendredi 19 mai 2017 ? 14:28 +0000, Waite, Dick (External) a ?crit : > That does sound about right. Can one stop this service starting? systemctl mask packagekit.service should completely disable the service (but please test to confirm). -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Dick.Waite at softwareag.com Mon May 22 02:14:17 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 22 May 2017 08:14:17 +0000 Subject: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E85C0E3@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010E853474@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E8534A7@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E856362@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D010E857407@daeexmbx1.eur.ad.sag> <67AE3A81-2CA6-4277-868E-161CF085FA8C@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85B8C0@daeexmbx1.eur.ad.sag>, <49577E32-7F10-4A1E-B4FA-A998945ED719@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D010E85C0E3@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E866201@daeexmbx2.eur.ad.sag> Grand New Monday, I updated four s390x machines this morning to SLES12 SP-3 Beta-3. No issues seen on the update or basic IVP?s 90% of my machines are virtual, so I have a ?checkpoint? safety net at the last GA point. I have found that: zipper migration ?query run and seems to ?Tidy-up? and re-build the SUSE repository environment, and then lets you know there is no action to take. I then run: zypper dup ?details ?l and this does the update from Beta-n to Beta-n+1 and so far this has been good builds? I do have a Check Point at SP-2 GA so maybe that is not a good path for physical machines. So now time for a bit more than basic IVP?s and of course some ?KDE? updates? Regards, __R From: Waite, Dick (External) Sent: Freitag, 19. Mai 2017 14:55 To: Vincent Moutoussamy Cc: sle-beta at lists.suse.com Subject: RE: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x Many Thanks Vincent. Understand your reasons. I'm happy to go from my checkpoint at SP2 GA with Migration to the new target, Beta-n or RC-n For my environment that works well and as you say we are not required to "check" a Beta-n to Beta-n+1 __R ________________________________ From: Vincent Moutoussamy [vmoutoussamy at suse.com] Sent: 19 May 2017 12:18 To: Waite, Dick (External) Cc: sle-beta at lists.suse.com Subject: Re: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x Hi, On 18 May 2017, at 19:07, Waite, Dick (External) > wrote: [?] As a DUP update from beta-n to beta-n+1 is not an official update, SUSE only support a new install from beta-n to Beta-n+1, which from my point of view seems odd. If I have the configuration I want for this virtual machine it seem logical to me that I should be able to "update"... Maybe a few words on why a beta-n to beta-n+1 is an issue, maybe others would like to know too ? Why don?t we support updating/upgrading from SLE beta-n to beta-n+x ? Because we need the flexibility of doing important/disruptive changes to packages, like upgrading/downgrading to different version without taking care of supporting it. So for instance, we can move forward with SLE Beta-n+4 without even think about upgrading SLE Beta-n to SLE Beta-n+4 and take care of all the changes between these versions. At the end of the day we only care about migrating from the previous SLE to SLE Beta-n+4. Changes between SLE Beta might not be like regular updates we make in official SLE SP released. Since our customers might not face this kind of changes with official SLE SP in production it seems useless to take extra care on supporting this for our Beta Phase. And this allow us to focus on more important aspects for the final version of the SLE SP we are preparing during the beta program. Don?t forget that support also means to dedicated QA resources (humans and machines) for various scenarios. I didn't go into much details but I hope you understand our points. Anyway as you say, I can always run a supported zypper migration from SP-2 GA to each Beta and RC and GMC Many thanks to the team, SP-3 has gone very well to-date, lets keep the fingers crossed. Great to hear, thanks! Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alexej.Moisejew at sigos.com Tue May 30 07:47:47 2017 From: Alexej.Moisejew at sigos.com (Alexej Moisejew) Date: Tue, 30 May 2017 13:47:47 +0000 Subject: [sle-beta] Update of filesystem package. Message-ID: Hi, got following message during the DVD upgrade to SP3 (Beta 3) from SLED 12 SP2: ( 21/374) Installing: filesystem-13.1-14.9.x86_64 ........................................................................................[error] Installation of filesystem-13.1-14.9.x86_64 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /mnt: cpio: chmod failed - Read-only file system error: filesystem-13.1-14.9.x86_64: install failed error: filesystem-13.1-11.13.x86_64: erase skipped Abort, retry, ignore? [a/r/i] (a): Is this a known issue? Regards, Alexej -- SIGOS Klingenhofstrasse 50d 90411 Nuernberg GERMANY Tel.: +49 911 95168-0 www.sigos.com HRB 9323 Nuernberg Gerichtsstand: Nuernberg Geschaeftsfuehrer: Adil Kaya, John van Siclen, Kevin Burns Follow us on: linked.in | xing.com | twitter.com | facebook.com