From thomas.kronseder at mtu.de Mon Nov 16 00:39:59 2015 From: thomas.kronseder at mtu.de (KRONSEDER, Thomas, Dr.) Date: Mon, 16 Nov 2015 07:39:59 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <1446455675.3706.8.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> Message-ID: <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> Hello, regarding: >> We do have quite a number of modules now that you can add into the >> mix, would it be very hard to have a KDE module so that one could >> have a DM of ones own choice ? >I think some announcements at SUSECon this week might help with that >(hint, hint ;) Do you have a pointer to the respective announcement(s) ? Mit freundlichen Gruessen / Best Regards Dr.-Ing. Thomas Kronseder MTU Aero Engines AG Fachgebietsverantwortlicher UNIX AdminCourt CAE / Analytik (POEA) CAE / analytic (POEA) Dachauer Strasse 665 80995 Muenchen Germany Tel: +49 (0)89 14 89 - 87 67 Fax: +49 (0)89 14 89 - 43 18 mailto:Thomas.Kronseder at mtu.de http://www.mtu.de -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Frederic Crozat Gesendet: Montag, 2. November 2015 10:15 An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLE-Classic et. al. Le dimanche 01 novembre 2015 ? 13:21 +0000, Waite, Dick (External) a ?crit : > Grand Foggy Sunday Afternoon, > > So time to tidy up some RC3 systems before the big GMC... > > One item on the DM does get my goat. I use SLE Classic 'cos that is > SUSE version of the wonderful KDE.. > How does one stop the icons on the desktop going walk about. In > Windows you can put them where you want them, hit refresh and they > stay put? Hmm, I'm not sure I understand your issue here. I've did additional tests and so far, if I move icons on the desktop, they stick to their new locations, whether I press F5 or I logout and login again. The only thing which is causing them to move is choosing "Organise Desktop by Name" > We seem to be stuck with just two screens for background and lock, > has anyone found a way to "personalize" ones own desktop, and have it > return after a restart? You mean your changes in background isn't not surviving logout or reboot ? If yes, it is a bug. My first guess would be gsettings-backend-dconf not being installed on your system (it is required by sle-gnome-basic pattern, so it should be always here). > We do have quite a number of modules now that you can add into the > mix, would it be very hard to have a KDE module so that one could > have a DM of ones own choice ? I think some announcements at SUSECon this week might help with that (hint, hint ;) > Talking of s390x I have not tried an install yet due to the issues > being reported. Can anyone confirm the s390x platform is good to > install a RC3 on ? Our tests shows RC3 can be installed on s390x -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From fcrozat at suse.com Mon Nov 16 00:52:10 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 16 Nov 2015 08:52:10 +0100 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> Message-ID: <1447660330.5052.13.camel@suse.com> Le lundi 16 novembre 2015 ? 07:39 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hello, > > regarding: > > > > We do have quite a number of modules now that you can add into > > > the > > > mix, would it be very hard to have a KDE module so that one could > > > have a DM of ones own choice ? > > > I think some announcements at SUSECon this week might help with > > that > > (hint, hint ;) > > Do you have a pointer to the respective announcement(s) ? I don't have any pointer but this was about SUSE Package Hub (so far, there is very few documentation available at https://en.opensuse.org/Portal:Backports?;) KDE 5 will be available there soon, but unsupported. I'm expecting broader announcement on Package hub soon but I don't have any ETA. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Mon Nov 16 01:09:52 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 16 Nov 2015 08:09:52 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <1447660330.5052.13.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp>, <1447660330.5052.13.camel@suse.com> Message-ID: <20151116080951.5374037.15769.16480@softwareag.com> Many Thanks for the update Frederic. Happy with not supported. If one gets issues then just back off to SLE-Classic. __R Sent from my BlackBerry 10 smartphone. Original Message From: Frederic Crozat Sent: Monday, 16 November 2015 08:52 To: KRONSEDER, Thomas, Dr. Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] SLE-Classic et. al. Le lundi 16 novembre 2015 ? 07:39 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hello, > > regarding: > > > > We do have quite a number of modules now that you can add into > > > the > > > mix, would it be very hard to have a KDE module so that one could > > > have a DM of ones own choice ? > > > I think some announcements at SUSECon this week might help with > > that > > (hint, hint ;) > > Do you have a pointer to the respective announcement(s) ? I don't have any pointer but this was about SUSE Package Hub (so far, there is very few documentation available at https://en.opensuse.org/Portal:Backports ;) KDE 5 will be available there soon, but unsupported. I'm expecting broader announcement on Package hub soon but I don't have any ETA. -- Frederic Crozat Enterprise Desktop Release Manager 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 thomas.kronseder at mtu.de Mon Nov 16 01:20:18 2015 From: thomas.kronseder at mtu.de (KRONSEDER, Thomas, Dr.) Date: Mon, 16 Nov 2015 08:20:18 +0000 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <1447660330.5052.13.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> Message-ID: <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> Hi Frederik, thank you for this update. So there is going to be some "optional" package update announcement on the package notification mailing list, isn't it? Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: Frederic Crozat [mailto:fcrozat at suse.com] Gesendet: Montag, 16. November 2015 08:52 An: KRONSEDER, Thomas, Dr. Cc: sles-beta at lists.suse.com Betreff: Re: AW: [sles-beta] SLE-Classic et. al. Le lundi 16 novembre 2015 ? 07:39 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hello, > > regarding: > > > > We do have quite a number of modules now that you can add into > > > the > > > mix, would it be very hard to have a KDE module so that one could > > > have a DM of ones own choice ? > > > I think some announcements at SUSECon this week might help with > > that > > (hint, hint ;) > > Do you have a pointer to the respective announcement(s) ? I don't have any pointer but this was about SUSE Package Hub (so far, there is very few documentation available at https://en.opensuse.org/Portal:Backports ;) KDE 5 will be available there soon, but unsupported. I'm expecting broader announcement on Package hub soon but I don't have any ETA. -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From fcrozat at suse.com Mon Nov 16 01:34:08 2015 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 16 Nov 2015 09:34:08 +0100 Subject: [sles-beta] SLE-Classic et. al. In-Reply-To: <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> References: <46AC8C81C10B8C48820201DF2AE1D76DF0C56AB4@hqmbx6.eur.ad.sag> <1446455675.3706.8.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC56281@memc023.de.mtu.corp> <1447660330.5052.13.camel@suse.com> <01559031EB071C47AA06542D982B9CD59AC5633B@memc023.de.mtu.corp> Message-ID: <1447662848.5052.15.camel@suse.com> Le lundi 16 novembre 2015 ? 08:20 +0000, KRONSEDER, Thomas, Dr. a ?crit : > Hi Frederik, > > thank you for this update. > So there is going to be some "optional" package update announcement > on the package notification mailing list, isn't it? I don't have all the details but at least, SUSE Package Hub, once opened, will be available as Add-on, after you register SLE12 system, at install time or after installation (similar to SDK, for instance). I'm not sure there will be individual announcement for each package entering the Hub. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From vmoutoussamy at suse.com Mon Nov 16 08:50:17 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 16 Nov 2015 16:50:17 +0100 Subject: [sles-beta] LVM startup issues... In-Reply-To: <20151109182528.5374037.71371.16399@softwareag.com> References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> Message-ID: Hi, bsc#934965 was resolved in RC1. @Joel could you confirm the status of your issue? Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 09 Nov 2015, at 19:25, Waite, Dick (External) wrote: > > 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 > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From Joel.Barbieri at merge.com Mon Nov 16 09:06:22 2015 From: Joel.Barbieri at merge.com (Joel Barbieri) Date: Mon, 16 Nov 2015 16:06:22 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> Message-ID: I will check the status of this issue with a fresh build and post status later today. Thanks, -Joel -----Original Message----- From: Vincent Moutoussamy [mailto:vmoutoussamy at suse.com] Sent: Monday, November 16, 2015 9:50 AM To: Waite, Dick (External) Cc: Joel Barbieri ; sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Hi, bsc#934965 was resolved in RC1. @Joel could you confirm the status of your issue? Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 09 Nov 2015, at 19:25, Waite, Dick (External) wrote: > > 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 > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From Joel.Barbieri at merge.com Mon Nov 16 10:17:13 2015 From: Joel.Barbieri at merge.com (Joel Barbieri) Date: Mon, 16 Nov 2015 17:17:13 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> Message-ID: I am still having this issue with a fresh build based on RC3. So I don't know if that is a re-open of an SR, an new SR, or how it should be handled. I can probably share the custom ISO we create to assist troubleshooting, or the yast profile, or whatnot. The boot time message is... [ TIME ] Timed out waiting for device dev-vg00-lv_emageon.device. [DEPEND] Dependency failed for /opt/emageon. [DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for Postfix Mail Transport Agent. OK...don't understand why Postfix has a message on this, but, it is there... Disk layout is... /dev/sda1 /boot/efi 156M /dev/sda2 / 4G /dev/sda3 [swap] 4G /dev/sda4 /usr 8G /dev/sda5 /tmp 2G /dev/sda6 /var 4G /dev/sda7 /opt 16G /dev/sda8 LVM vg00, contains lv_emageon at 8G [initial]... All filesystems are xfs, except for /boot/efi which is a DOS variant as required. We use by name. I would argue it is still nicer. Humans don't deal well with UUIDs, though I would consider using them in a SAN environment, but would probably still utilize the bindings file from mpath. -Joel -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Joel Barbieri Sent: Monday, November 16, 2015 10:06 AM To: Vincent Moutoussamy ; Waite, Dick (External) Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... I will check the status of this issue with a fresh build and post status later today. Thanks, -Joel -----Original Message----- From: Vincent Moutoussamy [mailto:vmoutoussamy at suse.com] Sent: Monday, November 16, 2015 9:50 AM To: Waite, Dick (External) Cc: Joel Barbieri ; sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Hi, bsc#934965 was resolved in RC1. @Joel could you confirm the status of your issue? Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 09 Nov 2015, at 19:25, Waite, Dick (External) wrote: > > 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 > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From vmoutoussamy at suse.com Tue Nov 17 06:11:32 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 17 Nov 2015 14:11:32 +0100 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> Message-ID: <18C0873E-5B85-44AF-B4E4-8AA211722052@suse.com> Hi, > > On 16 Nov 2015, at 18:17, Joel Barbieri wrote: > > > I am still having this issue with a fresh build based on RC3. > > So I don't know if that is a re-open of an SR, an new SR, or how it should be handled. > > I can probably share the custom ISO we create to assist troubleshooting, or the yast profile, or whatnot. > Ah, could you remind me the SR number please? I will check the status of this issue. If your SR has been closed the issue should be fixed, but targeted for the GMC. Btw do not hesitate to share the technical details here on the mailing list and not just on the scc support page, this way more eyes (beta testers and SUSE employees) could try to reproduce your issue. > The boot time message is... > > [ TIME ] Timed out waiting for device dev-vg00-lv_emageon.device. > [DEPEND] Dependency failed for /opt/emageon. > [DEPEND] Dependency failed for Local File Systems. > [DEPEND] Dependency failed for Postfix Mail Transport Agent. > > OK...don't understand why Postfix has a message on this, but, it is there... > > Disk layout is... > /dev/sda1 /boot/efi 156M > /dev/sda2 / 4G > /dev/sda3 [swap] 4G > /dev/sda4 /usr 8G > /dev/sda5 /tmp 2G > /dev/sda6 /var 4G > /dev/sda7 /opt 16G > /dev/sda8 LVM vg00, contains lv_emageon at 8G [initial]... > > All filesystems are xfs, except for /boot/efi which is a DOS variant as required. > > We use by name. I would argue it is still nicer. Humans don't deal well with UUIDs, though I would consider using them in a SAN environment, but would probably still utilize the bindings file from path. > -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From Joel.Barbieri at merge.com Tue Nov 17 07:51:53 2015 From: Joel.Barbieri at merge.com (Joel Barbieri) Date: Tue, 17 Nov 2015 14:51:53 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: <18C0873E-5B85-44AF-B4E4-8AA211722052@suse.com> References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> , <18C0873E-5B85-44AF-B4E4-8AA211722052@suse.com> Message-ID: I have not opened one, but Dick noted... ... 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 ... -Joel ________________________________________ From: Vincent Moutoussamy Sent: Tuesday, November 17, 2015 7:11 AM To: Joel Barbieri Cc: Waite, Dick (External); sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Hi, > > On 16 Nov 2015, at 18:17, Joel Barbieri wrote: > > > I am still having this issue with a fresh build based on RC3. > > So I don't know if that is a re-open of an SR, an new SR, or how it should be handled. > > I can probably share the custom ISO we create to assist troubleshooting, or the yast profile, or whatnot. > Ah, could you remind me the SR number please? I will check the status of this issue. If your SR has been closed the issue should be fixed, but targeted for the GMC. Btw do not hesitate to share the technical details here on the mailing list and not just on the scc support page, this way more eyes (beta testers and SUSE employees) could try to reproduce your issue. > The boot time message is... > > [ TIME ] Timed out waiting for device dev-vg00-lv_emageon.device. > [DEPEND] Dependency failed for /opt/emageon. > [DEPEND] Dependency failed for Local File Systems. > [DEPEND] Dependency failed for Postfix Mail Transport Agent. > > OK...don't understand why Postfix has a message on this, but, it is there... > > Disk layout is... > /dev/sda1 /boot/efi 156M > /dev/sda2 / 4G > /dev/sda3 [swap] 4G > /dev/sda4 /usr 8G > /dev/sda5 /tmp 2G > /dev/sda6 /var 4G > /dev/sda7 /opt 16G > /dev/sda8 LVM vg00, contains lv_emageon at 8G [initial]... > > All filesystems are xfs, except for /boot/efi which is a DOS variant as required. > > We use by name. I would argue it is still nicer. Humans don't deal well with UUIDs, though I would consider using them in a SAN environment, but would probably still utilize the bindings file from path. > -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From vmoutoussamy at suse.com Tue Nov 17 09:34:01 2015 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 17 Nov 2015 17:34:01 +0100 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> <18C0873E-5B85-44AF-B4E4-8AA211722052@suse.com> Message-ID: <63059EE0-FEDE-47B3-8984-6119B2FDA5EE@suse.com> Hi, > On 17 Nov 2015, at 15:51, Joel Barbieri wrote: > > > I have not opened one, but Dick noted... > > ... > 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 > ... > > -Joel > Please create a SR for your issue because this is not linked to bsc#945095. Please provide the autoyast file used, and any useful information (refer to https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.bootproblem). It would be also interesting to get a supportconfig of a freshly SLES12SP0 installed with the same autoyast file. Finally, please post the number and the content of your SR on this thread, this will allow other to take a look at the issue. Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager From Joel.Barbieri at merge.com Tue Nov 17 10:07:36 2015 From: Joel.Barbieri at merge.com (Joel Barbieri) Date: Tue, 17 Nov 2015 17:07:36 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: <63059EE0-FEDE-47B3-8984-6119B2FDA5EE@suse.com> References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> <18C0873E-5B85-44AF-B4E4-8AA211722052@suse.com> <63059EE0-FEDE-47B3-8984-6119B2FDA5EE@suse.com> Message-ID: Service Request: 10979088921 created re: LVM startup issues. Systemd is failing to start [timing out] the LVM device on initial [and any other] boot cycle for our autoyast profile which only ever gets minor tweaks from OS version to OS version. We utilize by name and autoyast successfully creates all filesystems, but cannot start the LVM it created on boot. By Name is utilized for all partitions, GPT for EFI. /dev/sda1 150M /boot/efi [fat] /dev/sda2 4G / [xfs] /dev/sda3 4G swap /dev/sda4 8G /usr [xfs] /dev/sda5 2G /tmp [xfs] /dev/sda6 4G /var [xfs] /dev/sda7 16G /opt [xfs] /dev/sda8 MAX [lvm - vg00] /dev/vg00/lv_emageon 8G [initial size] [xfs] Autoyast profile and pattern included. We roll our own OS to shrink the size and exclude any unnecessary rpm for our product. -Joel -----Original Message----- From: Vincent Moutoussamy [mailto:vmoutoussamy at suse.com] Sent: Tuesday, November 17, 2015 10:34 AM To: Joel Barbieri Cc: Waite, Dick (External) ; sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Hi, > On 17 Nov 2015, at 15:51, Joel Barbieri wrote: > > > I have not opened one, but Dick noted... > > ... > 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 > ... > > -Joel > Please create a SR for your issue because this is not linked to bsc#945095. Please provide the autoyast file used, and any useful information (refer to https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.bootproblem). It would be also interesting to get a supportconfig of a freshly SLES12SP0 installed with the same autoyast file. Finally, please post the number and the content of your SR on this thread, this will allow other to take a look at the issue. Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- A non-text attachment was scrubbed... Name: base12lvm-efi.xml Type: application/xml Size: 9433 bytes Desc: base12lvm-efi.xml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: emgsles12-12.1-0.x86_64.pat Type: application/octet-stream Size: 4623 bytes Desc: emgsles12-12.1-0.x86_64.pat URL: From Dick.Waite at softwareag.com Tue Nov 17 23:45:36 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Wed, 18 Nov 2015 06:45:36 +0000 Subject: [sles-beta] LVM startup issues... In-Reply-To: References: <20151109180704.5374037.62132.16395@softwareag.com> <20151109182528.5374037.71371.16399@softwareag.com> <18C0873E-5B85-44AF-B4E4-8AA211722052@suse.com> <63059EE0-FEDE-47B3-8984-6119B2FDA5EE@suse.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0C5E113@hqmbx6.eur.ad.sag> Grand New Day, This does sound very much like the issues I had with Beta2 and 3. I have done quite a lot of work with RC2 and 3 and do not see any issues with LVM, on my VMware Workstations. I'm at an IBM pitch at SAP today, but will run some updates from Beta2 systems to RC3 later this evening. __R -----Original Message----- From: Joel Barbieri [mailto:Joel.Barbieri at merge.com] Sent: Dienstag, 17. November 2015 18:08 To: Vincent Moutoussamy Cc: Waite, Dick (External); sles-beta at lists.suse.com Subject: RE: [sles-beta] LVM startup issues... Service Request: 10979088921 created re: LVM startup issues. Systemd is failing to start [timing out] the LVM device on initial [and any other] boot cycle for our autoyast profile which only ever gets minor tweaks from OS version to OS version. We utilize by name and autoyast successfully creates all filesystems, but cannot start the LVM it created on boot. By Name is utilized for all partitions, GPT for EFI. /dev/sda1 150M /boot/efi [fat] /dev/sda2 4G / [xfs] /dev/sda3 4G swap /dev/sda4 8G /usr [xfs] /dev/sda5 2G /tmp [xfs] /dev/sda6 4G /var [xfs] /dev/sda7 16G /opt [xfs] /dev/sda8 MAX [lvm - vg00] /dev/vg00/lv_emageon 8G [initial size] [xfs] Autoyast profile and pattern included. We roll our own OS to shrink the size and exclude any unnecessary rpm for our product. -Joel -----Original Message----- From: Vincent Moutoussamy [mailto:vmoutoussamy at suse.com] Sent: Tuesday, November 17, 2015 10:34 AM To: Joel Barbieri Cc: Waite, Dick (External) ; sles-beta at lists.suse.com Subject: Re: [sles-beta] LVM startup issues... Hi, > On 17 Nov 2015, at 15:51, Joel Barbieri wrote: > > > I have not opened one, but Dick noted... > > ... > 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 > ... > > -Joel > Please create a SR for your issue because this is not linked to bsc#945095. Please provide the autoyast file used, and any useful information (refer to https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.bootproblem). It would be also interesting to get a supportconfig of a freshly SLES12SP0 installed with the same autoyast file. Finally, please post the number and the content of your SR on this thread, this will allow other to take a look at the issue. Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From behlert at suse.com Wed Nov 18 05:07:15 2015 From: behlert at suse.com (Stefan Behlert) Date: Wed, 18 Nov 2015 13:07:15 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 12 SP1 GMC is available Message-ID: <20151118120715.GG5433@suse.de> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! SUSE CONFIDENTIAL !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Dear Beta participants, we are proud to announce the release of SUSE Linux Enterprise Server 12 SP1 GMC. (Goldmaster Candidate) ISO images are now available for download now. Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. Note that the directory contains the images for the SDK, too. 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. There's one issue that we are aware of with the SLES 12 SP1 GMC images, which is - In some cases, autoyast installation on IBM z Systems requires a reboot before bringing up the installed system. This can be achieved manually, or by setting the final_reboot flag in the general section of the autoyast profile[1,2]. This is being investigated by the development team, but we decided to not delay the GMC for it, in order to make the best use of testing schedules. [1] http://docserv.suse.de/documents/SLES12/SLES-autoyast/html/configuration.html#CreateProfile.General [2] See [bsc#944349] for a description of the issue Thanks for all your testing, 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) From eblock at nde.ag Wed Nov 18 08:00:35 2015 From: eblock at nde.ag (Eugen Block) Date: Wed, 18 Nov 2015 16:00:35 +0100 Subject: [sles-beta] Admin Server fails to boot on Xen In-Reply-To: <0160FB5D-0C9C-4466-A15F-0EB94CCDF181@suse.com> References: <20151027101234.Horde.5bokP7GFHu9lZxZJCktEGTj@www3.nde.ag> <20151028130231.Horde.fJy3TolBNiIJY1fW14oOsRS@www3.nde.ag> <8E800E0D470C1D4EAA87923CF0D8D62401521562B7@MPWMEX1.africanbank.net> <20151028175145.Horde.LVZMym1qpdCx_Ve2dphQ3is@www3.nde.ag> <3EDE946F-165A-4AAB-A8C5-260A0C8F4F4B@vmware.com> <8E800E0D470C1D4EAA87923CF0D8D6240152158F6C@MPWMEX1.africanbank.net> <20151029090040.Horde.dFxHcbFWSw0Y0LsDj2fKFZO@www3.nde.ag> <5867BA4F-9CAF-40EF-8C55-6382270CEA6A@suse.com> <20151029124615.Horde.nfSqg3meS6TyHGKpuQMxmpI@www3.nde.ag> <20151103212138.Horde.XsUdIZazVU0LkkLn7gEJ8Y1@www3.nde.ag> <0160FB5D-0C9C-4466-A15F-0EB94CCDF181@suse.com> Message-ID: <20151118160035.Horde.mT7fbGYsxHpxJqj9_hpHxkF@www3.nde.ag> Hi, I wanted to report that my issue has been resolved. We use NPIV as storage backend for the xen guests, that seems to have caused the grub failure. I don't know the details what had to be changed, so that's all I can tell. There will be a patch available in a couple of weeks. Regards, Eugen Zitat von Vincent Moutoussamy : > Hi beta testers, > > For your information, we are not able to reproduce both issues > internally but we are still analysing > Eugen?s supportconfigs to find the root causes. > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > > > >> On 03 Nov 2015, at 21:21, Eugen Block wrote: >> >> Just wanted to let you know that I'll be out of office for the rest >> of the week. I'll be back on Monday. >> >> Regards, >> Eugen >> >> Zitat von Eugen Block : >> >>> Alright,I have filed two SRs: >>> >>> - SR#10976589831: SLES12-SP1 fails to boot on Xen host (default >>> partitioning) >>> - SR#10976588861: SLES12-SP1 fails to boot on Xen host (/boot on ext4) >>> >>> Regards, >>> Eugen >>> >>> >>> Zitat von Vincent Moutoussamy : >>> >>>> Hi, >>>> >>>>> On 29 Oct 2015, at 09:00, Eugen Block wrote: >>>>> >>>>> Hi Wesley, >>>>> >>>>>> @Eugene, Does the reboot fail on the first reboot, even with >>>>>> the kernel installed? >>>>> >>>>> that is correct. It's the first reboot during installation >>>>> process. I checked the file systems before the reboot and the >>>>> kernel was installed. So I guess I'll follow up on Mike's >>>>> suggestion and file a SR. >>>>> >>>> Yes, please open the 2 SRs as suggested and post the SRs number >>>> on this thread for reference. >>>> This will allow us to track the issue more easily. >>>> >>>> Thanks, >>>> >>>> Regards, >>>> -- >>>> Vincent Moutoussamy >>>> SUSE Beta Program and SDK Project Manager >>> >>> >>> >>> -- >>> Eugen Block voice : +49-40-559 51 75 >>> NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 >>> Postfach 61 03 15 >>> D-22423 Hamburg e-mail : eblock at nde.ag >>> >>> Vorsitzende des Aufsichtsrates: Angelika Mozdzen >>> Sitz und Registergericht: Hamburg, HRB 90934 >>> Vorstand: Jens-U. Mozdzen >>> USt-IdNr. DE 814 013 983 >>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta >> >> >> >> -- >> Eugen Block voice : +49-40-559 51 75 >> NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 >> Postfach 61 03 15 >> D-22423 Hamburg e-mail : eblock at nde.ag >> >> Vorsitzende des Aufsichtsrates: Angelika Mozdzen >> Sitz und Registergericht: Hamburg, HRB 90934 >> Vorstand: Jens-U. Mozdzen >> USt-IdNr. DE 814 013 983 >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta -- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock at nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 From Dick.Waite at softwareag.com Thu Nov 19 06:39:20 2015 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Thu, 19 Nov 2015 13:39:20 +0000 Subject: [sles-beta] Status of SLE 12 SP1 GMC In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DF0C5C917@hqmbx6.eur.ad.sag> References: <20151113150230.GL11936@suse.de> <46AC8C81C10B8C48820201DF2AE1D76DF0C5C666@hqmbx6.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76DF0C5C917@hqmbx6.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DF0C5E8A7@hqmbx6.eur.ad.sag> Grand New Day, A SLES12-SP0 s390x system has been updated to SLES12-SP1 GMC status. This does use zFCP and has a LVM based file store. I have not run a full IVP but it's held it's own while we had lunch... __R -----Original Message----- From: Waite, Dick (External) Sent: Montag, 16. November 2015 21:18 To: 'Stefan Behlert' Cc: 'Gary Ernst'; 'Vincent Moutoussamy (vmoutoussamy at suse.com)' Subject: RE: [sles-beta] Status of SLE 12 SP1 GMC Evening All, I tried to see if SR10971994271 had ben fixed and tested, but I'm not allowed. As Gary is OoO until 7th December can we be sure to be sure this is fixed. I'd like to have some warm words that this zFCP issue is fixed. Running an update to find you have to then run the back-up to get your system back at GMC time is not good. __R -----Original Message----- From: Waite, Dick (External) Sent: Montag, 16. November 2015 11:51 To: 'Stefan Behlert' Cc: 'Gary Ernst'; Vincent Moutoussamy (vmoutoussamy at suse.com) Subject: RE: [sles-beta] Status of SLE 12 SP1 GMC Grand New Day, The issue Gary reported on the s390x systems, this is fixed in the GMC we get tomorrow? As SAG also use zFCP I have not done an install yet on s390x. So we have quite a lot of catching up to do before GA.... It would have been grand if this could have made the extra RC3 __R From Gary on the 19th October I reported shortly before the release of SLES12-SP1-RC That YaST was not able to configure ZFCP devices. (SR# 10971994271) While I understand that it was reported to close to the RC1 release and that only "show stoppers" would be addressed, It has not been addressed in RC2. This is most definitely a show stopper. From Vincent on the 20th October. We are still working on this issue, in fact the bug report (bsc#947181) related to your SR#10971994271 has been marked as duplicated of bsc#928574. So this mean that you are not the only one reporting this, and we are taking care of this important issue! -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Stefan Behlert Sent: Freitag, 13. November 2015 16:03 To: sled-beta at lists.suse.com; sleha-beta at lists.suse.com; sles-beta at lists.suse.com Subject: [sles-beta] Status of SLE 12 SP1 GMC 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) _______________________________________________ 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