From lukas.ocilka at suse.com Mon Nov 9 07:05:52 2015 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Mon, 9 Nov 2015 15:05:52 +0100 Subject: [sles-beta] Major Autoyast problem / bug In-Reply-To: References: Message-ID: <5640A840.7040907@suse.com> On 9.11.2015 14:18, matthias.hofer at arz.at wrote: > Hello SLES beta team, > > We cannot install SLES12 SP1 (RC3) with our autoyast configurtion, I get > the following popup during installation initialization: > > Calling the YaST module `inst_autosetup has failed. More information can > be found near the end of the '/var/log/YaST2/y2log' file. > This is worth reporting a bug at http://bugzilla.suse.com/. Please, > attach also all YaST logs stored in the '/var/log/YaST2/' directory. See > http://en.opensuse.org/Bugs/YaSTfor more information about YaST logs. > > But I don't know how to get these files, as we are in autoinstallation > mode. What can we do? Hi Matthias, Thanks for the report. There are several ways of getting logs and it depends on the state in which the AutoYast is See https://en.opensuse.org/openSUSE:Report_a_YaST_bug Usually it's enough to switch to a console #2 by pressing Ctrl+Alt+F2 (Alt+F2) and then you have shell, network should be already up. Alternatively you could send us your AutoYast profile, but we might not be able to reproduce it. All in all, bugreport in Bugzilla would be great. I'm adding two of our AutoYast experts into Cc. Thanks in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux From schubi at suse.de Mon Nov 9 08:11:03 2015 From: schubi at suse.de (Stefan Schubert) Date: Mon, 9 Nov 2015 16:11:03 +0100 Subject: [sles-beta] Major Autoyast problem / bug In-Reply-To: References: <5640A840.7040907@suse.com> Message-ID: <5640B787.1070109@suse.de> On 09/11/15 16:00, matthias.hofer at arz.at wrote: > Hi Lukas, > > I was able to get the logs when using SSH-based autoyast. > > > [...] > > All in all, bugreport in Bugzilla would be great. I'm adding two of our > > AutoYast experts into Cc. > > Which product do I have to choose for SLES12 SP1 RC3? Yes, with component AutoYaST please. Thank you ! Greetings Stefan > > > Thank you, > > Matthias Hofer/ARZ > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX GmbH GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From schubi at suse.de Mon Nov 9 08:22:59 2015 From: schubi at suse.de (Stefan Schubert) Date: Mon, 9 Nov 2015 16:22:59 +0100 Subject: [sles-beta] Major Autoyast problem / bug In-Reply-To: References: <5640A840.7040907@suse.com> <5640B787.1070109@suse.de> Message-ID: <5640BA53.5080609@suse.de> On 09/11/15 16:18, Matthias Hofer wrote: > > [...] > > > I was able to get the logs when using SSH-based autoyast. > > > > > > > [...] > > > > All in all, bugreport in Bugzilla would be great. I'm adding two > of our > > > > AutoYast experts into Cc. > > > > > > Which product do I have to choose for SLES12 SP1 RC3? > > > > Yes, with component AutoYaST please. > > Thank you ! > > My problem is that there is no such product available in > bugzilla.suse.com, as far as I can see. > > Therefore I'd like to repeat my question: Which product do I have to > choose for this bug in SLES12 SP1 RC3? > > Thanks again, > > Matthias Hofer Does the link https://bugzilla.suse.com/enter_bug.cgi?product=SUSE%20Linux%20Enterprise%20Server%2012%20SP1 work for you ? Greetings Stefan -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX GmbH GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From lukas.ocilka at suse.com Mon Nov 9 08:23:20 2015 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Mon, 9 Nov 2015 16:23:20 +0100 Subject: [sles-beta] Major Autoyast problem / bug In-Reply-To: References: <5640A840.7040907@suse.com> <5640B787.1070109@suse.de> Message-ID: <5640BA68.7070203@suse.com> On 9.11.2015 16:18, matthias.hofer at arz.at wrote: >> [...] >> > I was able to get the logs when using SSH-based autoyast. >> > >> > > [...] >> > > All in all, bugreport in Bugzilla would be great. I'm adding two > of our >> > > AutoYast experts into Cc. >> > >> > Which product do I have to choose for SLES12 SP1 RC3? >> >> Yes, with component AutoYaST please. >> Thank you ! > > My problem is that there is no such product available in > bugzilla.suse.com, as far as I can see. > > Therefore I'd like to repeat my question: Which product do I have to > choose for this bug in SLES12 SP1 RC3? Please use any SLES (e.g. SUSE Linux Enterprise Server 12 SP1) you will see or any openSUSE and give is the bug number so we can change it SLES 12 SP1 RC3 ourselves. The product you choose does not matter, we will change it. Just please attach Yast logs and your AutoYast profile. That are the most important pieces. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux From mkrapp at suse.com Mon Nov 9 08:31:00 2015 From: mkrapp at suse.com (Michael Krapp) Date: Mon, 9 Nov 2015 16:31:00 +0100 Subject: [sles-beta] Major Autoyast problem / bug In-Reply-To: References: <5640A840.7040907@suse.com> Message-ID: <20151109153100.GA24160@wawa.suse.de> Hi Matthias, * matthias.hofer at arz.at schrieb 20151109 16:01: > Hi Lukas, > > I was able to get the logs when using SSH-based autoyast. > > > [...] > > All in all, bugreport in Bugzilla would be great. I'm adding two of our > > AutoYast experts into Cc. > > Which product do I have to choose for SLES12 SP1 RC3? Alternatively you can open a Service Request in the Customer Center, using the Beta credentials. Support then takes care of creating the bug and adding you to Cc. > Thank you, > > Matthias Hofer/ARZ -- Kind regards / Cordialement / Mit freundlichen Gr??en Michael Krapp, Technical Support Engineer Worldwide Support Services Linux SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) Maxfeldstr. 5, D-90409 N?rnberg From fcrozat at suse.com Mon Nov 9 08:36:47 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 09 Nov 2015 16:36:47 +0100 Subject: [sles-beta] Major Autoyast problem / bug In-Reply-To: <5640BA53.5080609@suse.de> References: <5640A840.7040907@suse.com> <5640B787.1070109@suse.de> <5640BA53.5080609@suse.de> Message-ID: <1447083407.21192.13.camel@suse.com> Le lundi 09 novembre 2015 ? 16:22 +0100, Stefan Schubert a ?crit : > On 09/11/15 16:18, Matthias Hofer wrote: > > > [...] > > > > I was able to get the logs when using SSH-based autoyast. > > > > > > > > > [...] > > > > > All in all, bugreport in Bugzilla would be great. I'm adding > > > > > two > > of our > > > > > AutoYast experts into Cc. > > > > > > > > Which product do I have to choose for SLES12 SP1 RC3? > > > > > > Yes, with component AutoYaST please. > > > Thank you ! > > > > My problem is that there is no such product available in > > bugzilla.suse.com, as far as I can see. > > > > Therefore I'd like to repeat my question: Which product do I have > > to > > choose for this bug in SLES12 SP1 RC3? > > > > Thanks again, > > > > Matthias Hofer > > Does the link > https://bugzilla.suse.com/enter_bug.cgi?product=SUSE%20Linux%20Enterp > rise%20Server%2012%20SP1 > work for you ? A reminder for everybody here: beta testers can't open bugs on bugzilla.suse.com directly and should use service requests instead (available from SUSE Customer Center). -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Joel.Barbieri at merge.com Mon Nov 9 10:40:02 2015 From: Joel.Barbieri at merge.com (Joel Barbieri) Date: Mon, 9 Nov 2015 17:40:02 +0000 Subject: [sles-beta] LVM startup issues... Message-ID: I am having issues with LVM startup on boot. My autoyast profile creates a traditional disk layout, and automatically creates an LVM volume. On system reboot after installation [or anytime] it cannot successfully mount the volume it created. It instead times out waiting for the device [dev-vg00-lv_emageon]. All volumes are done by name and not by UUID or anything more exotic. Logging in shows the device to be available from via vgs and lvs, and active, but it is not available via /dev [e.g. /dev/vg00/lv_emageon]. /dev/mapper is empty... Running journalctl tells me... /var/lock/lvm/V_vg00:aux: open failed: No such file or directory Can't get lock for vg00 Failed to read Volume Group "vg00" (xkrW06-vHO2-12OW-DX...) during autoactivation. Starting Activation of VM2 logical volumes... Lvmetad is active, skipping direct activation during sysinit... ... Looks like attempts to start encrypted, lvm2, remote, with all LVM "skipping direct activation"... Followed by the timeout and fail... Anyone have any great hints? I may be ablet o workaround with some autoyast profile changes, or by using uuid, but possibly not. It seems similar to prior lvm systemd startup issues that occurred in OpenSuSE. This does not occur in SLES12SP0 with the same autoyast profile. Bug? Or is it more likely I'm doing something not quite supported any longer with systemd? -Joel Joel Barbieri Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 262-369-3118 joel.barbieri at merge.com From Dick.Waite at softwareag.com Mon Nov 9 11:07:04 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 9 Nov 2015 18:07:04 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: Message-ID: <20151109180704.5374037.62132.16395@softwareag.com> Evening, If this is Beta2 or 3 then it's known. If you see it with RC2 then it's an issue. __R Sent from my BlackBerry 10 smartphone. Original Message From: Joel Barbieri Sent: Monday, 9 November 2015 18:41 To: sles-beta at lists.suse.com Subject: [sles-beta] LVM startup issues... I am having issues with LVM startup on boot. My autoyast profile creates a traditional disk layout, and automatically creates an LVM volume. On system reboot after installation [or anytime] it cannot successfully mount the volume it created. It instead times out waiting for the device [dev-vg00-lv_emageon]. All volumes are done by name and not by UUID or anything more exotic. Logging in shows the device to be available from via vgs and lvs, and active, but it is not available via /dev [e.g. /dev/vg00/lv_emageon]. /dev/mapper is empty... Running journalctl tells me... /var/lock/lvm/V_vg00:aux: open failed: No such file or directory Can't get lock for vg00 Failed to read Volume Group "vg00" (xkrW06-vHO2-12OW-DX...) during autoactivation. Starting Activation of VM2 logical volumes... Lvmetad is active, skipping direct activation during sysinit... ... Looks like attempts to start encrypted, lvm2, remote, with all LVM "skipping direct activation"... Followed by the timeout and fail... Anyone have any great hints? I may be ablet o workaround with some autoyast profile changes, or by using uuid, but possibly not. It seems similar to prior lvm systemd startup issues that occurred in OpenSuSE. This does not occur in SLES12SP0 with the same autoyast profile. Bug? Or is it more likely I'm doing something not quite supported any longer with systemd? -Joel Joel Barbieri Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 262-369-3118 joel.barbieri at merge.com _______________________________________________ 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 Joel.Barbieri at merge.com Mon Nov 9 11:15:30 2015 From: Joel.Barbieri at merge.com (Joel Barbieri) Date: Mon, 9 Nov 2015 18:15:30 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: <20151109180704.5374037.62132.16395@softwareag.com> References: <20151109180704.5374037.62132.16395@softwareag.com> Message-ID: sles-release-12.1-1.292.x86_64 from RC3. So...an SR? I am just surprised that no one else is still experiencing... But then again, I'm always surprised when things I have been doing for a decade just stop working... -Joel -----Original Message----- From: Waite, Dick (External) [mailto:Dick.Waite at softwareag.com] Sent: Monday, November 09, 2015 12:07 PM To: Joel Barbieri ; sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Evening, If this is Beta2 or 3 then it's known. If you see it with RC2 then it's an issue. __R Sent from my BlackBerry 10 smartphone. Original Message From: Joel Barbieri Sent: Monday, 9 November 2015 18:41 To: sles-beta at lists.suse.com Subject: [sles-beta] LVM startup issues... I am having issues with LVM startup on boot. My autoyast profile creates a traditional disk layout, and automatically creates an LVM volume. On system reboot after installation [or anytime] it cannot successfully mount the volume it created. It instead times out waiting for the device [dev-vg00-lv_emageon]. All volumes are done by name and not by UUID or anything more exotic. Logging in shows the device to be available from via vgs and lvs, and active, but it is not available via /dev [e.g. /dev/vg00/lv_emageon]. /dev/mapper is empty... Running journalctl tells me... /var/lock/lvm/V_vg00:aux: open failed: No such file or directory Can't get lock for vg00 Failed to read Volume Group "vg00" (xkrW06-vHO2-12OW-DX...) during autoactivation. Starting Activation of VM2 logical volumes... Lvmetad is active, skipping direct activation during sysinit... ... Looks like attempts to start encrypted, lvm2, remote, with all LVM "skipping direct activation"... Followed by the timeout and fail... Anyone have any great hints? I may be ablet o workaround with some autoyast profile changes, or by using uuid, but possibly not. It seems similar to prior lvm systemd startup issues that occurred in OpenSuSE. This does not occur in SLES12SP0 with the same autoyast profile. Bug? Or is it more likely I'm doing something not quite supported any longer with systemd? -Joel Joel Barbieri Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 262-369-3118 joel.barbieri at merge.com _______________________________________________ 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 Dick.Waite at softwareag.com Mon Nov 9 11:25:29 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 9 Nov 2015 18:25:29 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: <20151109180704.5374037.62132.16395@softwareag.com>, Message-ID: <20151109182528.5374037.71371.16399@softwareag.com> The issues I had with LVM I think we're due. to systemd and ?how it worked with LVM. I'm on the move at the moment but a bit of paper I have says bug 945095 was covering the issues. The lady looking after LVM is Liuhua Wang. She is working out of Beijing. __R Sent from my BlackBerry 10 smartphone. Original Message From: Joel Barbieri Sent: Monday, 9 November 2015 19:16 To: sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... sles-release-12.1-1.292.x86_64 from RC3. So...an SR? I am just surprised that no one else is still experiencing... But then again, I'm always surprised when things I have been doing for a decade just stop working... -Joel -----Original Message----- From: Waite, Dick (External) [mailto:Dick.Waite at softwareag.com] Sent: Monday, November 09, 2015 12:07 PM To: Joel Barbieri ; sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Evening, If this is Beta2 or 3 then it's known. If you see it with RC2 then it's an issue. __R Sent from my BlackBerry 10 smartphone. Original Message From: Joel Barbieri Sent: Monday, 9 November 2015 18:41 To: sles-beta at lists.suse.com Subject: [sles-beta] LVM startup issues... I am having issues with LVM startup on boot. My autoyast profile creates a traditional disk layout, and automatically creates an LVM volume. On system reboot after installation [or anytime] it cannot successfully mount the volume it created. It instead times out waiting for the device [dev-vg00-lv_emageon]. All volumes are done by name and not by UUID or anything more exotic. Logging in shows the device to be available from via vgs and lvs, and active, but it is not available via /dev [e.g. /dev/vg00/lv_emageon]. /dev/mapper is empty... Running journalctl tells me... /var/lock/lvm/V_vg00:aux: open failed: No such file or directory Can't get lock for vg00 Failed to read Volume Group "vg00" (xkrW06-vHO2-12OW-DX...) during autoactivation. Starting Activation of VM2 logical volumes... Lvmetad is active, skipping direct activation during sysinit... ... Looks like attempts to start encrypted, lvm2, remote, with all LVM "skipping direct activation"... Followed by the timeout and fail... Anyone have any great hints? I may be ablet o workaround with some autoyast profile changes, or by using uuid, but possibly not. It seems similar to prior lvm systemd startup issues that occurred in OpenSuSE. This does not occur in SLES12SP0 with the same autoyast profile. Bug? Or is it more likely I'm doing something not quite supported any longer with systemd? -Joel Joel Barbieri Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 262-369-3118 joel.barbieri at merge.com _______________________________________________ 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 behlert at suse.com Fri Nov 13 08:02:30 2015 From: behlert at suse.com (Stefan Behlert) Date: Fri, 13 Nov 2015 16:02:30 +0100 Subject: [sles-beta] Status of SLE 12 SP1 GMC Message-ID: <20151113150230.GL11936@suse.de> Hi all, we know you are eagerly waiting for the GMC images to be released next Monday. Unfortunately, this will not be the case. We were busy this week to fix the last remaining show stoppers, and have been quite successful with that. Never-the-less, this took us for one nasty bug more time than we would have wished for, so we were only able to get (good) candidate builds this morning. QA is looking at these images at the moment, and will finish on Monday with the tests. If everything goes well, we will have a one day delay of the release, and you will get the GMC images on Tuesday. Currently it looks this will be the case and we all hope it stays that way ;) You will get another update on Monday next week. We are sorry for any inconveniences this may cause. thanks, Your SUSE Linux Enterprise Team -- Stefan Behlert, SUSE LINUX Release Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)