From ast at suse.com Tue Dec 1 08:59:26 2015 From: ast at suse.com (Anja Stock) Date: Tue, 1 Dec 2015 16:59:26 +0100 (CET) Subject: [sles-beta] SLES 12 SP1 Goldmaster is ready Message-ID: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta Customers, We are happy to announce that after the final validation and acceptance phase we have a Goldmaster for SUSE Linux Enterprise Server 12 Service Pack 1 SUSE Linux Enterprise Desktop 12 Service Pack 1 SUSE Linux Enterprise High Availability Extension 12 Service Pack 1 SUSE Linux Enterprise Software Development Kit 12 Service Pack 1 SUSE Linux Enterprise Workstation Extension 12 Service Pack 1 There were no changes since GMC3. The correct images are the one with "GMC3" in the name. The Goldmaster will only differentiate in the name of the images (replace GMC3 with GM). Thank you for the contributions in terms of code, testing, enhancement requests and bug reports that you have provided to make this a great release! Your SUSE Linux Enterprise Team -- Thank you, Anja Anja Stock Release-/Project Mgr. SUSE Linux Enterprise/JeOS ast at suse.com Tel: +49 9 11/7 40 53 381 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From allen at ua.edu Tue Dec 1 09:12:13 2015 From: allen at ua.edu (Beddingfield, Allen) Date: Tue, 1 Dec 2015 16:12:13 +0000 Subject: [sles-beta] My feedback/summary Message-ID: I just thought I would step up to the "microphone" and say a few words. So, I know that I've been pretty quiet on this beta (compared with the SLES 12 and 11 SP4 beta), but that is because I've not uncovered issues this time. :) My tests have been with various Dell hardware, Compellent SAN, XenServer, KVM, and VMware, as well as with our commonly used applications. The one issue we had with 12.0 going into the beta was addressed, and the tests I have done with the various 12.1 betas have "just worked". I think the only problem I had was early on with getting the systems registered, and that was a mix up with my SCC account. Since the list has been relatively quiet, I hope that others have had the same experience. Anyway, from all I can tell, this release is in good shape, and I see an e-mail regarding the gold master has arrived in my inbox while I'm typing away at this message... -- Allen Beddingfield Systems Engineer The University of Alabama From vmoutoussamy at suse.com Wed Dec 2 03:25:03 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 2 Dec 2015 11:25:03 +0100 Subject: [sles-beta] My feedback/summary In-Reply-To: References: Message-ID: Hi, > > On 01 Dec 2015, at 17:12, Beddingfield, Allen wrote: > > I just thought I would step up to the "microphone" and say a few words. > So, I know that I've been pretty quiet on this beta (compared with the SLES 12 and 11 SP4 beta), but that is because I've not uncovered issues this time. :) My tests have been with various Dell hardware, Compellent SAN, XenServer, KVM, and VMware, as well as with our commonly used applications. > The one issue we had with 12.0 going into the beta was addressed, and the tests I have done with the various 12.1 betas have "just worked". I think the only problem I had was early on with getting the systems registered, and that was a mix up with my SCC account. Since the list has been relatively quiet, I hope that others have had the same experience. > > Anyway, from all I can tell, this release is in good shape, and I see an e-mail regarding the gold master has arrived in my inbox while I'm typing away at this message? > Thank you for your feedback Allen, we really appreciate it. Could you elaborate a little bit about your registration issue? I just want to make sure that everything is ?GREEN? in your SCC administration page. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From vmoutoussamy at suse.com Wed Dec 2 05:31:57 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 2 Dec 2015 13:31:57 +0100 Subject: [sles-beta] Service Request: 10980794901 - Unable to Register a s390x System In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C61F46@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C61F46@hqmbx6.eur.ad.sag> Message-ID: <06439803-7F99-43B8-A9F6-FD7AFC2CBC33@suse.com> Hi, I saw that the support team is still investigating this issue. I will try to get additional information and keep you in touch. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 29 Nov 2015, at 08:22, Waite, Dick (External) wrote: > > Grand Sunday Morning, > > Part of the --debug output. I do have a SLES12-SP0 system registered Okay. I have looked at scc.suse.com and it looks Okay. > > I did try --cleanup and when that didn't work I tried: > > rm -f /etc/SUSEConnect > rm -f /etc/zypp/services.d/* > rm -f /etc/zypp/credentials.d/* > but I still get -3 > > ebug=true, language="POSIX"> > Executing: 'uname -i' Quiet: false > Output: 's390x' > Executing: 'read_values -s' Quiet: false > Output: 'Error: Unable to open configuration, return_code =-3' > command 'read_values -s' failed > SUSEConnect error: SUSE::Connect::SystemCallError: Error: Unable to open configuration, return_code =-3 > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/toolkit/system_calls.rb:27:in `execute' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/s390.rb:46:in `output' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/s390.rb:16:in `cpus' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/s390.rb:7:in `hwinfo' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/hwinfo/base.rb:13:in `info' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/system.rb:13:in `hwinfo' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/api.rb:40:in `announce_system' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/client.rb:48:in `announce_system' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/client.rb:142:in `announce_or_update' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/client.rb:26:in `register!' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/lib/suse/connect/cli.rb:42:in `execute!' > /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.27/bin/SUSEConnect:11:in `' > /usr/sbin/SUSEConnect:23:in `load' > /usr/sbin/SUSEConnect:23:in `
' > > > I have copied the SDK of GMC3 to the s390x and added it to the software repositories with Yast. > zypper dup ran Okay, see output below.... > > > > ########################################################################## > > dali158:~ # zypper dup > 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. > Loading repository data... > Reading installed packages... > Computing distribution upgrade... > > The following 14 packages are going to be upgraded: > autoyast2 autoyast2-installation release-notes-sles rollback-helper sles-release-DVD yast2-dhcp-server yast2-dns-server yast2-http-server yast2-installation > yast2-mail yast2-network yast2-nis-server yast2-schema yast2-services-manager > > 14 packages to upgrade. > Overall download size: 2.4 MiB. Already cached: 0 B. After the operation, additional 29.5 KiB will be used. > Continue? [y/n/? shows all options] (y): > Retrieving package release-notes-sles-12.1.20151119-1.1.noarch (1/14), 443.4 KiB ( 1.0 MiB unpacked) > Retrieving package rollback-helper-0.1-3.1.noarch (2/14), 7.9 KiB ( 1.5 KiB unpacked) > Retrieving package yast2-dns-server-3.1.17-1.43.noarch (3/14), 200.1 KiB ( 2.3 MiB unpacked) > Retrieving package yast2-mail-3.1.5-3.179.noarch (4/14), 141.3 KiB ( 1.2 MiB unpacked) > Retrieving package yast2-services-manager-3.1.40-1.1.noarch (5/14), 34.6 KiB ( 81.7 KiB unpacked) > Retrieving package sles-release-DVD-12.1-1.331.s390x (6/14), 3.4 KiB ( 66 B unpacked) > Retrieving package yast2-network-3.1.134-4.1.s390x (7/14), 196.2 KiB (808.1 KiB unpacked) > Retrieving package yast2-schema-3.1.5-1.79.s390x (8/14), 71.8 KiB (934.5 KiB unpacked) > Retrieving package yast2-dhcp-server-3.1.5-3.241.noarch (9/14), 207.6 KiB ( 2.8 MiB unpacked) > Retrieving package yast2-nis-server-3.1.3-3.211.noarch (10/14), 33.5 KiB (140.5 KiB unpacked) > Retrieving package yast2-http-server-3.1.6-3.186.noarch (11/14), 167.8 KiB ( 1.8 MiB unpacked) > Retrieving package autoyast2-installation-3.1.101.2-1.1.noarch (12/14), 151.2 KiB (681.3 KiB unpacked) > Retrieving package autoyast2-3.1.101.2-1.1.noarch (13/14), 650.2 KiB ( 6.4 MiB unpacked) > Retrieving package yast2-installation-3.1.162.1-1.1.noarch (14/14), 192.1 KiB (672.2 KiB unpacked) > Checking for file conflicts: ................................................................................................................................[done] > ( 1/14) Installing: release-notes-sles-12.1.20151119-1.1 ....................................................................................................[done] > ( 2/14) Installing: rollback-helper-0.1-3.1 .................................................................................................................[done] > ( 3/14) Installing: yast2-dns-server-3.1.17-1.43 ............................................................................................................[done] > ( 4/14) Installing: yast2-mail-3.1.5-3.179 ..................................................................................................................[done] > Additional rpm output: > Updating /etc/sysconfig/mail... > > > ( 5/14) Installing: yast2-services-manager-3.1.40-1.1 .......................................................................................................[done] > ( 6/14) Installing: sles-release-DVD-12.1-1.331 .............................................................................................................[done] > ( 7/14) Installing: yast2-network-3.1.134-4.1 ...............................................................................................................[done] > ( 8/14) Installing: yast2-schema-3.1.5-1.79 .................................................................................................................[done] > ( 9/14) Installing: yast2-dhcp-server-3.1.5-3.241 ...........................................................................................................[done] > (10/14) Installing: yast2-nis-server-3.1.3-3.211 ............................................................................................................[done] > (11/14) Installing: yast2-http-server-3.1.6-3.186 ...........................................................................................................[done] > (12/14) Installing: autoyast2-installation-3.1.101.2-1.1 ....................................................................................................[done] > (13/14) Installing: autoyast2-3.1.101.2-1.1 .................................................................................................................[done] > Additional rpm output: > Updating /etc/sysconfig/autoinstall... > > > (14/14) Installing: yast2-installation-3.1.162.1-1.1 ........................................................................................................[done] > Additional rpm output: > Updating /etc/sysconfig/security... > > > dali158:~ # > > __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; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: