From vmoutoussamy at suse.com Thu May 12 11:01:05 2016 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 12 May 2016 19:01:05 +0200 Subject: [sles-beta] Welcome to the Beta Program of SUSE Linux Enterprise 12 Service Pack 2 Message-ID: Greetings all, Welcome to the Beta Program of SUSE Linux Enterprise Server 12 Service Pack 2 We?re thrilled to have you join us! Your feedback will help us get the final touches in before the product is ready to be released! So, without further ado, here are the information about our Beta Program: * New changes for the SLE Beta Program - Public Beta Program starting end of May 2016: We have decided to open our SLE Beta Program to the public. BUT it will officially be announced and start at the same time of the release of our new www.suse.com web site (scheduled for end of May). We will have some dedicated suse.com SLE Beta Program web pages to support this project. Stay tuned. Until then, you (our Very Important Beta testers) remain exclusive beta testers, and have access to a dedicated web pages at: http://beta.suse.com/private/SLE12/SP2-BETA/ This web page regroups important information about the Beta Program and the Beta Products. - Bugzilla replaces our SUSE support portal: More information at the end of this email. If you have questions or concerns about these changes, please contact us at beta-programs at lists.suse.com * Schedule: Our plan is to release 4 betas, 3 Release Candidates and one Gold Master Candidate version, from May 12th, 2016 to September 9th, 2016. Please note that we reserve the right to change or adapt this schedule depending on various factors. But rest assured that we will communicate if there is any changes of plan. Scheduled releases: 2016-05-13 Beta 1 2016-06-02 Beta 2 2016-06-16 Beta 3 2016-07-07 Beta 4 2016-07-21 RC1 2016-08-11 RC2 2016-09-01 RC3 2016-09-22 GMC * Download: The SLE 12 SP2 beta releases will be available at https://download.suse.com, and the exact links will be sent with each release announcement and posted on http://beta.suse.com/private/SLE12/SP2-BETA/ * Beta Program communication: - Mailing lists: - Announcements of new beta versions, and share technical information, - Serve as discussion forums, - Share information about issues found by participants, - To post findings, also to minimize reporting of duplicates. sles-beta at lists.suse.com sled-beta at lists.suse.com sleha-beta at lists.suse.com - PSE/DSE SUSE customers do not need to contact their Premium Support Engineer, but it is recommended to keep them in touch of any bugs created. - Bugzilla: Unlike in the past SLE Beta Program, we will not use the SUSE support portal as the feedback and defect tool! Instead we will ask you to use our specific Bugzilla setup for the SLE Beta Product. Please visit our dedicated web pages regarding the Bugzilla Guideline: http://beta.suse.com/private/SLE12/SP2-BETA/bugzilla.html * Beta Program logistics: /!\ For any logistics, access issues, specific questions, please contact me Vincent Moutoussamy (Beta Project Manager) at the following address beta-programs at lists.suse.com Have fun and a happy beta testing ! Thanks. -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From Dick.Waite at softwareag.com Thu May 12 23:25:36 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 13 May 2016 05:25:36 +0000 Subject: [sles-beta] Welcome to the Beta Program of SUSE Linux Enterprise 12 Service Pack 2 In-Reply-To: References: Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DDFB9F@hqmbx6.eur.ad.sag> Grand New Friday, Will we have to register the machines we are using for the SP-2 Beta ? At the moment the machines I have moved into my SP-2 group all have a SP-1 GA registration plus the SDK, Script and workstation ext. As the Beta will be public I was thinking there wouldn't be a need to register ? I don't have a code anyway. __R ________________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Vincent Moutoussamy [vmoutoussamy at suse.com] Sent: 12 May 2016 19:01 To: sles-beta Subject: [sles-beta] Welcome to the Beta Program of SUSE Linux Enterprise 12 Service Pack 2 Greetings all, Welcome to the Beta Program of SUSE Linux Enterprise Server 12 Service Pack 2 We?re thrilled to have you join us! Your feedback will help us get the final touches in before the product is ready to be released! So, without further ado, here are the information about our Beta Program: * New changes for the SLE Beta Program - Public Beta Program starting end of May 2016: We have decided to open our SLE Beta Program to the public. BUT it will officially be announced and start at the same time of the release of our new www.suse.com web site (scheduled for end of May). We will have some dedicated suse.com SLE Beta Program web pages to support this project. Stay tuned. Until then, you (our Very Important Beta testers) remain exclusive beta testers, and have access to a dedicated web pages at: http://beta.suse.com/private/SLE12/SP2-BETA/ This web page regroups important information about the Beta Program and the Beta Products. - Bugzilla replaces our SUSE support portal: More information at the end of this email. If you have questions or concerns about these changes, please contact us at beta-programs at lists.suse.com * Schedule: Our plan is to release 4 betas, 3 Release Candidates and one Gold Master Candidate version, from May 12th, 2016 to September 9th, 2016. Please note that we reserve the right to change or adapt this schedule depending on various factors. But rest assured that we will communicate if there is any changes of plan. Scheduled releases: 2016-05-13 Beta 1 2016-06-02 Beta 2 2016-06-16 Beta 3 2016-07-07 Beta 4 2016-07-21 RC1 2016-08-11 RC2 2016-09-01 RC3 2016-09-22 GMC * Download: The SLE 12 SP2 beta releases will be available at https://download.suse.com, and the exact links will be sent with each release announcement and posted on http://beta.suse.com/private/SLE12/SP2-BETA/ * Beta Program communication: - Mailing lists: - Announcements of new beta versions, and share technical information, - Serve as discussion forums, - Share information about issues found by participants, - To post findings, also to minimize reporting of duplicates. sles-beta at lists.suse.com sled-beta at lists.suse.com sleha-beta at lists.suse.com - PSE/DSE SUSE customers do not need to contact their Premium Support Engineer, but it is recommended to keep them in touch of any bugs created. - Bugzilla: Unlike in the past SLE Beta Program, we will not use the SUSE support portal as the feedback and defect tool! Instead we will ask you to use our specific Bugzilla setup for the SLE Beta Product. Please visit our dedicated web pages regarding the Bugzilla Guideline: http://beta.suse.com/private/SLE12/SP2-BETA/bugzilla.html * Beta Program logistics: /!\ For any logistics, access issues, specific questions, please contact me Vincent Moutoussamy (Beta Project Manager) at the following address beta-programs at lists.suse.com Have fun and a happy beta testing ! Thanks. -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-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; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From vmoutoussamy at suse.com Fri May 13 07:02:37 2016 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 13 May 2016 15:02:37 +0200 Subject: [sles-beta] Welcome to the Beta Program of SUSE Linux Enterprise 12 Service Pack 2 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF9DDFB9F@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DDFB9F@hqmbx6.eur.ad.sag> Message-ID: <4647F90C-FAFF-4F69-B771-FA9024743AB1@suse.com> Hi, > On 13 May 2016, at 07:25, Waite, Dick (External) wrote: > > Grand New Friday, > > Will we have to register the machines we are using for the SP-2 Beta ? At the moment the machines I have moved into my SP-2 group all have a SP-1 GA registration plus the SDK, Script and workstation ext. Yes, there will be registration code like we did provide for SLE 12 SP1 Beta! More information will come soon, for now our focus is on releasing beta1 ; ) > As the Beta will be public I was thinking there wouldn't be a need to register ? I don't have a code anyway. Registration code will be available to VIP by default but not for the public. Stay tuned! Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From ast at suse.com Fri May 13 13:25:44 2016 From: ast at suse.com (Anja Stock) Date: Fri, 13 May 2016 21:25:44 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP2 Beta 1 is available In-Reply-To: <32f8252a3d5d5d77547896257f9d9f39@suse.de> References: <32f8252a3d5d5d77547896257f9d9f39@suse.de> Message-ID: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta participants, we are happy to announce the first Beta of SUSE Linux Enterprise Server 12 SP2. ISO images are now available for download now. Please go to https://www.novell.com/beta and select "View my beta page". Here you should see all Betas you are part of. Note that the directory contains the images for the SDK as well as for SLED. We offer 3 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and the third DVD the debuginfo packages. The final product will not contain the debuginfo packages on the media. For installation purposes you just need Media 1 for your architecture. Please verify the sha256sum of the ISO using the SHA256SUMS file, which can be found in the same directory on the download servers. Known issues: SLED / WE (desktop related issues) ----------------------------------- Bug 979051: GNOME desktop (SLES and SLED): keyboard layout is set to english by default, you need to switch layout using keyboard layout switcher on panel Bug 979072: GNOME desktop: icons are not properly organised on new accounts vinagre: RDP support is disabled for now, will come back in future Beta milestone Bug 979498: .xsession-errors* are empty for GNOME session. Workaround: use journalctl -b SLE Classic: menus are not positioned properly. Will be fixed in future Beta milestone SLES: ----- Bug 979497: [Build1507] Kernel panic - kernel bug at ../drivers/scsi/aacraid/commsup.c:814 At the moment it is not clear if the firmeware itself is affected or not. The number of affected customers should be small. Bug 978586: Incorrect signature on shim loader. The workaround is: disable Secure boot on UEFI firmware s390x: installation on CDL DASD on KVM still sees problems With this Beta1 snapshot we have reached several milestones: o Milestone: All maintenance web updates from previous product are integrated. o Milestone: Update is working (installable media). o Milestone: Kernel and installation works on all targeted machines. o Continue install and functional tests. o Start update tests. o Start tests of new/updated device drivers. o Start performance and regression tests. o Start legal review of SLE12 SP1 contents. o First version of Release Notes is available For the next Beta-Release we are targetting these actions and milestones: o Milestone: All SLE12 SP1 features have been functionally tested. o Milestone: All new/updated device drivers have been tested. o Continue install and functional tests. o Continue tests of new/updated device drivers. o Start system test. Thanks in advance for all your testing. 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 ast at suse.com Fri May 13 13:34:55 2016 From: ast at suse.com (Anja Stock) Date: Fri, 13 May 2016 21:34:55 +0200 Subject: [sles-beta] changelog for SLES12 SP2 Beta 1 In-Reply-To: References: Message-ID: <03aebe1507add41c73e5e81517cbb7a0@suse.de> Dear Customer, Partners, Fellows, please find attached the Changelog differences between SLE 12 SP1 GM and SLE 12 SP2 Beta 1 images. The complete changelog can be found on DVD 1. Thanks, Your SUSE Linux Enterprise Team -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: changelog.tgz Type: application/x-compressed-tar Size: 704604 bytes Desc: not available URL: From albrecht at opensourceservices.de Mon May 16 01:55:04 2016 From: albrecht at opensourceservices.de (Peter Albrecht) Date: Mon, 16 May 2016 09:55:04 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP2 Beta 1 is available In-Reply-To: References: <32f8252a3d5d5d77547896257f9d9f39@suse.de> Message-ID: <201605160955.04396.albrecht@opensourceservices.de> Hallo Anja, On Friday 13 May 2016 21:25:44 Anja Stock wrote: > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Dear Beta participants, > > we are happy to announce the first Beta of > > SUSE Linux Enterprise Server 12 SP2. > > ISO images are now available for download now. Please go to > https://www.novell.com/beta and select "View my beta page". > Here you should see all Betas you are part of. ich sehe nur die ISOs f?r SLED und SDK bzw. SLE HAE, aber nicht die f?r SLES. K?nnt Ihr bitte nochmal kontrollieren, ob ich die notwendigen Berechtigungen habe? Mein Benutzername ist peteralbrecht. Danke und viele Gr??e, Peter -- Peter Albrecht Ulmenstra?e 3 85609 Aschheim Telefon 0173-3528664 From vmoutoussamy at suse.com Tue May 17 03:58:17 2016 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 17 May 2016 11:58:17 +0200 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP2 Beta 1 is available In-Reply-To: <201605160955.04396.albrecht@opensourceservices.de> References: <32f8252a3d5d5d77547896257f9d9f39@suse.de> <201605160955.04396.albrecht@opensourceservices.de> Message-ID: <65F8638C-A8E6-4A09-81C5-9F03F3C69425@suse.com> Hi, > On 16 May 2016, at 09:55, Peter Albrecht wrote: > > Hallo Anja, > > On Friday 13 May 2016 21:25:44 Anja Stock wrote: >> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >> !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! >> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >> >> Dear Beta participants, >> >> we are happy to announce the first Beta of >> >> SUSE Linux Enterprise Server 12 SP2. >> >> ISO images are now available for download now. Please go to >> https://www.novell.com/beta and select "View my beta page". >> Here you should see all Betas you are part of. > > ich sehe nur die ISOs f?r SLED und SDK bzw. SLE HAE, aber nicht die f?r > SLES. K?nnt Ihr bitte nochmal kontrollieren, ob ich die notwendigen > Berechtigungen habe? Mein Benutzername ist peteralbrecht. I?m the main beta ?administrator? of the SLE Beta Program, so please contact me at beta-programs at lists.suse.com for any issue like that. Sadly, I?m not fluent in german so please write your request in english (or french will be ok ; ). Anyway, you should be able to retrieve SLES now. Sorry for the inconvenience, Regards; -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From Dick.Waite at softwareag.com Tue May 17 14:31:02 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Tue, 17 May 2016 20:31:02 +0000 Subject: [sles-beta] Registraion Keys Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE0D89@hqmbx6.eur.ad.sag> Grand Evening, It would make the updates cleaner and easier to follow if we had the Beta2 registration keys. __R ________________________________________ From: Waite, Dick (External) Subject: RE: [sles-beta] [ANNOUNCE] SLES 12 SP2 Beta 1 is available Grand New Day, Nags about not having a registration number but skip and skip gets you running the update. This is on a VMware x86_64 machine. __R 14-05-2016 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 From Dick.Waite at softwareag.com Wed May 18 03:02:48 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Wed, 18 May 2016 09:02:48 +0000 Subject: [sles-beta] GRUB and VMware disks Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE106B@hqmbx6.eur.ad.sag> Grand Day, A machine that under SLES12-SP1 updates and creates / writes a happy GRUB2 is now with SP-2 Beta1 having issues, see first 2 png's Second issue is almost the same as SLES12 SP1 Beta1 we have having issues to access LVM VMware disks, see last two png. Are these know issues or my fingers or should I create a bug ? This is happening on all my LVM VMware machines. I have not tried a new install as I don't do new installs. __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 -------------- A non-text attachment was scrubbed... Name: 2016-05-18_09h32_24.png Type: image/png Size: 56415 bytes Desc: 2016-05-18_09h32_24.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-18_10h09_20.png Type: image/png Size: 56925 bytes Desc: 2016-05-18_10h09_20.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-18_10h45_48.png Type: image/png Size: 42624 bytes Desc: 2016-05-18_10h45_48.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-18_10h46_12.png Type: image/png Size: 44685 bytes Desc: 2016-05-18_10h46_12.png URL: From jreidinger at suse.com Wed May 18 03:10:02 2016 From: jreidinger at suse.com (Josef Reidinger) Date: Wed, 18 May 2016 11:10:02 +0200 Subject: [sles-beta] GRUB and VMware disks In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF9DE106B@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE106B@hqmbx6.eur.ad.sag> Message-ID: <20160518111002.058e3726@pepa.labs.suse.cz> Hi Dick, it is error message from grub2. Parameters --no-nvram and --removable is not correct and it will be fixed for Beta2, but it is probably not root of issue. To determine what kind of problem it is I need to know your exact partitioning scheme. Is /dev/sdb really partition-less disk? Do you use LVM? I think it really deserve bug report as it need deeper investigation of your partitioning and if bootloader configuration is correct in your use case. Josef On Wed, 18 May 2016 09:02:48 +0000 "Dick (External) Waite" wrote: > Grand Day, > > A machine that under SLES12-SP1 updates and creates / writes a happy > GRUB2 is now with SP-2 Beta1 having issues, see first 2 png's > > Second issue is almost the same as SLES12 SP1 Beta1 we have having > issues to access LVM VMware disks, see last two png. > > Are these know issues or my fingers or should I create a bug ? > > This is happening on all my LVM VMware machines. I have not tried a > new install as I don't do new installs. > > __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 > From Dick.Waite at softwareag.com Wed May 18 10:39:42 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Wed, 18 May 2016 16:39:42 +0000 Subject: [sles-beta] GRUB and VMware disks In-Reply-To: <20160518155957.GA8791@qualcomm.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE106B@hqmbx6.eur.ad.sag>, <20160518155957.GA8791@qualcomm.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE12D3@hqmbx6.eur.ad.sag> Hi Mike, Have a look at bug# 945095 __R ________________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Marion, Mike [mmarion at qualcomm.com] Sent: 18 May 2016 18:00 To: sles-beta at lists.suse.com Subject: Re: [sles-beta] GRUB and VMware disks On Wed, May 18, 2016 at 09:02:48AM +0000, Waite, Dick (External) wrote: > Second issue is almost the same as SLES12 SP1 Beta1 we have having issues to > access LVM VMware disks, see last two png. Seeing the same (likely) issue with LVM inside KVM installs, going to try bare metal today. If I log into the emergency mode and run lvscan -v it shows all but the / volume as inactive. I checked and while /etc/lvm.conf has use_lvmetad = 1 that is set to 0 inside the initrd automatically. I recall the 12.1 beta had similar issues early on as well. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com Homer: "Marge! The bathroom scale is lying again!" ==> Simpsons 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 From Dick.Waite at softwareag.com Fri May 20 02:03:08 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 20 May 2016 08:03:08 +0000 Subject: [sles-beta] Which SDK to use.. Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE1F32@hqmbx6.eur.ad.sag> Grand Morning, We have a iso image of an SLE 12 SDK SP-2 Beta1 for each platform and SLE-SDK12-SP2-Pool. Are they the same ? Why do we have the iso image if one can also use the pool version ? Is this part of the registry ministry.... Just interested... __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: From kukuk at suse.de Fri May 20 02:09:39 2016 From: kukuk at suse.de (Thorsten Kukuk) Date: Fri, 20 May 2016 10:09:39 +0200 Subject: [sles-beta] Which SDK to use.. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF9DE1F32@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE1F32@hqmbx6.eur.ad.sag> Message-ID: <20160520080939.GA27939@suse.de> On Fri, May 20, Waite, Dick (External) wrote: > Grand Morning, > > We have a iso image of an SLE 12 SDK SP-2 Beta1 for each platform and SLE-SDK12-SP2-Pool. Are they the same ? Yes, this is our standard setup for every product and they are the same. That's the case since a really, really, really long time. > Why do we have the iso image if one can also use the pool version ? That's a special service Beta testers "normal paying customers" don't get. So that you don't need to go online with your Beta, but can install everything local from a media. Thorsten > Is this part of the registry ministry.... > > Just interested... > > __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 > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From Dick.Waite at softwareag.com Fri May 20 02:18:19 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Fri, 20 May 2016 08:18:19 +0000 Subject: [sles-beta] Which SDK to use.. In-Reply-To: <20160520080939.GA27939@suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE1F32@hqmbx6.eur.ad.sag>, <20160520080939.GA27939@suse.de> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE1FAA@hqmbx6.eur.ad.sag> Many Thanks Thorsten for the good words and speedy reply. So I can happily use the pool version and save a iso download. I have the web-scriping from the pool, so I'll take the SDK too. Have you all a grand day, I'm deep in an old rock quarry north of the Taunus, people put databases in very strange places... __R ________________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de] Sent: 20 May 2016 10:09 To: sles-beta at lists.suse.com Subject: Re: [sles-beta] Which SDK to use.. On Fri, May 20, Waite, Dick (External) wrote: > Grand Morning, > > We have a iso image of an SLE 12 SDK SP-2 Beta1 for each platform and SLE-SDK12-SP2-Pool. Are they the same ? Yes, this is our standard setup for every product and they are the same. That's the case since a really, really, really long time. > Why do we have the iso image if one can also use the pool version ? That's a special service Beta testers "normal paying customers" don't get. So that you don't need to go online with your Beta, but can install everything local from a media. Thorsten > Is this part of the registry ministry.... > > Just interested... > > __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 > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From pokorra at uni-siegen.de Sat May 21 21:49:37 2016 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Sun, 22 May 2016 05:49:37 +0200 Subject: [sles-beta] slurm at network-cluster-repository Message-ID: <1463888977.1763.6.camel@uni-siegen.de> Hello, this is not a special Beta bug, but it has something to do with SLES 12. I want to install the slurm packages at SLES 12 SP 1 from the repository: http://download.opensuse.org/repositories/network:/cluster/SLE_12/ The slurm package is missing a dependency. # zypper install slurm Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides libhwloc.so.5()(64bit) needed by slurm-15.08.2-1.5.x86_64 Solution 1: do not install slurm-15.08.2-1.5.x86_64 Solution 2: break slurm-15.08.2-1.5.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): ... The package libhwloc5 with the version '2.0-24' from the same repository do not provide the necessary dependency. # rpm -qa | grep libhwloc5 libhwloc5-2.0-24.2.x86_64 # rpm -ql libhwloc5 /usr/lib64/libhwloc.so.0 /usr/lib64/libhwloc.so.0.0.0 /usr/lib64/libnetloc.so.0 /usr/lib64/libnetloc.so.0.0.0 # # rpm -q --provides libhwloc5 libhwloc.so.0()(64bit) libhwloc5 = 2.0-24.2 libhwloc5(x86-64) = 2.0-24.2 libnetloc.so.0()(64bit) Best regards, Gerd Pokorra From kukuk at suse.de Sat May 21 22:52:50 2016 From: kukuk at suse.de (Thorsten Kukuk) Date: Sun, 22 May 2016 06:52:50 +0200 Subject: [sles-beta] slurm at network-cluster-repository In-Reply-To: <1463888977.1763.6.camel@uni-siegen.de> References: <1463888977.1763.6.camel@uni-siegen.de> Message-ID: <20160522045250.GA19914@suse.de> On Sun, May 22, Gerd Pokorra wrote: > Hello, > > this is not a special Beta bug, but it has something to do with SLES 12. > > > I want to install the slurm packages at SLES 12 SP 1 from the > repository: > http://download.opensuse.org/repositories/network:/cluster/SLE_12/ > > > The slurm package is missing a dependency. Sorry, but this has nothing to do with SLES, that's a standard openSUSE development project. slurm does not build with the new hwlock library, the openSUSE slurm maintainer has to fix that. But that's not even a SUSE employee. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From pokorra at uni-siegen.de Sun May 22 04:45:17 2016 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Sun, 22 May 2016 12:45:17 +0200 Subject: [sles-beta] slurm at network-cluster-repository In-Reply-To: <20160522045250.GA19914@suse.de> References: <1463888977.1763.6.camel@uni-siegen.de> <20160522045250.GA19914@suse.de> Message-ID: <1463913917.1997.4.camel@uni-siegen.de> Hello Thosten, thank you for giving me the background information. If have done the rebuild of a hwloc.src.rpm. After installation of that libhwloc I can install slurm without problem. slc3:~/slurm/specs/hwloc # zypper install /usr/src/packages/RPMS/x86_64/libhwloc5-1.4.1-1.1.x86_64.rpm Daten des Repositories laden ... Installierte Pakete lesen ... Paketabh?ngigkeiten aufl?sen ... Das folgende NEUE Paket wird installiert: libhwloc5 Das folgende Paket wird vom Anbieter nicht unterst?tzt: libhwloc5 1 neues Paket zu installieren. Overall download size: 218,8 KiB. Already cached: 0 B. Nach der Operation werden zus?tzlich 752,5 KiB belegt. Fortfahren? [j/n/? zeigt alle Optionen] (j): Paket libhwloc5-1.4.1-1.1.x86_64 wird abgerufen (1/1), 218,8 KiB (752,5 KiB entpackt) Test auf Dateikonflikte: ...........................................[fertig] (1/1) Installation von: libhwloc5-1.4.1-1.1 ........................[fertig] slc3:~/slurm/specs/hwloc # zypper install slurm Daten des Repositories laden ... Installierte Pakete lesen ... Paketabh?ngigkeiten aufl?sen ... Die folgenden 3 NEUEN Pakete werden installiert: libmysqlclient18 slurm slurm-plugins Die folgenden 2 Pakete werden vom Anbieter nicht unterst?tzt: slurm slurm-plugins 3 neue Pakete zu installieren. Overall download size: 5,9 MiB. Already cached: 0 B. Nach der Operation werden zus?tzlich 49,3 MiB belegt. Fortfahren? [j/n/? zeigt alle Optionen] (j): Have a nice Sunday Gerd Am Sonntag, den 22.05.2016, 06:52 +0200 schrieb Thorsten Kukuk: > On Sun, May 22, Gerd Pokorra wrote: > > > Hello, > > > > this is not a special Beta bug, but it has something to do with SLES 12. > > > > > > I want to install the slurm packages at SLES 12 SP 1 from the > > repository: > > http://download.opensuse.org/repositories/network:/cluster/SLE_12/ > > > > > > The slurm package is missing a dependency. > > Sorry, but this has nothing to do with SLES, that's a standard > openSUSE development project. > > > slurm does not build with the new hwlock library, the openSUSE > slurm maintainer has to fix that. But that's not even a SUSE employee. > > Thorsten > From kdupke at suse.com Mon May 23 01:57:23 2016 From: kdupke at suse.com (Kai Dupke) Date: Mon, 23 May 2016 09:57:23 +0200 Subject: [sles-beta] slurm at network-cluster-repository In-Reply-To: <1463888977.1763.6.camel@uni-siegen.de> References: <1463888977.1763.6.camel@uni-siegen.de> Message-ID: <5742B7E3.8000806@suse.com> On 05/22/2016 05:49 AM, Gerd Pokorra wrote: > Hello, > > this is not a special Beta bug, but it has something to do with SLES 12. > > > I want to install the slurm packages at SLES 12 SP 1 from the > repository: > http://download.opensuse.org/repositories/network:/cluster/SLE_12/ Please give the packages from http://build.openhpc.community/OpenHPC:/1.1/SLE_12_SP1/ a try. In case this doesn't work please let me know off the beta mailing list. This contains much more HPC stuff of course - feedback appreciated, too. regards, Kai Dupke Senior Product Manager Server Product Line -- Sell not virtue to purchase wealth, nor liberty to purchase power. Phone: +49-(0)5102-9310828 Mail: kdupke at suse.com Mobile: +49-(0)173-5876766 WWW: www.suse.com SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF:Felix Imend?rffer,Jane Smithard,Graham Norton,HRB 21284 (AG N?rnberg) From pokorra at uni-siegen.de Mon May 23 08:14:36 2016 From: pokorra at uni-siegen.de (Gerd Pokorra) Date: Mon, 23 May 2016 16:14:36 +0200 Subject: [sles-beta] slurm at network-cluster-repository In-Reply-To: <5742B7E3.8000806@suse.com> References: <1463888977.1763.6.camel@uni-siegen.de> <5742B7E3.8000806@suse.com> Message-ID: <1464012876.1700.23.camel@uni-siegen.de> Hello, I just tried the repository from http://build.openhpc.community/OpenHPC:/1.1/SLE_12_SP1/ It works fine. Best regards, Gerd Pokorra Am Montag, den 23.05.2016, 09:57 +0200 schrieb Kai Dupke: > On 05/22/2016 05:49 AM, Gerd Pokorra wrote: > > Hello, > > > > this is not a special Beta bug, but it has something to do with SLES 12. > > > > > > I want to install the slurm packages at SLES 12 SP 1 from the > > repository: > > http://download.opensuse.org/repositories/network:/cluster/SLE_12/ > > Please give the packages from > http://build.openhpc.community/OpenHPC:/1.1/SLE_12_SP1/ a try. > > In case this doesn't work please let me know off the beta mailing list. > > This contains much more HPC stuff of course - feedback appreciated, too. > > regards, > Kai Dupke > Senior Product Manager > Server Product Line From kukuk at suse.de Wed May 25 04:46:17 2016 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 25 May 2016 12:46:17 +0200 Subject: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing In-Reply-To: <3CBFA7CC2505A74B9C172B35128B886356A5D0AB@YLAV4460.INETPSA.com> References: <3CBFA7CC2505A74B9C172B35128B886356A5D0AB@YLAV4460.INETPSA.com> Message-ID: <20160525104617.GA31834@suse.de> On Wed, May 25, LOIC DEVULDER wrote: > C1-INTERNAL > > Hello all! > > It seems that the installed.xml file in /var/adm/autoinstall/cache is not generated anymore, and I can't find howto activate it during the installation. > Is it normal? It's good to have this file, I use it to be the base for an automated deployment using AutoYaST. /var/adm/autoinstall/cache is clearly a directory, on which content you should not relay and which you should not use. I guess this was temporary generated when generating /root/autoinst.xml during installation. So it can contain anything. /root/autoinst.xml is no longer generated during installation (that's why you don't see the temporary files any longer), because with SLE12 it is missing far too many configuration stuff. You need to create the autoinst.xml file now in the running system with corresponding YaST2 modules. This will also make sure on SLE12, that the xml file is really complete and not missing 50% of the stuff. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From etso_srva_linux at mpsa.com Wed May 25 08:35:07 2016 From: etso_srva_linux at mpsa.com ( etso-srva-linux) Date: Wed, 25 May 2016 14:35:07 +0000 Subject: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing In-Reply-To: <20160525104617.GA31834@suse.de> References: <3CBFA7CC2505A74B9C172B35128B886356A5D0AB@YLAV4460.INETPSA.com> <20160525104617.GA31834@suse.de> Message-ID: <3CBFA7CC2505A74B9C172B35128B886356A5D225@YLAV4460.INETPSA.com> Thanks, as long as I can have the final xml file it's ok for me :-) The installed.xml file was generated at the end of the installation. There was a message about this just after the installation configuration but there nothing now, maybe it would be good to have the same information about generating the xml file through YaST (or at least in the documentation). Regards / Cordialement, ___________________________________________________________________ PSA Peugeot Citro?n Devulder Lo?c (loic.devulder at mpsa.com) Senior Linux System Engineer / Linux HPC Specialist DF/DDCE/ISTA/DSEP/ULES - Linux Team Internal postal address: SX.BES.15 Phone Incident: 33 09 01 (L3 - firstly) or 22 92 40 (L4 - secondly) Office: +33 (0)9 66 66 69 06 (27 69 06) Mobile: +33 (0)6 87 72 47 31 ___________________________________________________________________ This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. -----Message d'origine----- De?: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Thorsten Kukuk Envoy??: mercredi 25 mai 2016 12:46 ??: sles-beta at lists.suse.com Objet?: Re: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing On Wed, May 25, LOIC DEVULDER wrote: > C1-INTERNAL > > Hello all! > > It seems that the installed.xml file in /var/adm/autoinstall/cache is not generated anymore, and I can't find howto activate it during the installation. > Is it normal? It's good to have this file, I use it to be the base for an automated deployment using AutoYaST. /var/adm/autoinstall/cache is clearly a directory, on which content you should not relay and which you should not use. I guess this was temporary generated when generating /root/autoinst.xml during installation. So it can contain anything. /root/autoinst.xml is no longer generated during installation (that's why you don't see the temporary files any longer), because with SLE12 it is missing far too many configuration stuff. You need to create the autoinst.xml file now in the running system with corresponding YaST2 modules. This will also make sure on SLE12, that the xml file is really complete and not missing 50% of the stuff. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From James.Taylor at eastcobbgroup.com Thu May 26 13:35:57 2016 From: James.Taylor at eastcobbgroup.com (James Taylor) Date: Thu, 26 May 2016 15:35:57 -0400 Subject: [sles-beta] yast2 Display Message-ID: <574717DD0200007500051858@inet.eastcobbgroup.com> Is there any way to keep yast2 to star without opening the full width of the screen. It has been doing this on all versions of sles12, and us really annoying. -jt James Taylor 678-697-9420 james.taylor at eastcobbgroup.com From fcrozat at suse.com Fri May 27 01:18:05 2016 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 27 May 2016 09:18:05 +0200 Subject: [sles-beta] yast2 Display In-Reply-To: <574717DD0200007500051858@inet.eastcobbgroup.com> References: <574717DD0200007500051858@inet.eastcobbgroup.com> Message-ID: <1464333485.13359.26.camel@suse.com> Le jeudi 26 mai 2016 ? 15:35 -0400, James Taylor a ?crit : > Is there any way to keep yast2 to star without opening the full width > of the screen. It has been doing this on all versions of sles12, and > us really annoying. By yast, do you mean Yast Control Center (ie the UI allowing to access each yast module) ? -- Frederic Crozat Enterprise Desktop Release Manager SUSE From msvec at suse.com Fri May 27 01:59:44 2016 From: msvec at suse.com (Michal Svec) Date: Fri, 27 May 2016 09:59:44 +0200 Subject: [sles-beta] Kernel and Xen changes in SLES 12 SP2 Message-ID: Dear Beta Tester, With SLES 12 SP2 there has been a notable change we would like to point out specifically during the Beta process. The Xen hypervisor functions have been ported over to the standard PV-OPS mechanism and are now included in the default kernel. Therefore there is no separate kernel-xen package and binary as everything is provided by the default kernel. The main purpose and benefit of this change is to have a single binary to cover complete functionality. This simplifies maintenance and management of the kernel, while also ensuring the kernel is more thoroughly tested. We have tested this kernel change extensively - in particular in the directly affected areas, but with the vast hardware and software combinations our customers use we wanted to point this out so that any potential corner cases are caught during the Beta phase. Below are more details about this change: AVAILABILITY The changes have been implemented and are available in SLES 12 SP2 Beta 1. USER-VISIBLE CHANGES Replacing kernel-xen with kernel-default means that you cannot rely on `uname -r` to determine whether or not you are running under a Xen hypervisor (for example, in a dom0 environment). If you have any scripts or tooling which perform this check, we recommend replacing the uname check with a test for the existence of /proc/xen/privcmd (which only exists in a Xen dom0 environment), or test an xl command, such as `xl info`. The pvops-based frontend block driver names devices using the 'xvd*' syntax. This naming syntax is used even if the VM configuration references devices using 'hd*' or 'sd*' syntax. This should not cause a problem with new VM installations, but when upgrading a VM to SLES 12 SP2, it may be necessary to manually change the name of the block devices in such places as /etc/fstab and /etc/default/grub. Referencing devices using UUID names should also avoid problems UPGRADE PROCESS The upgrade from SLES 11 or SLES 12 GA/SP1 follows the usual process and does not require anything special. KNOWN ISSUES We are not aware of any major bugs or issues. Thanks in advance for all your testing Your SUSE Linux Enterprise Team From Dick.Waite at softwareag.com Mon May 30 02:27:26 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 30 May 2016 08:27:26 +0000 Subject: [sles-beta] Beta Registration Codes Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE56AA@hqmbx6.eur.ad.sag> Grand Wet Morning, I ran some work this morning for SUSE looking for issues with virtual machines not getting their disks attached. Attached are some of the ?nags? we have been getting since Beta1 started, Friday 13th May. There are no registration codes for SP-2 beta, so you get a nag. I had a feeling last week I had more nags, the test I ran this morning gave results which need looking at, but while we are getting unknown access to the SCC how sure are we the code we are testing is the same day by day. I would have thought one would have the codes available before the iso?s are available, so we can do our registration well in advance. Could be I don?t understand what the issues are in giving us codes and getting rid of the nags and knowing you are getting good access to SCC code. Maybe it?s just a wet Monday morning but it?s the ?maybe? factor I don?t like when trying to QA/QE code. One needs the minimum number of variables, and the nags give me bad vibration, we need good vibration and good registration codes? __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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h18_21.png Type: image/png Size: 83913 bytes Desc: 2016-05-30_07h18_21.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h18_31.png Type: image/png Size: 82050 bytes Desc: 2016-05-30_07h18_31.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h18_47.png Type: image/png Size: 82046 bytes Desc: 2016-05-30_07h18_47.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h19_56.png Type: image/png Size: 84000 bytes Desc: 2016-05-30_07h19_56.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h21_07.png Type: image/png Size: 113092 bytes Desc: 2016-05-30_07h21_07.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h21_31.png Type: image/png Size: 84481 bytes Desc: 2016-05-30_07h21_31.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2016-05-30_07h21_44.png Type: image/png Size: 82746 bytes Desc: 2016-05-30_07h21_44.png URL: From lslezak at suse.cz Mon May 30 03:03:22 2016 From: lslezak at suse.cz (Ladislav Slezak) Date: Mon, 30 May 2016 11:03:22 +0200 Subject: [sles-beta] Beta Registration Codes In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF9DE56AA@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE56AA@hqmbx6.eur.ad.sag> Message-ID: <574C01DA.7090606@suse.cz> Hello, Dne 30.5.2016 v 10:27 Waite, Dick (External) napsal(a): [...] > Attached are some of the ?nags? we have been getting since Beta1 started, Friday > 13^th May. There are no registration codes for SP-2 beta, so you get a nag. I had > a feeling last week I had more nags, the test I ran this morning gave results > which need looking at, but while we are getting unknown access to the SCC how sure > are we the code we are testing is the same day by day. I just have tried Beta1 registering and got this results: - An invalid key: error "Unknown registration code" - A non-SP2 key: error "The subscription with the provided regcode does not include the requested product 'SUSE Linux Enterprise Server 12 SP2 x86_64' - An SP2 key: the registration succeeded, the update repository was added without any problem. According to the screenshots it seems that the system was registered successfully but the updates repository could not have been loaded. This looks like there is some problem on the SCC side or at updates.suse.com. You might try it again (maybe it was just a temporary issue), if you still get the error then report a bug at https://bugzilla.suse.com/ (use the "Registration" component). HTH -- Ladislav Slez?k Appliance department / YaST Developer Lihovarsk? 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak at suse.com SUSE From kukuk at suse.de Mon May 30 08:09:24 2016 From: kukuk at suse.de (Thorsten Kukuk) Date: Mon, 30 May 2016 16:09:24 +0200 Subject: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing In-Reply-To: <3CBFA7CC2505A74B9C172B35128B886356A5D225@YLAV4460.INETPSA.com> References: <3CBFA7CC2505A74B9C172B35128B886356A5D0AB@YLAV4460.INETPSA.com> <20160525104617.GA31834@suse.de> <3CBFA7CC2505A74B9C172B35128B886356A5D225@YLAV4460.INETPSA.com> Message-ID: <20160530140924.GA18613@suse.de> Hi, On Wed, May 25, etso-srva-linux wrote: > Thanks, as long as I can have the final xml file it's ok for me :-) > > The installed.xml file was generated at the end of the installation. There was a message about this just after the installation configuration but there nothing now, maybe it would be good to have the same information about generating the xml file through YaST (or at least in the documentation). Sometimes it really helps to read the release notes ;) It's documented there. Thorsten > > Regards / Cordialement, > ___________________________________________________________________ > PSA Peugeot Citro?n > Devulder Lo?c (loic.devulder at mpsa.com) > Senior Linux System Engineer / Linux HPC Specialist > DF/DDCE/ISTA/DSEP/ULES - Linux Team > Internal postal address: SX.BES.15 > Phone Incident: 33 09 01 (L3 - firstly) or 22 92 40 (L4 - secondly) > Office: +33 (0)9 66 66 69 06 (27 69 06) > Mobile: +33 (0)6 87 72 47 31 > ___________________________________________________________________ > > This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. > > > -----Message d'origine----- > De?: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Thorsten Kukuk > Envoy??: mercredi 25 mai 2016 12:46 > ??: sles-beta at lists.suse.com > Objet?: Re: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing > > On Wed, May 25, LOIC DEVULDER wrote: > > > C1-INTERNAL > > > > Hello all! > > > > It seems that the installed.xml file in /var/adm/autoinstall/cache is not generated anymore, and I can't find howto activate it during the installation. > > Is it normal? It's good to have this file, I use it to be the base for an automated deployment using AutoYaST. > > /var/adm/autoinstall/cache is clearly a directory, on which content > you should not relay and which you should not use. > I guess this was temporary generated when generating /root/autoinst.xml > during installation. So it can contain anything. > > /root/autoinst.xml is no longer generated during installation (that's why > you don't see the temporary files any longer), because with SLE12 it is > missing far too many configuration stuff. > > You need to create the autoinst.xml file now in the running system with > corresponding YaST2 modules. This will also make sure on SLE12, that > the xml file is really complete and not missing 50% of the stuff. > > Thorsten > > > -- > Thorsten Kukuk, Senior Architect SLES & Common Code Base > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany > GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From loic.devulder at mpsa.com Mon May 30 08:44:09 2016 From: loic.devulder at mpsa.com (LOIC DEVULDER) Date: Mon, 30 May 2016 14:44:09 +0000 Subject: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing In-Reply-To: <20160530140924.GA18613@suse.de> References: <3CBFA7CC2505A74B9C172B35128B886356A5D0AB@YLAV4460.INETPSA.com> <20160525104617.GA31834@suse.de> <3CBFA7CC2505A74B9C172B35128B886356A5D225@YLAV4460.INETPSA.com> <20160530140924.GA18613@suse.de> Message-ID: <3CBFA7CC2505A74B9C172B35128B886356A5E57C@YLAV4460.INETPSA.com> Hi Thorsten, You're right, in the 2.1.2 section, my bad :-) Regards / Cordialement, ___________________________________________________________________ PSA Groupe Devulder Lo?c (loic.devulder at mpsa.com) Senior Linux System Engineer / Linux HPC Specialist DF/DDCE/ISTA/DSEP/ULES - Linux Team Internal postal address: SX.BES.15 Phone Incident: 33 09 01 (L3 - firstly) or 22 92 40 (L4 - secondly) Office: +33 (0)9 66 66 69 06 (27 69 06) Mobile: +33 (0)6 87 72 47 31 ___________________________________________________________________ This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. -----Message d'origine----- De?: Thorsten Kukuk [mailto:kukuk at suse.de] Envoy??: lundi 30 mai 2016 16:09 ??: etso_srva_linux - BFetso_1 Cc?: sles-beta at lists.suse.com Objet?: Re: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing Hi, On Wed, May 25, etso-srva-linux wrote: > Thanks, as long as I can have the final xml file it's ok for me :-) > > The installed.xml file was generated at the end of the installation. There was a message about this just after the installation configuration but there nothing now, maybe it would be good to have the same information about generating the xml file through YaST (or at least in the documentation). Sometimes it really helps to read the release notes ;) It's documented there. Thorsten > > Regards / Cordialement, > ___________________________________________________________________ > PSA Peugeot Citro?n > Devulder Lo?c (loic.devulder at mpsa.com) > Senior Linux System Engineer / Linux HPC Specialist > DF/DDCE/ISTA/DSEP/ULES - Linux Team > Internal postal address: SX.BES.15 > Phone Incident: 33 09 01 (L3 - firstly) or 22 92 40 (L4 - secondly) > Office: +33 (0)9 66 66 69 06 (27 69 06) > Mobile: +33 (0)6 87 72 47 31 > ___________________________________________________________________ > > This message may contain confidential information. If you are not the intended recipient, please advise the sender immediately and delete this message. For further information on confidentiality and the risks inherent in electronic communication see http://disclaimer.psa-peugeot-citroen.com. > > > -----Message d'origine----- > De?: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Thorsten Kukuk > Envoy??: mercredi 25 mai 2016 12:46 > ??: sles-beta at lists.suse.com > Objet?: Re: [sles-beta] /var/adm/autoinstall/cache/installed.xml file missing > > On Wed, May 25, LOIC DEVULDER wrote: > > > C1-INTERNAL > > > > Hello all! > > > > It seems that the installed.xml file in /var/adm/autoinstall/cache is not generated anymore, and I can't find howto activate it during the installation. > > Is it normal? It's good to have this file, I use it to be the base for an automated deployment using AutoYaST. > > /var/adm/autoinstall/cache is clearly a directory, on which content > you should not relay and which you should not use. > I guess this was temporary generated when generating /root/autoinst.xml > during installation. So it can contain anything. > > /root/autoinst.xml is no longer generated during installation (that's why > you don't see the temporary files any longer), because with SLE12 it is > missing far too many configuration stuff. > > You need to create the autoinst.xml file now in the running system with > corresponding YaST2 modules. This will also make sure on SLE12, that > the xml file is really complete and not missing 50% of the stuff. > > Thorsten > > > -- > Thorsten Kukuk, Senior Architect SLES & Common Code Base > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany > GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From Dick.Waite at softwareag.com Mon May 30 13:39:57 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 30 May 2016 19:39:57 +0000 Subject: [sles-beta] Beta Registration Codes In-Reply-To: <574C01DA.7090606@suse.cz> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE56AA@hqmbx6.eur.ad.sag> <574C01DA.7090606@suse.cz> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF9DE58E6@hqmbx6.eur.ad.sag> Grand Eveing, At the moment I don't have a "registration code" for SLES12 SP-2 Beta. If you have one ? is it SUSE internal or can all the Beta user have access ? __R -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Ladislav Slezak Sent: Montag, 30. Mai 2016 11:03 To: sles-beta at lists.suse.com Subject: Re: [sles-beta] Beta Registration Codes Hello, Dne 30.5.2016 v 10:27 Waite, Dick (External) napsal(a): [...] > Attached are some of the ?nags? we have been getting since Beta1 > started, Friday 13^th May. There are no registration codes for SP-2 > beta, so you get a nag. I had a feeling last week I had more nags, the > test I ran this morning gave results which need looking at, but while > we are getting unknown access to the SCC how sure are we the code we are testing is the same day by day. I just have tried Beta1 registering and got this results: - An invalid key: error "Unknown registration code" - A non-SP2 key: error "The subscription with the provided regcode does not include the requested product 'SUSE Linux Enterprise Server 12 SP2 x86_64' - An SP2 key: the registration succeeded, the update repository was added without any problem. According to the screenshots it seems that the system was registered successfully but the updates repository could not have been loaded. This looks like there is some problem on the SCC side or at updates.suse.com. You might try it again (maybe it was just a temporary issue), if you still get the error then report a bug at https://bugzilla.suse.com/ (use the "Registration" component). HTH -- Ladislav Slez?k Appliance department / YaST Developer Lihovarsk? 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak at suse.com SUSE _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-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; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From vmoutoussamy at suse.com Tue May 31 09:54:01 2016 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 31 May 2016 17:54:01 +0200 Subject: [sles-beta] Beta Registration Codes In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF9DE58E6@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE56AA@hqmbx6.eur.ad.sag> <574C01DA.7090606@suse.cz> <46AC8C81C10B8C48820201DF2AE1D76DF9DE58E6@hqmbx6.eur.ad.sag> Message-ID: <600966CA-C94D-4939-920A-EC501869567C@suse.com> Hi, Sorry for the inconvenience but there is no Beta Registration Code _yet_. This is documented on http://beta.suse.com/private/SLE12/SP2-BETA/#2. Please be patient, we are planing to allow the registration for beta2 (scheduled for 2nd June). So stay tuned, all the information will be provided after beta2 released. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 30 May 2016, at 21:39, Waite, Dick (External) wrote: > > Grand Eveing, > > At the moment I don't have a "registration code" for SLES12 SP-2 Beta. If you have one ? is it SUSE internal or can all the Beta user have access ? > __R > > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Ladislav Slezak > Sent: Montag, 30. Mai 2016 11:03 > To: sles-beta at lists.suse.com > Subject: Re: [sles-beta] Beta Registration Codes > > Hello, > > Dne 30.5.2016 v 10:27 Waite, Dick (External) napsal(a): > [...] >> Attached are some of the ?nags? we have been getting since Beta1 >> started, Friday 13^th May. There are no registration codes for SP-2 >> beta, so you get a nag. I had a feeling last week I had more nags, the >> test I ran this morning gave results which need looking at, but while >> we are getting unknown access to the SCC how sure are we the code we are testing is the same day by day. > > I just have tried Beta1 registering and got this results: > > - An invalid key: error "Unknown registration code" > - A non-SP2 key: error "The subscription with the provided regcode does not include the requested product 'SUSE Linux Enterprise Server 12 SP2 x86_64' > - An SP2 key: the registration succeeded, the update repository was added > without any problem. > > According to the screenshots it seems that the system was registered successfully but the updates repository could not have been loaded. > > This looks like there is some problem on the SCC side or at updates.suse.com. > > You might try it again (maybe it was just a temporary issue), if you still get the error then report a bug at https://bugzilla.suse.com/ (use the "Registration" component). > > > HTH > > > -- > > Ladislav Slez?k > Appliance department / YaST Developer > Lihovarsk? 1060/12 > 190 00 Prague 9 / Czech Republic > tel: +420 284 028 960 > lslezak at suse.com > SUSE > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-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; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From Dick.Waite at softwareag.com Tue May 31 10:30:34 2016 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Tue, 31 May 2016 16:30:34 +0000 Subject: [sles-beta] Beta Registration Codes In-Reply-To: <600966CA-C94D-4939-920A-EC501869567C@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF9DE56AA@hqmbx6.eur.ad.sag> <574C01DA.7090606@suse.cz> <46AC8C81C10B8C48820201DF2AE1D76DF9DE58E6@hqmbx6.eur.ad.sag>, <600966CA-C94D-4939-920A-EC501869567C@suse.com> Message-ID: <20160531163033.1753919699.3728.20834@softwareag.com> Many Thanks for the good words Vincent. 2nd June 2016 is not so far away. I will stay tuned and keep an eye open on SCC.SUSE.com Many thanks, __R Sent from my BlackBerry 10 smartphone. Original Message From: Vincent Moutoussamy Sent: Tuesday, 31 May 2016 18:14 To: Waite, Dick (External) Cc: Ladislav Slezak; sles-beta at lists.suse.com Subject: Re: [sles-beta] Beta Registration Codes Hi, Sorry for the inconvenience but there is no Beta Registration Code _yet_. This is documented on http://beta.suse.com/private/SLE12/SP2-BETA/#2. Please be patient, we are planing to allow the registration for beta2 (scheduled for 2nd June). So stay tuned, all the information will be provided after beta2 released. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 30 May 2016, at 21:39, Waite, Dick (External) wrote: > > Grand Eveing, > > At the moment I don't have a "registration code" for SLES12 SP-2 Beta. If you have one ? is it SUSE internal or can all the Beta user have access ? > __R > > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Ladislav Slezak > Sent: Montag, 30. Mai 2016 11:03 > To: sles-beta at lists.suse.com > Subject: Re: [sles-beta] Beta Registration Codes > > Hello, > > Dne 30.5.2016 v 10:27 Waite, Dick (External) napsal(a): > [...] >> Attached are some of the ?nags? we have been getting since Beta1 >> started, Friday 13^th May. There are no registration codes for SP-2 >> beta, so you get a nag. I had a feeling last week I had more nags, the >> test I ran this morning gave results which need looking at, but while >> we are getting unknown access to the SCC how sure are we the code we are testing is the same day by day. > > I just have tried Beta1 registering and got this results: > > - An invalid key: error "Unknown registration code" > - A non-SP2 key: error "The subscription with the provided regcode does not include the requested product 'SUSE Linux Enterprise Server 12 SP2 x86_64' > - An SP2 key: the registration succeeded, the update repository was added > without any problem. > > According to the screenshots it seems that the system was registered successfully but the updates repository could not have been loaded. > > This looks like there is some problem on the SCC side or at updates.suse.com. > > You might try it again (maybe it was just a temporary issue), if you still get the error then report a bug at https://bugzilla.suse.com/ (use the "Registration" component). > > > HTH > > > -- > > Ladislav Slez?k > Appliance department / YaST Developer > Lihovarsk? 1060/12 > 190 00 Prague 9 / Czech Republic > tel: +420 284 028 960 > lslezak at suse.com > SUSE > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-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; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta