From vmoutoussamy at suse.com  Thu Mar  1 08:09:10 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Thu, 1 Mar 2018 16:09:10 +0100
Subject: [sle-beta] postfix fails to start
In-Reply-To: <cb69d9fd-44e4-4f14-1150-7c346d114fc7@b1-systems.de>
References: <cb69d9fd-44e4-4f14-1150-7c346d114fc7@b1-systems.de>
Message-ID: <2C63BA87-BEC0-45E0-AD5E-823475A0AA93@suse.com>

Hi,

Could you please create a dedicated SLES 15 Bug for this?
You will find the links here: https://www.suse.com/betaprogram/sle-beta/#bugzilla
And please do not hesitate to be a little bit more verbose ; )

In an ideal world, one bug and fix against openSUSE LEAP leads to one bug and
fix against SLES.
But we really want to track SLE 15 bugs separately for tracking purpose
especially since we are approaching the RC phase and also to make sure that we
can provide any fixes asap and not waiting for the fixes to be applied by an
indirect or direct sync between openSUSE and SLE.

Have a nice day,

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 28 Feb 2018, at 17:53, Eike Waldt <waldt at b1-systems.de> wrote:
> 
> Hi there,
> 
> there is an open bug for postfix which we encountered today also on
> SLES15 beta7.
> 
> https://bugzilla.suse.com/show_bug.cgi?id=1063679
> 
> Please fix it ;)
> 
> Cheers,
> 
> --
> Eike Waldt
> Linux Consultant & Trainer
> Tel.: +49-175-7241189
> Mail: waldt at b1-systems.de
> 
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180301/72899afe/attachment.sig>

From okurz at suse.de  Thu Mar  1 13:38:45 2018
From: okurz at suse.de (Oliver Kurz)
Date: Thu, 01 Mar 2018 21:38:45 +0100
Subject: [sle-beta] Desktop Tools module required by Development-Tools
	module?
In-Reply-To: <414038067.4519389.1519936539611.JavaMail.zimbra@tre-sc.jus.br>
References: <414038067.4519389.1519936539611.JavaMail.zimbra@tre-sc.jus.br>
Message-ID: <138193430.ReW8WXXdBG@linux-28d6.suse>

Hello,

On Thursday, 1 March 2018 21:35:39 CET Luiz Angelo Daros de Luca wrote:
> Hello,
> 
> During installation, I choose to install development tools module (for git).
> However, this module requires product(sle-module-desktop-applications). Is
> it really necessary?
> 
> I didn't expect to need to install desktop application in order to simply
> build some apps or only to use git for conf management.

Yes, the development module depends on the desktop-applications module. This 
does not mean that one needs to install any other packages from this module 
except for the dependencies.

Regards,
Oliver

From okurz at suse.de  Thu Mar  1 23:51:32 2018
From: okurz at suse.de (Oliver Kurz)
Date: Fri, 02 Mar 2018 07:51:32 +0100
Subject: [sle-beta] Need rpm-build package for SLES15 Beta 7
In-Reply-To: <b32c713e0aa14c5382e82854167cfa17@EXUSDAGORL02.INTERNAL.ROOT.TES>
References: <b32c713e0aa14c5382e82854167cfa17@EXUSDAGORL02.INTERNAL.ROOT.TES>
Message-ID: <3770385.uor3VPOxPF@linux-28d6.suse>

Hi,

On Friday, 2 March 2018 06:45:32 CET Bong Koo wrote:
> Hi,
> 
> I am testing SLES 15 Beta 7, and found that 'rpmbuild' utility is missing.
> I have checked the released ISO files, but no luck so far.
> Can you let me know where / how I can get it ?
> Or, forward this email to the right people, please.
> 
> PS: I have installed SUSE Linux Enterprise Server.

One can use
https://scc.suse.com/packages
to find out how and where to find packages.
The utility "rpmbuild" is part of the package "rpm-build" which is included in 
the module "Development Tools". So please add this module to your system to 
get access to rpmbuild.

Regards,
Oliver

From vmoutoussamy at suse.com  Fri Mar  2 03:29:32 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Fri, 2 Mar 2018 11:29:32 +0100
Subject: [sle-beta] Desktop Tools module required by Development-Tools
 module?
In-Reply-To: <414038067.4519389.1519936539611.JavaMail.zimbra@tre-sc.jus.br>
References: <414038067.4519389.1519936539611.JavaMail.zimbra@tre-sc.jus.br>
Message-ID: <7E268911-10AE-430A-9097-ED542DF83B57@suse.com>

Hi,

Well the "Development Tools module" contains more than just the usual toolchain
components (gcc, etc) there is gnome-builder for instance for an obvious
development tool with desktop dependencies.

And like Oliver said, the enablement of "Desktop Applications module? when
enabling the ?Development Tools module" is done to avoid potential dependency
issues. It doesn?t mean it will install Desktop Applications without your
approval, it will only retrieve the necessary packages/dependencies if your
install a DevTools that has this requirement.

Have a nice day,

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 1 Mar 2018, at 21:35, Luiz Angelo Daros de Luca <luizluca at tre-sc.jus.br> wrote:
> 
> Hello,
> 
> During installation, I choose to install development tools module (for git). However, this module requires product(sle-module-desktop-applications).
> Is it really necessary?
> 
> I didn't expect to need to install desktop application in order to simply build some apps or only to use git for conf management.
> 
> Regards,
> 
> --
> Luiz Angelo Daros de Luca
> Tribunal Regional Eleitoral de Santa Catarina
> STI/CSIT/Se??o de Comunica??o de Dados
> e-mail: luizluca at tre-sc.jus.br
> jabber: luizluca at tre-sc.gov.br
> fone: +55 48 3251-7458
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180302/03ba3742/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180302/03ba3742/attachment.sig>

From eckert at b1-systems.de  Thu Mar  1 08:26:26 2018
From: eckert at b1-systems.de (Michael Eckert)
Date: Thu, 1 Mar 2018 16:26:26 +0100
Subject: [sle-beta] postfix fails to start
In-Reply-To: <2C63BA87-BEC0-45E0-AD5E-823475A0AA93@suse.com>
References: <cb69d9fd-44e4-4f14-1150-7c346d114fc7@b1-systems.de>
	<2C63BA87-BEC0-45E0-AD5E-823475A0AA93@suse.com>
Message-ID: <af101d36-cf50-4ed2-d063-1acd194388bc@b1-systems.de>

Hello Vincent,

I have created another one regarding this case:
https://bugzilla.suse.com/show_bug.cgi?id=1083536

All best,

Michael

On 03/01/2018 04:09 PM, Vincent Moutoussamy wrote:
> Hi,
> 
> Could you please create a dedicated SLES 15 Bug for this?
> You will find the links here: https://www.suse.com/betaprogram/sle-beta/#bugzilla
> And please do not hesitate to be a little bit more verbose ; )
> 
> In an ideal world, one bug and fix against openSUSE LEAP leads to one bug and
> fix against SLES.
> But we really want to track SLE 15 bugs separately for tracking purpose
> especially since we are approaching the RC phase and also to make sure that we
> can provide any fixes asap and not waiting for the fixes to be applied by an
> indirect or direct sync between openSUSE and SLE.
> 
> Have a nice day,
> 
> Regards,
> --
> Vincent Moutoussamy
> SUSE Beta Program and SDK Project Manager
> 
>> On 28 Feb 2018, at 17:53, Eike Waldt <waldt at b1-systems.de> wrote:
>>
>> Hi there,
>>
>> there is an open bug for postfix which we encountered today also on
>> SLES15 beta7.
>>
>> https://bugzilla.suse.com/show_bug.cgi?id=1063679
>>
>> Please fix it ;)
>>
>> Cheers,
>>
>> --
>> Eike Waldt
>> Linux Consultant & Trainer
>> Tel.: +49-175-7241189
>> Mail: waldt at b1-systems.de
>>
>> B1 Systems GmbH
>> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>>
>> _______________________________________________
>> sle-beta mailing list
>> sle-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/sle-beta
> 

-- 
Michael Eckert
Linux Consultant & Developer
Tel.: +49-151-61 959 727
Mail: eckert at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180301/83a72644/attachment.sig>

From Dick.Waite at softwareag.com  Tue Mar  6 03:06:44 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Tue, 6 Mar 2018 10:06:44 +0000
Subject: [sle-beta] When Migrating from SLES12 to SLES15 ....
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076B72D@daeexmbx1.eur.ad.sag>

It would be a grand time to be able to amend the file system layout... Maybe amend a LVM layout, one can do this at New Install time, could this also be offered at Migration time, or a subset ????

Regards,

__R

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180306/676e809f/attachment.htm>

From kukuk at suse.de  Tue Mar  6 04:50:59 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Tue, 6 Mar 2018 12:50:59 +0100
Subject: [sle-beta] When Migrating from SLES12 to SLES15 ....
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076B72D@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076B72D@daeexmbx1.eur.ad.sag>
Message-ID: <20180306115059.GA20598@suse.de>

On Tue, Mar 06, Waite, Dick (External) wrote:

> It would be a grand time to be able to amend the file system layout... Maybe
> amend a LVM layout, one can do this at New Install time, could this also be
> offered at Migration time, or a subset ????

Changing the filesystem layout or the underlaying technology (LVM,
softraid, ...) is not possible during migration, you would need to
create a full backup and restore. And even then this will most likely
not work, since a lot of tools configure itself during installation
depending on the setup, you need to find all of them and reconfigure
them.
So a fresh installation is really much faster.

  Thorsten


-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From Dick.Waite at softwareag.com  Tue Mar  6 10:26:55 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Tue, 6 Mar 2018 17:26:55 +0000
Subject: [sle-beta] When Migrating from SLES12 to SLES15 ....
In-Reply-To: <20180306115059.GA20598@suse.de>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076B72D@daeexmbx1.eur.ad.sag>,
	<20180306115059.GA20598@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076C9F2@daeexmbx1.eur.ad.sag>

I was thinking of the amends one can do if the system is not mounted, which are quite helpful. Agreed one does not want to be running backup-reload in a migration, but while the LVM's are not mounted there are a number of operations one can do which might be handy in the SLES15 configuration. Agreed one can use a "rescue" environment and do much the same, but while you have a working environment running the migration, why not take advantage....

"So a fresh installation is really much faster." This may be true for the OS but it might take a few weeks to install and configure all the applications needed to make this a working system.  I was thinking you could add some disks and add them into the LVM and configure them. In a new install there are grand tools accessible during the install, which I would image are also available in a migration. Again you could do this in a service slot, but if it's there in the migration it's a nice bonus point... One up on the Red team.

__R
________________________________________
From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
Sent: 06 March 2018 12:50
To: sle-beta at lists.suse.com
Subject: Re: [sle-beta] When Migrating from SLES12 to SLES15 ....

On Tue, Mar 06, Waite, Dick (External) wrote:

> It would be a grand time to be able to amend the file system layout... Maybe
> amend a LVM layout, one can do this at New Install time, could this also be
> offered at Migration time, or a subset ????

Changing the filesystem layout or the underlaying technology (LVM,
softraid, ...) is not possible during migration, you would need to
create a full backup and restore. And even then this will most likely
not work, since a lot of tools configure itself during installation
depending on the setup, you need to find all of them and reconfigure
them.
So a fresh installation is really much faster.

  Thorsten


--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From beta-programs at lists.suse.com  Wed Mar  7 04:14:38 2018
From: beta-programs at lists.suse.com (SUSE Beta Program)
Date: Wed, 07 Mar 2018 12:14:38 +0100
Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 Release Candidate 1
	is out!
Message-ID: <5a9fc99e34735_5b2a4c531079a1@boucane.mail>

Here it comes! Release Candidate 1 of SUSE Linux Enterprise 15:
  SUSE Linux Enterprise Server (SLES),
  SUSE Linux Enterprise Just Enough Operating System(JeOS),
  SUSE Linux Enterprise Desktop (SLED),
  SUSE Linux Enterprise High Availability (SLE-HA),
  and SUSE Linux Enterprise Workstation Extension (SLE-WE)

Download[1]

== Important Notice
=Packages DVD
When using Packages DVD to install SLE modules, please make sure to also add the 
Product repository you are installing (SLES / SLED / HA / ...) from Packages DVD.
Not doing so might result in missing system roles during installation.

=Notable changes
- Migration from SLE 12 to SLE 15:
Here are the supported Migration scenarios from SLE 12 to SLE 15. 
  - Offline migration:
    By using SLE-15-Installer and SLE-15-Packages isos manually. Boot on the 
    SLE-15-Installer, then select and follow the "Upgrade" wizard. Make sure you add the 
    SLE-15-Packages DVD as the source for the SLE 15 
    Modules.    
  - Online migration:
    By using a SLE 15 Beta Registration Code[2] on a SLE 12 instance and booting
    on the SLE-15-Installer. Then select and follow the "Upgrade" wizard. Make
    sure your network setting is done so the SLE-15-Installer will be able to
    contact our SCC or your SMT/SUSE Manager as source for the SLE 15 Modules. 
- SLES 15 JeOS images are now available for download and testing!
- The Desktop Productivity Module has been replaced by the SLE Workstation 
Extension. This will only be an issue if you do an upgrade from a former Beta 
installation (which is an unsupported scenario[3]).
- The HA Module and HA Product have been combined to one HA Product which will 
be available for the various products where it's eligible. Reason for the
changes with those two modules is that we want to simplify the universe.
- yast2-ca-management is no longer provided (FATE#319119).
- OpenSSL 1.0 is no longer installed by default, all packages have been migrated
to OpenSSL 1.1. OpenSSL 1.0 will be available in Legacy module in the next
milestone.

=Fixed bugs in RC 1 (selection):
- Existing swap partition is handled as ordinary filesystem [Bug 1080926]
- Many YaST components were updated and received a lot of enhancements and 
fixes.
- Packages added (across all modules):
a52dec, alacarte, apache-pdfbox, boost, bzr, cal10n, c-ares, cargo, check, createrepo_c, 
cscope, delayacct-utils, dmraid, FastCGI, fftw3_3_3_6-gnu-openmpi2-hpc, flatpak-builder,
glade, glew, gnustep-base, gstreamer-plugins-ugly, hdf5_1_10_1-gnu-openmpi2-hpc, 
installation-images-SLES_SAP, installation-images-SLES, kiwi-boot-descriptions, libcap1,
libGLw, liboping, libpst, libqt5-qt3d, libqt5-qtquickcontrols2, libqt5-qtsensors,
libqt5-qtwayland, libqt5xdg, libyui-qt-graph, meanwhile, meld, monitoring-plugins,
mpiP_3_4_1-gnu-openmpi2-hpc, netcdf_4_4_1_1-gnu-mvapich2-hpc, 
netcdf_4_4_1_1-gnu-openmpi2-hpc, netcdf-fortran_4_4_4-gnu-openmpi2-hpc, 
openmpi_2_1_2-gnu-hpc, openmpi_2_1_2-gnu-hpc-testsuite, openmpi2, 
petsc_3_8_3-gnu-mpich-hpc, petsc_3_8_3-gnu-mvapich2-hpc, petsc_3_8_3-gnu-openmpi2-hpc,
petsc, pixz, prctl, procinfo, purple-import-empathy, pv, python-kiwi, rust,
scalapack_2_0_2-gnu-openmpi2-hpc, shim, stunnel, tidyp, u-boot, unar, vala, yast2-rmt. 

== More information
SLE Beta Page[4]
Release Notes[5]
Known Issues[6]

  Your SUSE Linux Enterprise Team

== Beta Program
Please refer to our dedicated SLE Beta Program webpage[1] for any general
information. However, do not hesitate to contact us at
beta-programs at lists.suse.com if you have any questions.

You received this email because you're signed up to get updates from us.
Please send an email to beta-programs at lists.suse.com if you want to
unsubscribe.

[1] https://www.suse.com/betaprogram/sle-beta/#download
[2] https://www.suse.com/betaprogram/sle-beta/#faq-reg
[3] https://www.suse.com/betaprogram/sle-beta
[4] https://www.suse.com/betaprogram/sle-beta/#releasenotes
[5] https://www.suse.com/betaprogram/sle-beta/#knownissues
[6] https://www.suse.com/betaprogram/sle-beta/#releases
[7] https://www.suse.com/betaprogram/sle-beta/#faq-update1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180307/42863b14/attachment.htm>

From vmoutoussamy at suse.com  Wed Mar  7 08:19:42 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Wed, 7 Mar 2018 16:19:42 +0100
Subject: [sle-beta] When Migrating from SLES12 to SLES15 ....
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076C9F2@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076B72D@daeexmbx1.eur.ad.sag>
	<20180306115059.GA20598@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D012076C9F2@daeexmbx1.eur.ad.sag>
Message-ID: <B8C0FF64-4C67-4A05-BC5E-5265504176C2@suse.com>

Hi,
> On 6 Mar 2018, at 18:26, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
> 
> I was thinking of the amends one can do if the system is not mounted, which are quite helpful. Agreed one does not want to be running backup-reload in a migration, but while the LVM's are not mounted there are a number of operations one can do which might be handy in the SLES15 configuration. Agreed one can use a "rescue" environment and do much the same, but while you have a working environment running the migration, why not take advantage?.

IMHO, changing the filesystem layout or the underlaying technology of an
existing system is already a big deal on his own. If it?s not just adding a
new disk for new free space, any changes will be significant enough to require
some additional pre-production testing.

> "So a fresh installation is really much faster." This may be true for the OS but it might take a few weeks to install and configure all the applications needed to make this a working system.

By the way we already recommend to do fresh install for Migrating from major
SLE version (like from SLE 11 to SLE 12*), and I?m not aware of any change in
that regard for migrating to SLE 15.

This means that we consider a fresh install to be the best method to put the
major SLE version in production for (not all but) most customers and use cases.
Why? well for various reasons it?s the safer route for you, and it also allow
you to evaluate and make changes if necessary step by step.

>  I was thinking you could add some disks and add them into the LVM and configure them. In a new install there are grand tools accessible during the install, which I would image are also available in a migration. Again you could do this in a service slot, but if it's there in the migration it's a nice bonus point... One up on the Red team.

Well, touching anything related to filesystem or disk put the existing data at
potential risk right? This is not just for SLE but for any OS out there.

So you could see your proposal as a neat new feature but also as a new way to
potentially break things during the migration process.

Regards,

*https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.paths
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> __R
> ________________________________________
> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
> Sent: 06 March 2018 12:50
> To: sle-beta at lists.suse.com
> Subject: Re: [sle-beta] When Migrating from SLES12 to SLES15 ....
> 
> On Tue, Mar 06, Waite, Dick (External) wrote:
> 
>> It would be a grand time to be able to amend the file system layout... Maybe
>> amend a LVM layout, one can do this at New Install time, could this also be
>> offered at Migration time, or a subset ????
> 
> Changing the filesystem layout or the underlaying technology (LVM,
> softraid, ...) is not possible during migration, you would need to
> create a full backup and restore. And even then this will most likely
> not work, since a lot of tools configure itself during installation
> depending on the setup, you need to find all of them and reconfigure
> them.
> So a fresh installation is really much faster.
> 
>  Thorsten
> 
> 
> --
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta
> 
> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180307/51639609/attachment.sig>

From beta-programs at lists.suse.com  Wed Mar  7 09:05:10 2018
From: beta-programs at lists.suse.com (SUSE Beta Program)
Date: Wed, 07 Mar 2018 17:05:10 +0100
Subject: [sle-beta] [ANNOUNCE] SUSE Beta Documentations are available!
Message-ID: <5aa00db6c0679_6691105930c2864f@boucane.mail>

We are proud to announce the availability of our SUSE Beta Documentations!

Being an "open open source company" means that we want to do more than just offering
open source products but also to open our development processes. And this will allow
our users and partners to be involved earlier and deeper than before. 

Thus our SUSE Documentation team did an amazing job on producing and sharing their
draft documentations at https://susedoc.github.io/.

# Important Notice:
"This page contains links to draft builds from the SUSE documentation source
code repositories. These builds are triggered automatically with each commit.
They are work in progress and may contain a mixture of up-to-date and outdated
documentation. Use the documents here at your own risk.

For official documentation refer to https://www.suse.com/documentation (SUSE)
and https://doc.opensuse.org (openSUSE)."

# SLE 15 Product
The SLE 15 Documentations can be found in the "develop" column on
https://susedoc.github.io/ for each SLE Products.

Please be aware that some sections might still be using the latest official
documentation from SLE 12 SP3!

## SLE 15 Upgrade Guide:
We now have a dedicated "Upgrade Guide" for SLES[1] and SLED[2]!

## Report a documentation bug
You will find a "REPORT BUG" link next to each section of our SLE documentation. 
This allow you to create documentation bugs throught our "Public Beta SUSE Linux
Enterprise Bugzilla products"[3].

# Other SUSE Products
At the moment we are focusing more on the SLE documentation, but still other 
SUSE Products documentations are available. 
You won't be able to freely open bug report for the non-SLE products for now!
If you want to report issues or be involved in any other SUSE Products beta
program, please contact us at beta-programs at lists.suse.com. 

Regards,

[1] https://susedoc.github.io/doc-sle/develop/SLES-upgrade/single-html/
[2] https://susedoc.github.io/doc-sle/develop/SLED-upgrade/single-html/
[3] https://www.suse.com/betaprogram/sle-beta/#bugzilla

Your SUSE Linux Enterprise Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180307/9667a91b/attachment.htm>

From tomaz.borstnar at softergee.si  Wed Mar  7 10:32:53 2018
From: tomaz.borstnar at softergee.si (=?UTF-8?B?VG9tYcW+IEJvcsWhdG5hciwgU29mdGVyZ2Vl?=)
Date: Wed, 7 Mar 2018 18:32:53 +0100
Subject: [sle-beta] yast CA module gone in SLE 15?
Message-ID: <e0954297-f6cd-d722-0307-579cd4f55b7f@softergee.si>

Hello!

Why would this useful thing be gone from SLE 15?

Toma?


From vmoutoussamy at suse.com  Thu Mar  8 02:33:19 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Thu, 8 Mar 2018 10:33:19 +0100
Subject: [sle-beta] [Beta-programs] [ANNOUNCE] SUSE Linux Enterprise 15
 Release Candidate 1 is out!
In-Reply-To: <5a9fc99e34735_5b2a4c531079a1@boucane.mail>
References: <5a9fc99e34735_5b2a4c531079a1@boucane.mail>
Message-ID: <2C3BD38A-6148-4CB8-9598-4B8DE109AC20@suse.com>

Hi,

We have received some reports about users facing issue when trying to download
SLE 15 RC1. The typical error message seen is:

> Downloads
> 
> We're sorry, we are unable to complete the download at this time.
> 
> There is no such download build in our system, or it once was but has been removed.

Or some might have even seen ?permission issue?, etc.

Well the workaround for such issue is to delete suse.com and download.suse.com
cookies? These issues are not specific to the beta download but to
download.suse.com.

We are sorry for the inconvenience, we have reported these issues to our web
team.

Have a nice day,
Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 7 Mar 2018, at 12:14, SUSE Beta Program <beta-programs at lists.suse.com> wrote:
> 
> Having trouble viewing this email? Please check the plain text version of it with your mailer.
> 
> 
> 
> 
>  <https://www.suse.com/betaprogram/sle-beta/>
> 
> Here it comes! Release Candidate 1 of SUSE Linux Enterprise 15 for:
> 
> SUSE Linux Enterprise Server (SLES),
> SUSE Linux Enterprise Just Enough Operating System (JeOS),
> SUSE Linux Enterprise Desktop (SLED),
> SUSE Linux Enterprise Workstation Extension (SLE-WE),
> SUSE Linux Enterprise High Availablility (SLE-HA)
> 
> Download ? <https://www.suse.com/betaprogram/sle-beta/#download>
> Important Notice
> Packages DVD
> 
> When using Packages DVD to install SLE modules, please make sure to also add the Product repository you are installing (SLES / SLED / HA / ...) from Packages DVD. Not doing so might result in missing system roles during installation.
> 
> Migration from SLE 12 to SLE 15
> 
> Offline migration:
> By using SLE-15-Installer and SLE-15-Packages isos manually. Boot on the SLE-15-Installer, then select and follow the "Upgrade" wizard. Make sure you add the SLE-15-Packages DVD as the source for the SLE 15 Modules.
> 
> Online migration:
> By using a SLE 15 Beta Registration Code <https://www.suse.com/betaprogram/sle-beta/#faq-reg> on a SLE 12 instance and booting on the SLE-15-Installer. Then select and follow the "Upgrade" wizard. Make sure your network setting is done so the SLE-15-Installerwill be able to contact our SCC or your SMT/SUSE Manager as source for the SLE 15 Modules.
> Notable changes
> 
> SLES 15 JeOS images are also available for download and testing!
> The Desktop Productivity Module has been replaced by the SLE Workstation Extension. This will only be an issue if you do an upgrade from a former Beta installation, which is an unsupported scenario <https://www.suse.com/betaprogram/sle-beta/#faq-update1>.
> The HA Module and HA Product have been combined to one HA Product which will be available for the various products where it's eligible. Reason for the changes with those two modules is that we want to simplify the universe.
> yast2-ca-management is no longer provided (FATE#319119).
> OpenSSL 1.0 is no longer installed by default, all packages have been migrated to OpenSSL 1.1. OpenSSL 1.0 will be available in Legacy module in the future.
> Fixed bug in RC1 (selection)
> 
> Existing swap partition is handled as ordinary filesystem [Bug 1080926]
> Many YaST components were updated and received a lot of enhancements and fixes.
> Added packages (across all modules):
> a52dec, alacarte, apache-pdfbox, boost, bzr, cal10n, c-ares, cargo, check, createrepo_c, cscope, delayacct-utils, dmraid, FastCGI, fftw3_3_3_6-gnu-openmpi2-hpc, flatpak-builder, glade, glew, gnustep-base, gstreamer-plugins-ugly, hdf5_1_10_1-gnu-openmpi2-hpc, installation-images-SLES_SAP, installation-images-SLES, kiwi-boot-descriptions, libcap1, libGLw, liboping, libpst, libqt5-qt3d, libqt5-qtquickcontrols2, libqt5-qtsensors, libqt5-qtwayland, libqt5xdg, libyui-qt-graph, meanwhile, meld, monitoring-plugins, mpiP_3_4_1-gnu-openmpi2-hpc, netcdf_4_4_1_1-gnu-mvapich2-hpc, netcdf_4_4_1_1-gnu-openmpi2-hpc, netcdf-fortran_4_4_4-gnu-openmpi2-hpc, openmpi_2_1_2-gnu-hpc, openmpi_2_1_2-gnu-hpc-testsuite, openmpi2, petsc_3_8_3-gnu-mpich-hpc, petsc_3_8_3-gnu-mvapich2-hpc, petsc_3_8_3-gnu-openmpi2-hpc, petsc, pixz, prctl, procinfo, purple-import-empathy, pv, python-kiwi, rust, scalapack_2_0_2-gnu-openmpi2-hpc, shim, stunnel, tidyp, u-boot, unar, vala, yast2-rmt.
> More information
> SLE Beta Page ? <https://www.suse.com/betaprogram/sle-beta>
> Release Notes ? <https://www.suse.com/betaprogram/sle-beta/#releasenotes>
> Known Issues ? <https://www.suse.com/betaprogram/sle-beta/#knownissues>
> 
> Your SUSE Linux Enterprise Team
> 
> 
> Do not hesitate to contact us at beta-programs at lists.suse.com <mailto:beta-programs at lists.suse.com> if you have any questions.
> 
> You received this email because you're signed up to get updates from us. Click here to unsubscribe. <mailto:beta-programs at lists.suse.com?subject=Unsubscribe%20from%20SLE%20Beta&body=Unsubscribe%20Unsubscribe%20from%20SLE%20Beta>_______________________________________________
> Beta-programs mailing list
> Beta-programs at lists.suse.com <mailto:Beta-programs at lists.suse.com>
> http://lists.suse.com/mailman/listinfo/beta-programs <http://lists.suse.com/mailman/listinfo/beta-programs>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180308/3a5a9784/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180308/3a5a9784/attachment.sig>

From Dick.Waite at softwareag.com  Thu Mar  8 03:08:29 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Thu, 8 Mar 2018 10:08:29 +0000
Subject: [sle-beta] RC1 UPDATE - Looking good
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076D9AC@daeexmbx1.eur.ad.sag>

Grand Morning,

If one has not made the following amend before running an UPDATE

solver.onlyRequires = true
installRecommends=false # or commented

How can one remove all the not needed bits and bobs with zypper or Yast2 or does one have to do the whole thing again ?

Many Thanks

__R

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180308/ac49bc71/attachment.htm>

From wayne.patton at suse.com  Thu Mar  8 12:52:22 2018
From: wayne.patton at suse.com (Wayne Patton)
Date: Thu, 8 Mar 2018 19:52:22 +0000
Subject: [sle-beta] SLE15 RC1 unable to pxe boot to install image
Message-ID: <1520538740.26756.23.camel@suse.com>

I am unable to pxe boot to the install image for SLES 15 RC1. 

I am using VMware Workstation version 14. I am able to pxe boot SLES 12
SP2 & SP3 and CaaS 2 just fine using the same setup. 

I have two options in my pxelinux.cfg/default file for SLE 15. The
first is modeled after my SLES 12 entry and the second is taken from
the example files that I found by installing the tftpboot-installation-
SLE-15-x86_64 package on another SLES 15 VM. 

For the first option, like SLE 12, I copied the initrd and linux files
from the install media to my tftp server into
/srv/tftpboot/sles/15/ga/x86_64/

For the second option, I copied the entire /srv/tftpboot/SLE-15-x86_64/ 
tree structure from the tftpboot-installation-SLE-15-x86_64 package to
my tftpserver, which is used in the second option below. 

I get the same results with both options. 

UI menu.c32

LABEL sles15-rc1-x86_64 - like 12
  MENU LABEL SLES 15 RC1 x86_64 - like 12
  KERNEL sles/15/ga/x86_64/linux
  APPEND initrd=sles/15/ga/x86_64/initrd install=http://192.168.122.1/i
nstall/sles/15/ga/x86_64/dvd1/

LABEL sles15-rc1-x86_64 - 15 tftpboot package
  MENU LABEL SLES 15 RC1 x86_64 - 15 tftpboot package
  KERNEL SLE-15-x86_64/boot/x86_64/loader/linux
  APPEND initrd=SLE-15-x86_64/boot/x86_64/loader/initrd instsys=tftp://
192.168.122.1/SLE-15-x86_64/boot/x86_64/root install=http://192.168.122
.1/install/sles/15/ga/x86_64/dvd1/

On the console, I get the following: 
---BEGIN OUTPUT--------
Starting udev... ok
Loading basic drivers   ok
Starting hardware detection .. ok
(If a driver is not working for you, try booting with
brokenmodules=driver_name

VMware SATA AHCI controller
  drivers: ahci*
VMware Virtual Machine Chipset
  drivers: ata_piix*, ata_generic, pata_acpi
VMware LSI Logic Parallel SCSI Controller
  drivers: mptspi*
VMware PRO/1000 MT Single Port Adapter
  drivers: e1000*
---END OUTPUT--------


And it stops there.  I would expect the following lines to show up next
but they never do. They do show up for SLES12 (SP2 & 3) and CaaS. For
SLE15 they do not.  


---BEGIN EXPECTED OUTPUT-----
eth0: network config created
Sending DHCP request to eth0
ok, ip = xxx.xxx.xxx.xxx/xx
---END EXPECTED OUTPUT-----

Also, I purposly changed the IP address in my SLES 12 entry to make it
not find the install media so I could see if this was before or after
trying to load the install image. It still output the above three lines
before hanging so this leads me to believe this is a function of
initrd????

I am not sure where to turn next. I have been google'ing all morning
with no luck, and also tried searching past posts here as well.

I also get the same results with Leap 15 (build 151.1) 

Thanks.
Wayne


-- 

Wayne Patton
Technical Account Manager
wayne.patton at suse.com
479-366-5446


From kukuk at suse.de  Thu Mar  8 12:57:25 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Thu, 8 Mar 2018 20:57:25 +0100
Subject: [sle-beta] sle12sp3 zypper dup to sle15 using all avail Package
 repos ... surprising number of SLE12 pkgs left behind a fairly basic
 development platform
In-Reply-To: <FB6BE87C-1A19-41AB-929E-45BC1753C88B@emc.com>
References: <FB6BE87C-1A19-41AB-929E-45BC1753C88B@emc.com>
Message-ID: <20180308195725.GA7960@suse.de>



Hi,

zypper dup from SLES12 SP3 to SLES15 is no supported upgrade path and
will never be. If you have bad luck, this can destroy your system and
requires a fresh installation.

On Thu, Mar 08, Bahi, David wrote:

> kernel and gcc are parallel w/ older versions preserved i guess... but the rest
> (shouldn't boost have been updated to 1_66_0, etc) ?

https://en.opensuse.org/openSUSE:Shared_library_packaging_policy

  Thorsten

> bahid at hw-and-os-97:~> grep -i  "system package" zypper_se-s-i-t_package.log  |
> cut -d'|' -f 2 | while read x ; do printf "%-40s %s\n" "$x" "$(rpm -qi $x |
> grep Distribution)" ; done
> kiwi                                     Distribution: SUSE Linux Enterprise 12
> kiwi-desc-isoboot                        Distribution: SUSE Linux Enterprise 12
> kiwi-desc-netboot                        Distribution: SUSE Linux Enterprise 12
> kiwi-desc-oemboot                        Distribution: SUSE Linux Enterprise 12
> kiwi-desc-vmxboot                        Distribution: SUSE Linux Enterprise 12
> kiwi-doc                                 Distribution: SUSE Linux Enterprise 12
> kiwi-templates                           Distribution: SUSE Linux Enterprise 12
> boost-license1_54_0                      Distribution: SUSE Linux Enterprise 12
> cpp48                                    Distribution: SUSE Linux Enterprise 12
> gcc48                                    Distribution: SUSE Linux Enterprise 12
> gcc48-c++                                Distribution: SUSE Linux Enterprise 12
> gcc48-info                               Distribution: SUSE Linux Enterprise 12
> gcc48-locale                             Distribution: SUSE Linux Enterprise 12
> libHalf11                                Distribution: SUSE Linux Enterprise 12
> libIex-2_1-11                            Distribution: SUSE Linux Enterprise 12
> libIlmImf-Imf_2_1-21                     Distribution: SUSE Linux Enterprise 12
> libIlmThread-2_1-11                      Distribution: SUSE Linux Enterprise 12
> libLLVM                                  Distribution: SUSE Linux Enterprise 12
> libMagickCore-6_Q16-1                    Distribution: SUSE Linux Enterprise 12
> libMagickWand-6_Q16-1                    Distribution: SUSE Linux Enterprise 12
> libadns1                                 Distribution: SUSE Linux Enterprise 12
> libasan0                                 Distribution: SUSE Linux Enterprise 12
> libaspell15                              Distribution: SUSE Linux Enterprise 12
> libass5                                  Distribution: SUSE Linux Enterprise 12
> libboost_atomic1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_chrono1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_context1_54_0                   Distribution: SUSE Linux Enterprise 12
> libboost_date_time1_54_0                 Distribution: SUSE Linux Enterprise 12
> libboost_filesystem1_54_0                Distribution: SUSE Linux Enterprise 12
> libboost_graph1_54_0                     Distribution: SUSE Linux Enterprise 12
> libboost_graph_parallel1_54_0            Distribution: SUSE Linux Enterprise 12
> libboost_iostreams1_54_0                 Distribution: SUSE Linux Enterprise 12
> libboost_locale1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_log1_54_0                       Distribution: SUSE Linux Enterprise 12
> libboost_math1_54_0                      Distribution: SUSE Linux Enterprise 12
> libboost_mpi1_54_0                       Distribution: SUSE Linux Enterprise 12
> libboost_program_options1_54_0           Distribution: SUSE Linux Enterprise 12
> libboost_python1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_random1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_regex1_54_0                     Distribution: SUSE Linux Enterprise 12
> libboost_serialization1_54_0             Distribution: SUSE Linux Enterprise 12
> libboost_signals1_54_0                   Distribution: SUSE Linux Enterprise 12
> libboost_system1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_test1_54_0                      Distribution: SUSE Linux Enterprise 12
> libboost_thread1_54_0                    Distribution: SUSE Linux Enterprise 12
> libboost_timer1_54_0                     Distribution: SUSE Linux Enterprise 12
> libboost_wave1_54_0                      Distribution: SUSE Linux Enterprise 12
> libcamgm100                              Distribution: SUSE Linux Enterprise 12
> libcloog-isl4                            Distribution: SUSE Linux Enterprise 12
> libcryptsetup4                           Distribution: SUSE Linux Enterprise 12
> libdialog11                              Distribution: SUSE Linux Enterprise 12
> libdvdnav4                               Distribution: SUSE Linux Enterprise 12
> libelf0                                  Distribution: SUSE Linux Enterprise 12
> libesd0                                  Distribution: SUSE Linux Enterprise 12
> libevent-2_0-5                           Distribution: SUSE Linux Enterprise 12
> libffi4                                  Distribution: SUSE Linux Enterprise 12
> libftgl2                                 Distribution: SUSE Linux Enterprise 12
> libgfortran3                             Distribution: SUSE Linux Enterprise 12
> libgif6                                  Distribution: SUSE Linux Enterprise 12
> libgnutls28                              Distribution: SUSE Linux Enterprise 12
> libgtop-2_0-10                           Distribution: SUSE Linux Enterprise 12
> libgucharmap_2_90-7                      Distribution: SUSE Linux Enterprise 12
> libhogweed2                              Distribution: SUSE Linux Enterprise 12
> libical1                                 Distribution: SUSE Linux Enterprise 12
> libicu52_1                               Distribution: SUSE Linux Enterprise 12
> libicu52_1-data                          Distribution: SUSE Linux Enterprise 12
> libisl10                                 Distribution: SUSE Linux Enterprise 12
> libjson-c2                               Distribution: SUSE Linux Enterprise 12
> liblcms1                                 Distribution: SUSE Linux Enterprise 12
> liblua5_1                                Distribution: SUSE Linux Enterprise 12
> liblua5_2                                Distribution: SUSE Linux Enterprise 12
> libmozjs-24                              Distribution: SUSE Linux Enterprise 12
> libmpfr4                                 Distribution: SUSE Linux Enterprise 12
> libnettle4                               Distribution: SUSE Linux Enterprise 12
> libnl1                                   Distribution: SUSE Linux Enterprise 12
> libopenct1                               Distribution: SUSE Linux Enterprise 12
> libprocps3                               Distribution: SUSE Linux Enterprise 12
> libprotobuf9                             Distribution: SUSE Linux Enterprise 12
> libprotobuf-lite9                        Distribution: SUSE Linux Enterprise 12
> libprotoc9                               Distribution: SUSE Linux Enterprise 12
> libpth20                                 Distribution: SUSE Linux Enterprise 12
> libpython3_4m1_0                         Distribution: SUSE Linux Enterprise 12
> libqrencode3                             Distribution: SUSE Linux Enterprise 12
> libreadline6                             Distribution: SUSE Linux Enterprise 12
> libruby2_1-2_1                           Distribution: SUSE Linux Enterprise 12
> libsgutils2-2                            Distribution: SUSE Linux Enterprise 12
> libts-1_0-0                              Distribution: SUSE Linux Enterprise 12
> libttf2                                  Distribution: SUSE Linux Enterprise 12
> libunistring0                            Distribution: SUSE Linux Enterprise 12
> liburcu0                                 Distribution: SUSE Linux Enterprise 12
> libvpx1                                  Distribution: SUSE Linux Enterprise 12
> libwebp5                                 Distribution: SUSE Linux Enterprise 12
> libwebrtc_audio_processing0              Distribution: SUSE Linux Enterprise 12
> libxtables10                             Distribution: SUSE Linux Enterprise 12
> libyui7                                  Distribution: SUSE Linux Enterprise 12
> libzmq3                                  Distribution: SUSE Linux Enterprise 12
> libzvbi0                                 Distribution: SUSE Linux Enterprise 12
> lsb5-core                                Distribution: SUSE Linux Enterprise 12
> mhash                                    Distribution: (none)
> novell-sound-theme                       Distribution: SUSE Linux Enterprise 12
> openmpi-compat                           Distribution: SUSE Linux Enterprise 12
> python-PyYAML                            Distribution: SUSE Linux Enterprise 12
> python-appdirs                           Distribution: devel:languages:python /
> SLE_12_SP2
> python-astroid                           Distribution: devel:languages:python /
> SLE_12_SP2
> python-backports                         Distribution: devel:languages:python /
> SLE_12_SP2
> python-backports.functools_lru_cache     Distribution: devel:languages:python /
> SLE_12_SP2
> python-configparser                      Distribution: devel:languages:python /
> SLE_12_SP2
> python-deltarpm                          Distribution: SUSE Linux Enterprise 12
> python-ecdsa                             Distribution: SUSE Linux Enterprise 12
> python-flake8                            Distribution: devel:languages:python /
> SLE_12_SP2
> python-flake8-polyfill                   Distribution: devel:languages:python /
> SLE_12_SP2
> python-gconf                             Distribution: SUSE Linux Enterprise 12
> python-ipaddr                            Distribution: SUSE Linux Enterprise 12
> python-lazy-object-proxy                 Distribution: devel:languages:python /
> SLE_12_SP2
> python-mccabe                            Distribution: devel:languages:python /
> SLE_12_SP2
> python-packaging                         Distribution: devel:languages:python /
> SLE_12_SP2
> python-pyasn1-modules                    Distribution: SUSE Linux Enterprise 12
> python-pycrypto                          Distribution: SUSE Linux Enterprise 12
> python-pyflakes                          Distribution: devel:languages:python /
> SLE_12_SP2
> python-snowballstemmer                   Distribution: devel:languages:python /
> SLE_12_SP2
> python-wrapt                             Distribution: devel:languages:python /
> SLE_12_SP2
> python-yum                               Distribution: SUSE Linux Enterprise 12
> ruby2.1                                  Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-abstract_method          Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-cfa                      Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-cfa_grub2                Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-cheetah                  Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-fast_gettext             Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-gem2rpm                  Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-ruby-augeas              Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-ruby-dbus                Distribution: SUSE Linux Enterprise 12
> ruby2.1-stdlib                           Distribution: SUSE Linux Enterprise 12
> saxon6                                   Distribution: SUSE Linux Enterprise 12
> udhcp                                    Distribution: SUSE Linux Enterprise 12
> MultiMarkdown-5                          Distribution: Publishing / SLE_12_SP2
> ShellCheck                               Distribution: devel:languages:haskell
> / SLE_12_SP2_Backports
> VMware-ovftool                           Distribution: (none)
> ansible                                  Distribution: systemsmanagement /
> SLE_12_SP2
> aspell                                   Distribution: SUSE Linux Enterprise 12
> aspell-en                                Distribution: SUSE Linux Enterprise 12
> aspell-ispell                            Distribution: SUSE Linux Enterprise 12
> atom                                     Distribution: (none)
> bitstream-vera-fonts                     Distribution: SUSE Linux Enterprise 12
> boost-devel                              Distribution: SUSE Linux Enterprise 12
> configure-network                        Distribution: (none)
> createrepo                               Distribution: SUSE Linux Enterprise 12
> cryptconfig                              Distribution: SUSE Linux Enterprise 12
> desktop-translations                     Distribution: SUSE Linux Enterprise 12
> facter                                   Distribution: SUSE Linux Enterprise 12
> finger                                   Distribution: SUSE Linux Enterprise 12
> flash-plugin                             Distribution: (none)
> freetype                                 Distribution: SUSE Linux Enterprise 12
> gconf2-branding-SLES                     Distribution: SUSE Linux Enterprise 12
> gnome-mime-data                          Distribution: SUSE Linux Enterprise 12
> gnome-nettool                            Distribution: SUSE Linux Enterprise 12
> google-chrome-stable                     Distribution: (none)
> gucharmap                                Distribution: SUSE Linux Enterprise 12
> icmpinfo                                 Distribution: SUSE Linux Enterprise 12
> inst-source-utils                        Distribution: SUSE Linux Enterprise 12
> java-1_8_0-openjdk-plugin                Distribution: SUSE Linux Enterprise 12
> joe                                      Distribution: SUSE Linux Enterprise 12
> kernel-default                           Distribution: SUSE Linux Enterprise 12
> Distribution: SUSE Linux Enterprise 15
> kernel-default-devel                     Distribution: SUSE Linux Enterprise 12
> Distribution: SUSE Linux Enterprise 15
> kernel-devel                             Distribution: SUSE Linux Enterprise 12
> Distribution: SUSE Linux Enterprise 15
> kernel-source                            Distribution: SUSE Linux Enterprise 12
> Distribution: SUSE Linux Enterprise 15
> kernel-syms                              Distribution: SUSE Linux Enterprise 12
> Distribution: SUSE Linux Enterprise 15
> libdm0                                   Distribution: SUSE Linux Enterprise 12
> libdrm-tools                             Distribution: SUSE Linux Enterprise 12
> libidn-tools                             Distribution: SUSE Linux Enterprise 12
> libmng1                                  Distribution: SUSE Linux Enterprise 12
> libnscd1                                 Distribution: SUSE Linux Enterprise 12
> libqt4                                   Distribution: SUSE Linux Enterprise 12
> libqt4-sql                               Distribution: SUSE Linux Enterprise 12
> libqt4-x11                               Distribution: SUSE Linux Enterprise 12
> libstdc++48-devel                        Distribution: SUSE Linux Enterprise 12
> libstroke                                Distribution: SUSE Linux Enterprise 12
> libyui-ncurses7                          Distribution: SUSE Linux Enterprise 12
> libyui-qt7                               Distribution: SUSE Linux Enterprise 12
> machinery                                Distribution: SUSE Linux Enterprise 12
> mhash-devel                              Distribution: (none)
> mingetty                                 Distribution: SUSE Linux Enterprise 12
> mpt-firmware                             Distribution: SUSE Linux Enterprise 12
> net-snmp-python                          Distribution: (none)
> openct                                   Distribution: SUSE Linux Enterprise 12
> opensc                                   Distribution: SUSE Linux Enterprise 12
> openssh-askpass                          Distribution: SUSE Linux Enterprise 12
> opie                                     Distribution: SUSE Linux Enterprise 12
> protobuf-devel                           Distribution: SUSE Linux Enterprise 12
> puppet                                   Distribution: SUSE Linux Enterprise 12
> python-flake8-docstrings                 Distribution: devel:languages:python /
> SLE_12_SP2
> python-flake8-todo                       Distribution: devel:languages:python /
> SLE_12_SP2
> python-ipy                               Distribution: SUSE Linux Enterprise 12
> python-isort                             Distribution: devel:languages:python /
> SLE_12_SP2
> python-netaddr                           Distribution: SUSE Linux Enterprise 12
> python-pcapy                             Distribution: (none)
> python-protobuf                          Distribution: (none)
> python-pycodestyle                       Distribution: devel:languages:python /
> SLE_12_SP2
> python-pydocstyle                        Distribution: devel:languages:python /
> SLE_12_SP2
> python-pyldap                            Distribution: SUSE Linux Enterprise 12
> python-pylint                            Distribution: devel:languages:python /
> SLE_12_SP2
> python-pyroute2                          Distribution: devel:languages:python /
> SLE_12_SP2
> python-rpyc                              Distribution: devel:languages:python /
> openSUSE_Factory
> recode                                   Distribution: SUSE Linux Enterprise 12
> repotool                                 Distribution: (none)
> rsh                                      Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-hiera-1                  Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-json_pure                Distribution: SUSE Linux Enterprise 12
> ruby2.1-rubygem-ruby-shadow              Distribution: SUSE Linux Enterprise 12
> rubygem-hiera-1                          Distribution: SUSE Linux Enterprise 12
> sshpass                                  Distribution: network / SLE_12_SP3
> unclutter                                Distribution: SUSE Linux Enterprise 12
> updatetool                               Distribution: (none)
> x86info                                  Distribution: SUSE Linux Enterprise 12
> xinetd                                   Distribution: SUSE Linux Enterprise 12
> xlockmore                                Distribution: SUSE Linux Enterprise 12
> xsd                                      Distribution: devel:libraries:c_c++ /
> SLE_12_SP3
> yast2-boot-server                        Distribution: SUSE Linux Enterprise 12
> yast2-branding-SLE                       Distribution: SUSE Linux Enterprise 12
> yast2-inetd                              Distribution: SUSE Linux Enterprise 12
> yast2-metapackage-handler                Distribution: SUSE Linux Enterprise 12
> 

> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta


-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From kukuk at suse.de  Thu Mar  8 13:43:00 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Thu, 8 Mar 2018 21:43:00 +0100
Subject: [sle-beta] sle12sp3 zypper dup to sle15 using all avail Package
 repos ... surprising number of SLE12 pkgs left behind a fairly basic
 development platform
In-Reply-To: <844BF273-12CD-436B-8BBB-EEAE33B2B37B@emc.com>
References: <FB6BE87C-1A19-41AB-929E-45BC1753C88B@emc.com>
	<20180308195725.GA7960@suse.de>
	<844BF273-12CD-436B-8BBB-EEAE33B2B37B@emc.com>
Message-ID: <20180308204300.GA10625@suse.de>

On Thu, Mar 08, Bahi, David wrote:

> thanks for the two clarifications.
> 
> nothing else required these shared libs or they would have had the old and new
> side by side.
> there were several non-library applications, but i guess i'm really only
> concerned by the absence of kiwi and createrepo.

kiwi and createrepo are still there. (Development-Tools and Basystem Modules)

> no zypper dup.  
> what is the PXE menu method of describing all the Package application/module
> repos then? 

Like in the past with the addon= option.

> because entering URLs by hand via the update tool is clumsy (time consuming and
> error prone).
> looking at this from an OEM perspective, _updating_ appliances is going to be
> interesting w/o zypper dup.

Nothing has changed here compared to the past.

  Thorsten

> 
>     On Mar 8, 2018, at 14:57, Thorsten Kukuk <kukuk at suse.de> wrote:
> 
> 
> 
>     Hi,
> 
>     zypper dup from SLES12 SP3 to SLES15 is no supported upgrade path and
>     will never be. If you have bad luck, this can destroy your system and
>     requires a fresh installation.
> 
>     On Thu, Mar 08, Bahi, David wrote:
> 
> 
>         kernel and gcc are parallel w/ older versions preserved i guess... but
>         the rest
>         (shouldn't boost have been updated to 1_66_0, etc) ?
> 
> 
>     https://en.opensuse.org/openSUSE:Shared_library_packaging_policy
> 
>      Thorsten
> 
> 
>         bahid at hw-and-os-97:~> grep -i  "system package"
>         zypper_se-s-i-t_package.log  |
>         cut -d'|' -f 2 | while read x ; do printf "%-40s %s\n" "$x" "$(rpm -qi
>         $x |
>         grep Distribution)" ; done
>         kiwi                                     Distribution: SUSE Linux
>         Enterprise 12
>         kiwi-desc-isoboot                        Distribution: SUSE Linux
>         Enterprise 12
>         kiwi-desc-netboot                        Distribution: SUSE Linux
>         Enterprise 12
>         kiwi-desc-oemboot                        Distribution: SUSE Linux
>         Enterprise 12
>         kiwi-desc-vmxboot                        Distribution: SUSE Linux
>         Enterprise 12
>         kiwi-doc                                 Distribution: SUSE Linux
>         Enterprise 12
>         kiwi-templates                           Distribution: SUSE Linux
>         Enterprise 12
>         boost-license1_54_0                      Distribution: SUSE Linux
>         Enterprise 12
>         cpp48                                    Distribution: SUSE Linux
>         Enterprise 12
>         gcc48                                    Distribution: SUSE Linux
>         Enterprise 12
>         gcc48-c++                                Distribution: SUSE Linux
>         Enterprise 12
>         gcc48-info                               Distribution: SUSE Linux
>         Enterprise 12
>         gcc48-locale                             Distribution: SUSE Linux
>         Enterprise 12
>         libHalf11                                Distribution: SUSE Linux
>         Enterprise 12
>         libIex-2_1-11                            Distribution: SUSE Linux
>         Enterprise 12
>         libIlmImf-Imf_2_1-21                     Distribution: SUSE Linux
>         Enterprise 12
>         libIlmThread-2_1-11                      Distribution: SUSE Linux
>         Enterprise 12
>         libLLVM                                  Distribution: SUSE Linux
>         Enterprise 12
>         libMagickCore-6_Q16-1                    Distribution: SUSE Linux
>         Enterprise 12
>         libMagickWand-6_Q16-1                    Distribution: SUSE Linux
>         Enterprise 12
>         libadns1                                 Distribution: SUSE Linux
>         Enterprise 12
>         libasan0                                 Distribution: SUSE Linux
>         Enterprise 12
>         libaspell15                              Distribution: SUSE Linux
>         Enterprise 12
>         libass5                                  Distribution: SUSE Linux
>         Enterprise 12
>         libboost_atomic1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_chrono1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_context1_54_0                   Distribution: SUSE Linux
>         Enterprise 12
>         libboost_date_time1_54_0                 Distribution: SUSE Linux
>         Enterprise 12
>         libboost_filesystem1_54_0                Distribution: SUSE Linux
>         Enterprise 12
>         libboost_graph1_54_0                     Distribution: SUSE Linux
>         Enterprise 12
>         libboost_graph_parallel1_54_0            Distribution: SUSE Linux
>         Enterprise 12
>         libboost_iostreams1_54_0                 Distribution: SUSE Linux
>         Enterprise 12
>         libboost_locale1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_log1_54_0                       Distribution: SUSE Linux
>         Enterprise 12
>         libboost_math1_54_0                      Distribution: SUSE Linux
>         Enterprise 12
>         libboost_mpi1_54_0                       Distribution: SUSE Linux
>         Enterprise 12
>         libboost_program_options1_54_0           Distribution: SUSE Linux
>         Enterprise 12
>         libboost_python1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_random1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_regex1_54_0                     Distribution: SUSE Linux
>         Enterprise 12
>         libboost_serialization1_54_0             Distribution: SUSE Linux
>         Enterprise 12
>         libboost_signals1_54_0                   Distribution: SUSE Linux
>         Enterprise 12
>         libboost_system1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_test1_54_0                      Distribution: SUSE Linux
>         Enterprise 12
>         libboost_thread1_54_0                    Distribution: SUSE Linux
>         Enterprise 12
>         libboost_timer1_54_0                     Distribution: SUSE Linux
>         Enterprise 12
>         libboost_wave1_54_0                      Distribution: SUSE Linux
>         Enterprise 12
>         libcamgm100                              Distribution: SUSE Linux
>         Enterprise 12
>         libcloog-isl4                            Distribution: SUSE Linux
>         Enterprise 12
>         libcryptsetup4                           Distribution: SUSE Linux
>         Enterprise 12
>         libdialog11                              Distribution: SUSE Linux
>         Enterprise 12
>         libdvdnav4                               Distribution: SUSE Linux
>         Enterprise 12
>         libelf0                                  Distribution: SUSE Linux
>         Enterprise 12
>         libesd0                                  Distribution: SUSE Linux
>         Enterprise 12
>         libevent-2_0-5                           Distribution: SUSE Linux
>         Enterprise 12
>         libffi4                                  Distribution: SUSE Linux
>         Enterprise 12
>         libftgl2                                 Distribution: SUSE Linux
>         Enterprise 12
>         libgfortran3                             Distribution: SUSE Linux
>         Enterprise 12
>         libgif6                                  Distribution: SUSE Linux
>         Enterprise 12
>         libgnutls28                              Distribution: SUSE Linux
>         Enterprise 12
>         libgtop-2_0-10                           Distribution: SUSE Linux
>         Enterprise 12
>         libgucharmap_2_90-7                      Distribution: SUSE Linux
>         Enterprise 12
>         libhogweed2                              Distribution: SUSE Linux
>         Enterprise 12
>         libical1                                 Distribution: SUSE Linux
>         Enterprise 12
>         libicu52_1                               Distribution: SUSE Linux
>         Enterprise 12
>         libicu52_1-data                          Distribution: SUSE Linux
>         Enterprise 12
>         libisl10                                 Distribution: SUSE Linux
>         Enterprise 12
>         libjson-c2                               Distribution: SUSE Linux
>         Enterprise 12
>         liblcms1                                 Distribution: SUSE Linux
>         Enterprise 12
>         liblua5_1                                Distribution: SUSE Linux
>         Enterprise 12
>         liblua5_2                                Distribution: SUSE Linux
>         Enterprise 12
>         libmozjs-24                              Distribution: SUSE Linux
>         Enterprise 12
>         libmpfr4                                 Distribution: SUSE Linux
>         Enterprise 12
>         libnettle4                               Distribution: SUSE Linux
>         Enterprise 12
>         libnl1                                   Distribution: SUSE Linux
>         Enterprise 12
>         libopenct1                               Distribution: SUSE Linux
>         Enterprise 12
>         libprocps3                               Distribution: SUSE Linux
>         Enterprise 12
>         libprotobuf9                             Distribution: SUSE Linux
>         Enterprise 12
>         libprotobuf-lite9                        Distribution: SUSE Linux
>         Enterprise 12
>         libprotoc9                               Distribution: SUSE Linux
>         Enterprise 12
>         libpth20                                 Distribution: SUSE Linux
>         Enterprise 12
>         libpython3_4m1_0                         Distribution: SUSE Linux
>         Enterprise 12
>         libqrencode3                             Distribution: SUSE Linux
>         Enterprise 12
>         libreadline6                             Distribution: SUSE Linux
>         Enterprise 12
>         libruby2_1-2_1                           Distribution: SUSE Linux
>         Enterprise 12
>         libsgutils2-2                            Distribution: SUSE Linux
>         Enterprise 12
>         libts-1_0-0                              Distribution: SUSE Linux
>         Enterprise 12
>         libttf2                                  Distribution: SUSE Linux
>         Enterprise 12
>         libunistring0                            Distribution: SUSE Linux
>         Enterprise 12
>         liburcu0                                 Distribution: SUSE Linux
>         Enterprise 12
>         libvpx1                                  Distribution: SUSE Linux
>         Enterprise 12
>         libwebp5                                 Distribution: SUSE Linux
>         Enterprise 12
>         libwebrtc_audio_processing0              Distribution: SUSE Linux
>         Enterprise 12
>         libxtables10                             Distribution: SUSE Linux
>         Enterprise 12
>         libyui7                                  Distribution: SUSE Linux
>         Enterprise 12
>         libzmq3                                  Distribution: SUSE Linux
>         Enterprise 12
>         libzvbi0                                 Distribution: SUSE Linux
>         Enterprise 12
>         lsb5-core                                Distribution: SUSE Linux
>         Enterprise 12
>         mhash                                    Distribution: (none)
>         novell-sound-theme                       Distribution: SUSE Linux
>         Enterprise 12
>         openmpi-compat                           Distribution: SUSE Linux
>         Enterprise 12
>         python-PyYAML                            Distribution: SUSE Linux
>         Enterprise 12
>         python-appdirs                           Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-astroid                           Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-backports                         Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-backports.functools_lru_cache     Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-configparser                      Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-deltarpm                          Distribution: SUSE Linux
>         Enterprise 12
>         python-ecdsa                             Distribution: SUSE Linux
>         Enterprise 12
>         python-flake8                            Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-flake8-polyfill                   Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-gconf                             Distribution: SUSE Linux
>         Enterprise 12
>         python-ipaddr                            Distribution: SUSE Linux
>         Enterprise 12
>         python-lazy-object-proxy                 Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-mccabe                            Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-packaging                         Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-pyasn1-modules                    Distribution: SUSE Linux
>         Enterprise 12
>         python-pycrypto                          Distribution: SUSE Linux
>         Enterprise 12
>         python-pyflakes                          Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-snowballstemmer                   Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-wrapt                             Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-yum                               Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1                                  Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-abstract_method          Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-cfa                      Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-cfa_grub2                Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-cheetah                  Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-fast_gettext             Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-gem2rpm                  Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-ruby-augeas              Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-ruby-dbus                Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-stdlib                           Distribution: SUSE Linux
>         Enterprise 12
>         saxon6                                   Distribution: SUSE Linux
>         Enterprise 12
>         udhcp                                    Distribution: SUSE Linux
>         Enterprise 12
>         MultiMarkdown-5                          Distribution: Publishing /
>         SLE_12_SP2
>         ShellCheck                               Distribution:
>         devel:languages:haskell
>         / SLE_12_SP2_Backports
>         VMware-ovftool                           Distribution: (none)
>         ansible                                  Distribution:
>         systemsmanagement /
>         SLE_12_SP2
>         aspell                                   Distribution: SUSE Linux
>         Enterprise 12
>         aspell-en                                Distribution: SUSE Linux
>         Enterprise 12
>         aspell-ispell                            Distribution: SUSE Linux
>         Enterprise 12
>         atom                                     Distribution: (none)
>         bitstream-vera-fonts                     Distribution: SUSE Linux
>         Enterprise 12
>         boost-devel                              Distribution: SUSE Linux
>         Enterprise 12
>         configure-network                        Distribution: (none)
>         createrepo                               Distribution: SUSE Linux
>         Enterprise 12
>         cryptconfig                              Distribution: SUSE Linux
>         Enterprise 12
>         desktop-translations                     Distribution: SUSE Linux
>         Enterprise 12
>         facter                                   Distribution: SUSE Linux
>         Enterprise 12
>         finger                                   Distribution: SUSE Linux
>         Enterprise 12
>         flash-plugin                             Distribution: (none)
>         freetype                                 Distribution: SUSE Linux
>         Enterprise 12
>         gconf2-branding-SLES                     Distribution: SUSE Linux
>         Enterprise 12
>         gnome-mime-data                          Distribution: SUSE Linux
>         Enterprise 12
>         gnome-nettool                            Distribution: SUSE Linux
>         Enterprise 12
>         google-chrome-stable                     Distribution: (none)
>         gucharmap                                Distribution: SUSE Linux
>         Enterprise 12
>         icmpinfo                                 Distribution: SUSE Linux
>         Enterprise 12
>         inst-source-utils                        Distribution: SUSE Linux
>         Enterprise 12
>         java-1_8_0-openjdk-plugin                Distribution: SUSE Linux
>         Enterprise 12
>         joe                                      Distribution: SUSE Linux
>         Enterprise 12
>         kernel-default                           Distribution: SUSE Linux
>         Enterprise 12
>         Distribution: SUSE Linux Enterprise 15
>         kernel-default-devel                     Distribution: SUSE Linux
>         Enterprise 12
>         Distribution: SUSE Linux Enterprise 15
>         kernel-devel                             Distribution: SUSE Linux
>         Enterprise 12
>         Distribution: SUSE Linux Enterprise 15
>         kernel-source                            Distribution: SUSE Linux
>         Enterprise 12
>         Distribution: SUSE Linux Enterprise 15
>         kernel-syms                              Distribution: SUSE Linux
>         Enterprise 12
>         Distribution: SUSE Linux Enterprise 15
>         libdm0                                   Distribution: SUSE Linux
>         Enterprise 12
>         libdrm-tools                             Distribution: SUSE Linux
>         Enterprise 12
>         libidn-tools                             Distribution: SUSE Linux
>         Enterprise 12
>         libmng1                                  Distribution: SUSE Linux
>         Enterprise 12
>         libnscd1                                 Distribution: SUSE Linux
>         Enterprise 12
>         libqt4                                   Distribution: SUSE Linux
>         Enterprise 12
>         libqt4-sql                               Distribution: SUSE Linux
>         Enterprise 12
>         libqt4-x11                               Distribution: SUSE Linux
>         Enterprise 12
>         libstdc++48-devel                        Distribution: SUSE Linux
>         Enterprise 12
>         libstroke                                Distribution: SUSE Linux
>         Enterprise 12
>         libyui-ncurses7                          Distribution: SUSE Linux
>         Enterprise 12
>         libyui-qt7                               Distribution: SUSE Linux
>         Enterprise 12
>         machinery                                Distribution: SUSE Linux
>         Enterprise 12
>         mhash-devel                              Distribution: (none)
>         mingetty                                 Distribution: SUSE Linux
>         Enterprise 12
>         mpt-firmware                             Distribution: SUSE Linux
>         Enterprise 12
>         net-snmp-python                          Distribution: (none)
>         openct                                   Distribution: SUSE Linux
>         Enterprise 12
>         opensc                                   Distribution: SUSE Linux
>         Enterprise 12
>         openssh-askpass                          Distribution: SUSE Linux
>         Enterprise 12
>         opie                                     Distribution: SUSE Linux
>         Enterprise 12
>         protobuf-devel                           Distribution: SUSE Linux
>         Enterprise 12
>         puppet                                   Distribution: SUSE Linux
>         Enterprise 12
>         python-flake8-docstrings                 Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-flake8-todo                       Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-ipy                               Distribution: SUSE Linux
>         Enterprise 12
>         python-isort                             Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-netaddr                           Distribution: SUSE Linux
>         Enterprise 12
>         python-pcapy                             Distribution: (none)
>         python-protobuf                          Distribution: (none)
>         python-pycodestyle                       Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-pydocstyle                        Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-pyldap                            Distribution: SUSE Linux
>         Enterprise 12
>         python-pylint                            Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-pyroute2                          Distribution:
>         devel:languages:python /
>         SLE_12_SP2
>         python-rpyc                              Distribution:
>         devel:languages:python /
>         openSUSE_Factory
>         recode                                   Distribution: SUSE Linux
>         Enterprise 12
>         repotool                                 Distribution: (none)
>         rsh                                      Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-hiera-1                  Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-json_pure                Distribution: SUSE Linux
>         Enterprise 12
>         ruby2.1-rubygem-ruby-shadow              Distribution: SUSE Linux
>         Enterprise 12
>         rubygem-hiera-1                          Distribution: SUSE Linux
>         Enterprise 12
>         sshpass                                  Distribution: network /
>         SLE_12_SP3
>         unclutter                                Distribution: SUSE Linux
>         Enterprise 12
>         updatetool                               Distribution: (none)
>         x86info                                  Distribution: SUSE Linux
>         Enterprise 12
>         xinetd                                   Distribution: SUSE Linux
>         Enterprise 12
>         xlockmore                                Distribution: SUSE Linux
>         Enterprise 12
>         xsd                                      Distribution:
>         devel:libraries:c_c++ /
>         SLE_12_SP3
>         yast2-boot-server                        Distribution: SUSE Linux
>         Enterprise 12
>         yast2-branding-SLE                       Distribution: SUSE Linux
>         Enterprise 12
>         yast2-inetd                              Distribution: SUSE Linux
>         Enterprise 12
>         yast2-metapackage-handler                Distribution: SUSE Linux
>         Enterprise 12
> 
> 
> 
>         _______________________________________________
>         sle-beta mailing list
>         sle-beta at lists.suse.com
>         http://lists.suse.com/mailman/listinfo/sle-beta
> 
> 
> 
>     -- 
>     Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
>     SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
>     GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG
>     Nuernberg)
>     _______________________________________________
>     sle-beta mailing list
>     sle-beta at lists.suse.com
>     http://lists.suse.com/mailman/listinfo/sle-beta
> 
> 

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From wayne.patton at suse.com  Thu Mar  8 14:09:09 2018
From: wayne.patton at suse.com (Wayne Patton)
Date: Thu, 8 Mar 2018 21:09:09 +0000
Subject: [sle-beta] SLE15 RC1 unable to pxe boot to install image
In-Reply-To: <1520538740.26756.23.camel@suse.com>
References: <1520538740.26756.23.camel@suse.com>
Message-ID: <1520543348.26756.27.camel@suse.com>

Update: Both options I presented below work in KVM with no changes. I
created a network in KVM, a blank VM, enabled DHCP on that network
using dnsmasq and it worked.

So is this a network driver issue??? Something else?

WP


On Thu, 2018-03-08 at 19:52 +0000, Wayne Patton wrote:
> I am unable to pxe boot to the install image for SLES 15 RC1. 
> 
> I am using VMware Workstation version 14. I am able to pxe boot SLES
> 12
> SP2 & SP3 and CaaS 2 just fine using the same setup. 
> 
> I have two options in my pxelinux.cfg/default file for SLE 15. The
> first is modeled after my SLES 12 entry and the second is taken from
> the example files that I found by installing the tftpboot-
> installation-
> SLE-15-x86_64 package on another SLES 15 VM. 
> 
> For the first option, like SLE 12, I copied the initrd and linux
> files
> from the install media to my tftp server into
> /srv/tftpboot/sles/15/ga/x86_64/
> 
> For the second option, I copied the entire /srv/tftpboot/SLE-15-
> x86_64/ 
> tree structure from the tftpboot-installation-SLE-15-x86_64 package
> to
> my tftpserver, which is used in the second option below. 
> 
> I get the same results with both options. 
> 
> UI menu.c32
> 
> LABEL sles15-rc1-x86_64 - like 12
>   MENU LABEL SLES 15 RC1 x86_64 - like 12
>   KERNEL sles/15/ga/x86_64/linux
>   APPEND initrd=sles/15/ga/x86_64/initrd install=http://192.168.122.1
> /i
> nstall/sles/15/ga/x86_64/dvd1/
> 
> LABEL sles15-rc1-x86_64 - 15 tftpboot package
>   MENU LABEL SLES 15 RC1 x86_64 - 15 tftpboot package
>   KERNEL SLE-15-x86_64/boot/x86_64/loader/linux
>   APPEND initrd=SLE-15-x86_64/boot/x86_64/loader/initrd
> instsys=tftp://
> 192.168.122.1/SLE-15-x86_64/boot/x86_64/root install=http://192.168.1
> 22
> .1/install/sles/15/ga/x86_64/dvd1/
> 
> On the console, I get the following: 
> ---BEGIN OUTPUT--------
> Starting udev... ok
> Loading basic drivers   ok
> Starting hardware detection .. ok
> (If a driver is not working for you, try booting with
> brokenmodules=driver_name
> 
> VMware SATA AHCI controller
>   drivers: ahci*
> VMware Virtual Machine Chipset
>   drivers: ata_piix*, ata_generic, pata_acpi
> VMware LSI Logic Parallel SCSI Controller
>   drivers: mptspi*
> VMware PRO/1000 MT Single Port Adapter
>   drivers: e1000*
> ---END OUTPUT--------
> 
> 
> And it stops there.  I would expect the following lines to show up
> next
> but they never do. They do show up for SLES12 (SP2 & 3) and CaaS. For
> SLE15 they do not.  
> 
> 
> ---BEGIN EXPECTED OUTPUT-----
> eth0: network config created
> Sending DHCP request to eth0
> ok, ip = xxx.xxx.xxx.xxx/xx
> ---END EXPECTED OUTPUT-----
> 
> Also, I purposly changed the IP address in my SLES 12 entry to make
> it
> not find the install media so I could see if this was before or after
> trying to load the install image. It still output the above three
> lines
> before hanging so this leads me to believe this is a function of
> initrd????
> 
> I am not sure where to turn next. I have been google'ing all morning
> with no luck, and also tried searching past posts here as well.
> 
> I also get the same results with Leap 15 (build 151.1) 
> 
> Thanks.
> Wayne
> 
> 

From kukuk at suse.de  Thu Mar  8 22:29:58 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Fri, 9 Mar 2018 06:29:58 +0100
Subject: [sle-beta] SLE15 RC1 unable to pxe boot to install image
In-Reply-To: <1520543348.26756.27.camel@suse.com>
References: <1520538740.26756.23.camel@suse.com>
	<1520543348.26756.27.camel@suse.com>
Message-ID: <20180309052958.GA12467@suse.de>

On Thu, Mar 08, Wayne Patton wrote:

> Update: Both options I presented below work in KVM with no changes. I
> created a network in KVM, a blank VM, enabled DHCP on that network
> using dnsmasq and it worked.
> 
> So is this a network driver issue??? Something else?

Can you install this VMWare machines with a DVD?

  Thorsten

> WP
> 
> 
> On Thu, 2018-03-08 at 19:52 +0000, Wayne Patton wrote:
> > I am unable to pxe boot to the install image for SLES 15 RC1. 
> > 
> > I am using VMware Workstation version 14. I am able to pxe boot SLES
> > 12
> > SP2 & SP3 and CaaS 2 just fine using the same setup. 
> > 
> > I have two options in my pxelinux.cfg/default file for SLE 15. The
> > first is modeled after my SLES 12 entry and the second is taken from
> > the example files that I found by installing the tftpboot-
> > installation-
> > SLE-15-x86_64 package on another SLES 15 VM. 
> > 
> > For the first option, like SLE 12, I copied the initrd and linux
> > files
> > from the install media to my tftp server into
> > /srv/tftpboot/sles/15/ga/x86_64/
> > 
> > For the second option, I copied the entire /srv/tftpboot/SLE-15-
> > x86_64/ 
> > tree structure from the tftpboot-installation-SLE-15-x86_64 package
> > to
> > my tftpserver, which is used in the second option below. 
> > 
> > I get the same results with both options. 
> > 
> > UI menu.c32
> > 
> > LABEL sles15-rc1-x86_64 - like 12
> >   MENU LABEL SLES 15 RC1 x86_64 - like 12
> >   KERNEL sles/15/ga/x86_64/linux
> >   APPEND initrd=sles/15/ga/x86_64/initrd install=http://192.168.122.1
> > /i
> > nstall/sles/15/ga/x86_64/dvd1/
> > 
> > LABEL sles15-rc1-x86_64 - 15 tftpboot package
> >   MENU LABEL SLES 15 RC1 x86_64 - 15 tftpboot package
> >   KERNEL SLE-15-x86_64/boot/x86_64/loader/linux
> >   APPEND initrd=SLE-15-x86_64/boot/x86_64/loader/initrd
> > instsys=tftp://
> > 192.168.122.1/SLE-15-x86_64/boot/x86_64/root install=http://192.168.1
> > 22
> > .1/install/sles/15/ga/x86_64/dvd1/
> > 
> > On the console, I get the following: 
> > ---BEGIN OUTPUT--------
> > Starting udev... ok
> > Loading basic drivers   ok
> > Starting hardware detection .. ok
> > (If a driver is not working for you, try booting with
> > brokenmodules=driver_name
> > 
> > VMware SATA AHCI controller
> >   drivers: ahci*
> > VMware Virtual Machine Chipset
> >   drivers: ata_piix*, ata_generic, pata_acpi
> > VMware LSI Logic Parallel SCSI Controller
> >   drivers: mptspi*
> > VMware PRO/1000 MT Single Port Adapter
> >   drivers: e1000*
> > ---END OUTPUT--------
> > 
> > 
> > And it stops there.  I would expect the following lines to show up
> > next
> > but they never do. They do show up for SLES12 (SP2 & 3) and CaaS. For
> > SLE15 they do not.  
> > 
> > 
> > ---BEGIN EXPECTED OUTPUT-----
> > eth0: network config created
> > Sending DHCP request to eth0
> > ok, ip = xxx.xxx.xxx.xxx/xx
> > ---END EXPECTED OUTPUT-----
> > 
> > Also, I purposly changed the IP address in my SLES 12 entry to make
> > it
> > not find the install media so I could see if this was before or after
> > trying to load the install image. It still output the above three
> > lines
> > before hanging so this leads me to believe this is a function of
> > initrd????
> > 
> > I am not sure where to turn next. I have been google'ing all morning
> > with no luck, and also tried searching past posts here as well.
> > 
> > I also get the same results with Leap 15 (build 151.1) 
> > 
> > Thanks.
> > Wayne
> > 
> > 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From kdupke at suse.com  Fri Mar  9 05:49:42 2018
From: kdupke at suse.com (Kai Dupke)
Date: Fri, 9 Mar 2018 13:49:42 +0100
Subject: [sle-beta] samba-tool missing
In-Reply-To: <5AA22AAA0200004D0002D437@mail.triples.at>
References: <5AA22AAA0200004D0002D437@mail.triples.at>
Message-ID: <0f65749f-e45c-d731-8399-18698036bbf1@suse.com>

On 09.03.2018 07:33, Peter jahn wrote:
> The command samba-tool is the "Main Samba administration tool" for Samba 4.
> https://www.samba.org/samba/docs/current/man-html/samba-tool.8.html

What is missing in the YaSt2 samba client/server tool?

> This command was not available in SLES12 and it seems that it is still true for SLES15RC1. Are there any reasons why SUSE doesn't offer the main administration tool?

I have not found a feature request to add this at all.

Of course, for SUSE Linux Enterprise we are looking into YaST2 as the
tool to manage wherever possible, this feature request might not be
accepted.

Best regards,
Kai Dupke
Senior Product Manager
SUSE Linux Enterprise 15
-- 
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 wayne.patton at suse.com  Fri Mar  9 06:54:18 2018
From: wayne.patton at suse.com (Wayne Patton)
Date: Fri, 9 Mar 2018 13:54:18 +0000
Subject: [sle-beta] SLE15 RC1 unable to pxe boot to install image
In-Reply-To: <20180309052958.GA12467@suse.de>
References: <1520538740.26756.23.camel@suse.com>
	<1520543348.26756.27.camel@suse.com> <20180309052958.GA12467@suse.de>
Message-ID: <1520603656.29644.5.camel@suse.com>

Thorsten - Yes I can install it with the dvd/iso images.

Wayne



On Fri, 2018-03-09 at 06:29 +0100, Thorsten Kukuk wrote:
> On Thu, Mar 08, Wayne Patton wrote:
> 
> > Update: Both options I presented below work in KVM with no changes.
> > I
> > created a network in KVM, a blank VM, enabled DHCP on that network
> > using dnsmasq and it worked.
> > 
> > So is this a network driver issue??? Something else?
> 
> Can you install this VMWare machines with a DVD?
> 
>   Thorsten
> 
> > WP
> > 
> > 
> > On Thu, 2018-03-08 at 19:52 +0000, Wayne Patton wrote:
> > > I am unable to pxe boot to the install image for SLES 15 RC1. 
> > > 
> > > I am using VMware Workstation version 14. I am able to pxe boot
> > > SLES
> > > 12
> > > SP2 & SP3 and CaaS 2 just fine using the same setup. 
> > > 
> > > I have two options in my pxelinux.cfg/default file for SLE 15.
> > > The
> > > first is modeled after my SLES 12 entry and the second is taken
> > > from
> > > the example files that I found by installing the tftpboot-
> > > installation-
> > > SLE-15-x86_64 package on another SLES 15 VM. 
> > > 
> > > For the first option, like SLE 12, I copied the initrd and linux
> > > files
> > > from the install media to my tftp server into
> > > /srv/tftpboot/sles/15/ga/x86_64/
> > > 
> > > For the second option, I copied the entire /srv/tftpboot/SLE-15-
> > > x86_64/ 
> > > tree structure from the tftpboot-installation-SLE-15-x86_64
> > > package
> > > to
> > > my tftpserver, which is used in the second option below. 
> > > 
> > > I get the same results with both options. 
> > > 
> > > UI menu.c32
> > > 
> > > LABEL sles15-rc1-x86_64 - like 12
> > >   MENU LABEL SLES 15 RC1 x86_64 - like 12
> > >   KERNEL sles/15/ga/x86_64/linux
> > >   APPEND initrd=sles/15/ga/x86_64/initrd install=http://192.168.1
> > > 22.1
> > > /i
> > > nstall/sles/15/ga/x86_64/dvd1/
> > > 
> > > LABEL sles15-rc1-x86_64 - 15 tftpboot package
> > >   MENU LABEL SLES 15 RC1 x86_64 - 15 tftpboot package
> > >   KERNEL SLE-15-x86_64/boot/x86_64/loader/linux
> > >   APPEND initrd=SLE-15-x86_64/boot/x86_64/loader/initrd
> > > instsys=tftp://
> > > 192.168.122.1/SLE-15-x86_64/boot/x86_64/root install=http://192.1
> > > 68.1
> > > 22
> > > .1/install/sles/15/ga/x86_64/dvd1/
> > > 
> > > On the console, I get the following: 
> > > ---BEGIN OUTPUT--------
> > > Starting udev... ok
> > > Loading basic drivers   ok
> > > Starting hardware detection .. ok
> > > (If a driver is not working for you, try booting with
> > > brokenmodules=driver_name
> > > 
> > > VMware SATA AHCI controller
> > >   drivers: ahci*
> > > VMware Virtual Machine Chipset
> > >   drivers: ata_piix*, ata_generic, pata_acpi
> > > VMware LSI Logic Parallel SCSI Controller
> > >   drivers: mptspi*
> > > VMware PRO/1000 MT Single Port Adapter
> > >   drivers: e1000*
> > > ---END OUTPUT--------
> > > 
> > > 
> > > And it stops there.  I would expect the following lines to show
> > > up
> > > next
> > > but they never do. They do show up for SLES12 (SP2 & 3) and CaaS.
> > > For
> > > SLE15 they do not.  
> > > 
> > > 
> > > ---BEGIN EXPECTED OUTPUT-----
> > > eth0: network config created
> > > Sending DHCP request to eth0
> > > ok, ip = xxx.xxx.xxx.xxx/xx
> > > ---END EXPECTED OUTPUT-----
> > > 
> > > Also, I purposly changed the IP address in my SLES 12 entry to
> > > make
> > > it
> > > not find the install media so I could see if this was before or
> > > after
> > > trying to load the install image. It still output the above three
> > > lines
> > > before hanging so this leads me to believe this is a function of
> > > initrd????
> > > 
> > > I am not sure where to turn next. I have been google'ing all
> > > morning
> > > with no luck, and also tried searching past posts here as well.
> > > 
> > > I also get the same results with Leap 15 (build 151.1) 
> > > 
> > > Thanks.
> > > Wayne
> > > 
> > > 
> > 
> > _______________________________________________
> > sle-beta mailing list
> > sle-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sle-beta
> 
> 

From kukuk at suse.de  Fri Mar  9 07:28:50 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Fri, 9 Mar 2018 15:28:50 +0100
Subject: [sle-beta] SLE15 RC1 unable to pxe boot to install image
In-Reply-To: <1520603656.29644.5.camel@suse.com>
References: <1520538740.26756.23.camel@suse.com>
	<1520543348.26756.27.camel@suse.com>
	<20180309052958.GA12467@suse.de>
	<1520603656.29644.5.camel@suse.com>
Message-ID: <20180309142850.GA29718@suse.de>

On Fri, Mar 09, Wayne Patton wrote:

> Thorsten - Yes I can install it with the dvd/iso images.

Then please create a bug report, I have no idea what is special
with VMware, I don't use that.

  Thorsten

> Wayne
> 
> 
> 
> On Fri, 2018-03-09 at 06:29 +0100, Thorsten Kukuk wrote:
> > On Thu, Mar 08, Wayne Patton wrote:
> > 
> > > Update: Both options I presented below work in KVM with no changes.
> > > I
> > > created a network in KVM, a blank VM, enabled DHCP on that network
> > > using dnsmasq and it worked.
> > > 
> > > So is this a network driver issue??? Something else?
> > 
> > Can you install this VMWare machines with a DVD?
> > 
> >   Thorsten
> > 
> > > WP
> > > 
> > > 
> > > On Thu, 2018-03-08 at 19:52 +0000, Wayne Patton wrote:
> > > > I am unable to pxe boot to the install image for SLES 15 RC1. 
> > > > 
> > > > I am using VMware Workstation version 14. I am able to pxe boot
> > > > SLES
> > > > 12
> > > > SP2 & SP3 and CaaS 2 just fine using the same setup. 
> > > > 
> > > > I have two options in my pxelinux.cfg/default file for SLE 15.
> > > > The
> > > > first is modeled after my SLES 12 entry and the second is taken
> > > > from
> > > > the example files that I found by installing the tftpboot-
> > > > installation-
> > > > SLE-15-x86_64 package on another SLES 15 VM. 
> > > > 
> > > > For the first option, like SLE 12, I copied the initrd and linux
> > > > files
> > > > from the install media to my tftp server into
> > > > /srv/tftpboot/sles/15/ga/x86_64/
> > > > 
> > > > For the second option, I copied the entire /srv/tftpboot/SLE-15-
> > > > x86_64/ 
> > > > tree structure from the tftpboot-installation-SLE-15-x86_64
> > > > package
> > > > to
> > > > my tftpserver, which is used in the second option below. 
> > > > 
> > > > I get the same results with both options. 
> > > > 
> > > > UI menu.c32
> > > > 
> > > > LABEL sles15-rc1-x86_64 - like 12
> > > >   MENU LABEL SLES 15 RC1 x86_64 - like 12
> > > >   KERNEL sles/15/ga/x86_64/linux
> > > >   APPEND initrd=sles/15/ga/x86_64/initrd install=http://192.168.1
> > > > 22.1
> > > > /i
> > > > nstall/sles/15/ga/x86_64/dvd1/
> > > > 
> > > > LABEL sles15-rc1-x86_64 - 15 tftpboot package
> > > >   MENU LABEL SLES 15 RC1 x86_64 - 15 tftpboot package
> > > >   KERNEL SLE-15-x86_64/boot/x86_64/loader/linux
> > > >   APPEND initrd=SLE-15-x86_64/boot/x86_64/loader/initrd
> > > > instsys=tftp://
> > > > 192.168.122.1/SLE-15-x86_64/boot/x86_64/root install=http://192.1
> > > > 68.1
> > > > 22
> > > > .1/install/sles/15/ga/x86_64/dvd1/
> > > > 
> > > > On the console, I get the following: 
> > > > ---BEGIN OUTPUT--------
> > > > Starting udev... ok
> > > > Loading basic drivers   ok
> > > > Starting hardware detection .. ok
> > > > (If a driver is not working for you, try booting with
> > > > brokenmodules=driver_name
> > > > 
> > > > VMware SATA AHCI controller
> > > >   drivers: ahci*
> > > > VMware Virtual Machine Chipset
> > > >   drivers: ata_piix*, ata_generic, pata_acpi
> > > > VMware LSI Logic Parallel SCSI Controller
> > > >   drivers: mptspi*
> > > > VMware PRO/1000 MT Single Port Adapter
> > > >   drivers: e1000*
> > > > ---END OUTPUT--------
> > > > 
> > > > 
> > > > And it stops there.  I would expect the following lines to show
> > > > up
> > > > next
> > > > but they never do. They do show up for SLES12 (SP2 & 3) and CaaS.
> > > > For
> > > > SLE15 they do not.  
> > > > 
> > > > 
> > > > ---BEGIN EXPECTED OUTPUT-----
> > > > eth0: network config created
> > > > Sending DHCP request to eth0
> > > > ok, ip = xxx.xxx.xxx.xxx/xx
> > > > ---END EXPECTED OUTPUT-----
> > > > 
> > > > Also, I purposly changed the IP address in my SLES 12 entry to
> > > > make
> > > > it
> > > > not find the install media so I could see if this was before or
> > > > after
> > > > trying to load the install image. It still output the above three
> > > > lines
> > > > before hanging so this leads me to believe this is a function of
> > > > initrd????
> > > > 
> > > > I am not sure where to turn next. I have been google'ing all
> > > > morning
> > > > with no luck, and also tried searching past posts here as well.
> > > > 
> > > > I also get the same results with Leap 15 (build 151.1) 
> > > > 
> > > > Thanks.
> > > > Wayne
> > > > 
> > > > 
> > > 
> > > _______________________________________________
> > > sle-beta mailing list
> > > sle-beta at lists.suse.com
> > > http://lists.suse.com/mailman/listinfo/sle-beta
> > 
> > 

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From snwint at suse.de  Fri Mar  9 08:02:17 2018
From: snwint at suse.de (Steffen Winterfeldt)
Date: Fri, 9 Mar 2018 16:02:17 +0100 (CET)
Subject: [sle-beta] SLE15 RC1 unable to pxe boot to install image
In-Reply-To: <20180309142850.GA29718@suse.de>
References: <1520538740.26756.23.camel@suse.com>
	<1520543348.26756.27.camel@suse.com>
	<20180309052958.GA12467@suse.de>
	<1520603656.29644.5.camel@suse.com>
	<20180309142850.GA29718@suse.de>
Message-ID: <alpine.LSU.2.11.1803091600420.3169@zrgpnys.fhfr.qr>

On Friday 2018-03-09 15:28, Thorsten Kukuk wrote:

> On Fri, Mar 09, Wayne Patton wrote:
>
>> Thorsten - Yes I can install it with the dvd/iso images.
>
> Then please create a bug report, I have no idea what is special
> with VMware, I don't use that.

Reported a number of times already, e.g. bsc #1082147. Basically a
kernel issue.


Steffen


>
>  Thorsten
>
>> Wayne
>>
>>
>>
>> On Fri, 2018-03-09 at 06:29 +0100, Thorsten Kukuk wrote:
>>> On Thu, Mar 08, Wayne Patton wrote:
>>>
>>>> Update: Both options I presented below work in KVM with no changes.
>>>> I
>>>> created a network in KVM, a blank VM, enabled DHCP on that network
>>>> using dnsmasq and it worked.
>>>>
>>>> So is this a network driver issue??? Something else?
>>>
>>> Can you install this VMWare machines with a DVD?
>>>
>>>   Thorsten
>>>
>>>> WP
>>>>
>>>>
>>>> On Thu, 2018-03-08 at 19:52 +0000, Wayne Patton wrote:
>>>>> I am unable to pxe boot to the install image for SLES 15 RC1.
>>>>>
>>>>> I am using VMware Workstation version 14. I am able to pxe boot
>>>>> SLES
>>>>> 12
>>>>> SP2 & SP3 and CaaS 2 just fine using the same setup.
>>>>>
>>>>> I have two options in my pxelinux.cfg/default file for SLE 15.
>>>>> The
>>>>> first is modeled after my SLES 12 entry and the second is taken
>>>>> from
>>>>> the example files that I found by installing the tftpboot-
>>>>> installation-
>>>>> SLE-15-x86_64 package on another SLES 15 VM.
>>>>>
>>>>> For the first option, like SLE 12, I copied the initrd and linux
>>>>> files
>>>>> from the install media to my tftp server into
>>>>> /srv/tftpboot/sles/15/ga/x86_64/
>>>>>
>>>>> For the second option, I copied the entire /srv/tftpboot/SLE-15-
>>>>> x86_64/
>>>>> tree structure from the tftpboot-installation-SLE-15-x86_64
>>>>> package
>>>>> to
>>>>> my tftpserver, which is used in the second option below.
>>>>>
>>>>> I get the same results with both options.
>>>>>
>>>>> UI menu.c32
>>>>>
>>>>> LABEL sles15-rc1-x86_64 - like 12
>>>>>   MENU LABEL SLES 15 RC1 x86_64 - like 12
>>>>>   KERNEL sles/15/ga/x86_64/linux
>>>>>   APPEND initrd=sles/15/ga/x86_64/initrd install=http://192.168.1
>>>>> 22.1
>>>>> /i
>>>>> nstall/sles/15/ga/x86_64/dvd1/
>>>>>
>>>>> LABEL sles15-rc1-x86_64 - 15 tftpboot package
>>>>>   MENU LABEL SLES 15 RC1 x86_64 - 15 tftpboot package
>>>>>   KERNEL SLE-15-x86_64/boot/x86_64/loader/linux
>>>>>   APPEND initrd=SLE-15-x86_64/boot/x86_64/loader/initrd
>>>>> instsys=tftp://
>>>>> 192.168.122.1/SLE-15-x86_64/boot/x86_64/root install=http://192.1
>>>>> 68.1
>>>>> 22
>>>>> .1/install/sles/15/ga/x86_64/dvd1/
>>>>>
>>>>> On the console, I get the following:
>>>>> ---BEGIN OUTPUT--------
>>>>> Starting udev... ok
>>>>> Loading basic drivers   ok
>>>>> Starting hardware detection .. ok
>>>>> (If a driver is not working for you, try booting with
>>>>> brokenmodules=driver_name
>>>>>
>>>>> VMware SATA AHCI controller
>>>>>   drivers: ahci*
>>>>> VMware Virtual Machine Chipset
>>>>>   drivers: ata_piix*, ata_generic, pata_acpi
>>>>> VMware LSI Logic Parallel SCSI Controller
>>>>>   drivers: mptspi*
>>>>> VMware PRO/1000 MT Single Port Adapter
>>>>>   drivers: e1000*
>>>>> ---END OUTPUT--------
>>>>>
>>>>>
>>>>> And it stops there.  I would expect the following lines to show
>>>>> up
>>>>> next
>>>>> but they never do. They do show up for SLES12 (SP2 & 3) and CaaS.
>>>>> For
>>>>> SLE15 they do not.
>>>>>
>>>>>
>>>>> ---BEGIN EXPECTED OUTPUT-----
>>>>> eth0: network config created
>>>>> Sending DHCP request to eth0
>>>>> ok, ip = xxx.xxx.xxx.xxx/xx
>>>>> ---END EXPECTED OUTPUT-----
>>>>>
>>>>> Also, I purposly changed the IP address in my SLES 12 entry to
>>>>> make
>>>>> it
>>>>> not find the install media so I could see if this was before or
>>>>> after
>>>>> trying to load the install image. It still output the above three
>>>>> lines
>>>>> before hanging so this leads me to believe this is a function of
>>>>> initrd????
>>>>>
>>>>> I am not sure where to turn next. I have been google'ing all
>>>>> morning
>>>>> with no luck, and also tried searching past posts here as well.
>>>>>
>>>>> I also get the same results with Leap 15 (build 151.1)
>>>>>
>>>>> Thanks.
>>>>> Wayne
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> sle-beta mailing list
>>>> sle-beta at lists.suse.com
>>>> http://lists.suse.com/mailman/listinfo/sle-beta
>>>
>>>
>
> -- 
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta
>

-- 
Give orange me give eat orange me eat orange give me eat orange give me you.
(chimp Nim, using sign language)

From vmoutoussamy at suse.com  Fri Mar  9 09:03:45 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Fri, 9 Mar 2018 17:03:45 +0100
Subject: [sle-beta] RC1 UPDATE - Looking good
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076D9AC@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076D9AC@daeexmbx1.eur.ad.sag>
Message-ID: <098CB384-FCA5-43A7-8682-F45B2C155D7F@suse.com>

Hi,
> 
> On 8 Mar 2018, at 11:08, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
> 
> Grand Morning,
> 
> If one has not made the following amend before running an UPDATE
> solver.onlyRequires = true
> installRecommends=false # or commented
Just to give others a little bit of context:

Regarding solver.onlyRequires and installRecommends the default settings are the
same for SLES 12 SP3 and SLES 15.

# grep solver.onlyRequires /etc/zypp/zypp.conf
# solver.onlyRequires = false

in /etc/zypp/zypper.conf:
## Install soft dependencies (recommended packages)
##
## CAUTION: The system wide default for all libzypp based applications (zypper,
## yast, pk,..) is defined in  /etc/zypp/zypp.conf(solver.onlyRequires)  and it
## will per default install recommended packages. It is NOT RECOMMENDED to define
## this value here for zypper exclusively, unless you are very certain that you
## want zypper to behave different than other libzypp based packagemanagement software
## on your system.
##
## Valid values: boolean
## Default value: follow zypp.conf(solver.onlyRequires)
##
# installRecommends = yes

> How can one remove all the not needed bits and bobs with zypper or Yast2 or does one have to do the whole thing again ?
First thing first, could you tell us what was the reason to change the default
settings?

Second, do you mean how could you remove all installed packages that were
considered as ?recommended packages??

Not sure if this is the best approach but I have just come up with this to list
all installed recommended packages:
# for i in `zypper pa -i | awk -F '|' '{print $3}'`; do zypper info --recommends $i | grep -A 10 Recommends >> installed-recommended-packages.txt; done

This can may take a long time to be executed...

- zypper pa -i | awk -F '|' '{print $3}? :
List all installed package in your system and only their name.
- zypper info --recommends $i :
add the recommended packages of a given package in the info output
- grep -A 10 Recommends:
Dirty way to only show the ?Recommends?, so it will only save the potential
max of 10 recommended packages (I dunno if any has more than 10?) and not the entire
zypper info output, for better readability.

Last, the general advice when you want to have a system with very limited
packages set is to (fresh) install a SLES minimal or use JeOS, then you can
change the default setting of ?solver.onlyRequires? if you really want to after
reckoning that this might cause side effects.
> 
> Many Thanks
> 
> __R

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/269d7ff2/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/269d7ff2/attachment.sig>

From vmoutoussamy at suse.com  Fri Mar  9 09:28:06 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Fri, 9 Mar 2018 17:28:06 +0100
Subject: [sle-beta] yast CA module gone in SLE 15?
In-Reply-To: <e0954297-f6cd-d722-0307-579cd4f55b7f@softergee.si>
References: <e0954297-f6cd-d722-0307-579cd4f55b7f@softergee.si>
Message-ID: <CEEFC45B-7C03-49C4-81EC-A086429B0F5C@suse.com>

Hi,

Well "yast2 ca-management is a wild combination of yast(ruby) yast (perl)
c++(swig) and and c++ lib?, and the maintenance of it was becoming a real
challenge.

We are working on an alternative for yast2 ca-management, I hope to be able to
provide more details soon.

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 7 Mar 2018, at 18:32, Toma? Bor?tnar, Softergee <tomaz.borstnar at softergee.si> wrote:
> 
> Hello!
> 
> Why would this useful thing be gone from SLE 15?
> 
> Toma?
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/bdae8a2d/attachment.sig>

From vmoutoussamy at suse.com  Fri Mar  9 09:37:14 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Fri, 9 Mar 2018 17:37:14 +0100
Subject: [sle-beta] SLES gnome-session-failed for SLES 12sp3 -> 15 via
 zypper dup
In-Reply-To: <7805E5E9-D8B3-41F4-B98F-D44CDA50E276@emc.com>
References: <7805E5E9-D8B3-41F4-B98F-D44CDA50E276@emc.com>
Message-ID: <57546213-8B27-4091-8BC6-00DEF3B46CF5@suse.com>

Hi,

?zypper dup? is not a supported method to upgrade to Major SLE version,
thus not supported to upgrade from SLES 12 SP3 to SLES 15.

This is only supported for Service Pack Migration of a SLE version, and note
even in this case we recommend to use ?zypper migration? instead
https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.migr.zypper.onlinemigr <https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.migr.zypper.onlinemigr>

Note:
This is not new with SLE15, the same statement are true for migrating from SLE
11 to SLE 12. cf https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.methods <https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.methods>

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 8 Mar 2018, at 20:59, Bahi, David <David.Bahi at dell.com <mailto:David.Bahi at dell.com>> wrote:
> 
> Is this zypper dup path bz worthy?
> 
> prompt > systemctl isolate graphical.target
> 
> Only gets the GDM up as well - doesn't allow me to login.
> 
> bahid at hw-and-os-97:~> zypper se -s -i wayland gnome-session gnome-shell-classic
> Loading repository data...
> Reading installed packages...
> 
> S  | Name                          | Type    | Version     | Arch   | Repository
> ---+-------------------------------+---------+-------------+--------+----------------------------
> i+ | gnome-session                 | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
> i  | gnome-session-core            | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
> i  | gnome-session-default-session | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
> i+ | gnome-shell-classic           | package | 3.26.2-4.1  | noarch | Module-Desktop-Applications
> i  | libgstwayland-1_0-0           | package | 1.12.4-3.1  | x86_64 | Module-Desktop-Applications
> i  | libwayland-client0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
> i  | libwayland-cursor0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
> i  | libwayland-egl1               | package | 18.0.0-20.1 | x86_64 | Module-Basesystem
> i  | libwayland-server0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
> 
> 
> 
> VNC session is just black... Is this a Wayland / X-display permissions issue ? Here's the log.
> 
> bahid at hw-and-os-97:~> cat ~/.vnc/hw-and-os-97\:1.log
> 
> Xvnc TigerVNC 1.8.0 - built ??? ?? ???? ??:??:??
> Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
> See http://www.tigervnc.org <http://www.tigervnc.org/> for information on TigerVNC.
> Underlying X server release 11906000, The X.Org <http://x.org/> Foundation
> 
> 
> Thu Mar  8 14:27:47 2018
>  vncext:      VNC extension running!
>  vncext:      Listening for VNC connections on all interface(s), port 5901
>  vncext:      created VNC server for screen 0
> /etc/X11/xim: Checking whether an input method should be started.
> sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
> INPUT_METHOD is not set or empty (no user selected input method).
> Trying to start a default input method for the locale en_US.UTF-8 ...
> There is no default input method for the current locale.
> Dummy input method "none" (do not use any fancy input method by default)
> gnome-session-binary[1979]: WARNING: software acceleration check failed: Child process exited with code 1
> Unable to init server: Could not connect: Connection refused
> 
> ** (gnome-session-failed:2029): WARNING **: Cannot open display:
> 
> Thu Mar  8 14:27:53 2018
>  Connections: accepted: 10.138.8.158::55122
>  SConnection: Client needs protocol version 3.8
> 
> Thu Mar  8 14:27:56 2018
>  SConnection: Client requests security type VncAuth(2)
>  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
>  VNCSConnST:  Client pixel format depth 32 (32bpp) little-endian rgb max
>               255,255,255 shift 16,8,0
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com <mailto:sle-beta at lists.suse.com>
> http://lists.suse.com/mailman/listinfo/sle-beta <http://lists.suse.com/mailman/listinfo/sle-beta>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/da6ff6d8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/da6ff6d8/attachment.sig>

From David.Bahi at dell.com  Fri Mar  9 12:20:17 2018
From: David.Bahi at dell.com (Bahi, David)
Date: Fri, 9 Mar 2018 19:20:17 +0000
Subject: [sle-beta] SLES gnome-session-failed for SLES 12sp3 -> 15 via
 zypper dup
In-Reply-To: <57546213-8B27-4091-8BC6-00DEF3B46CF5@suse.com>
References: <7805E5E9-D8B3-41F4-B98F-D44CDA50E276@emc.com>
	<57546213-8B27-4091-8BC6-00DEF3B46CF5@suse.com>
Message-ID: <A46165CC-3B02-416A-BF0A-0229E999E459@emc.com>

A fresh install, using the Installer ISO and SLP for Packages + SLED / base / desktop_applications, made no difference.

Same result with a vncserver invocation (5901 - not the yast2 enable remote administration port 5900 thing) :

"Connection refused"

"cannot open display".

Nothing to do with firewall and this bz:

https://bugzilla.suse.com/show_bug.cgi?id=1081952

as firewall was entirely disabled for this attempt (because there's no Yast2 tool for configuring it yet).


Opened:

https://bugzilla.suse.com/show_bug.cgi?id=1084756

db

On Mar 9, 2018, at 11:37, Vincent Moutoussamy <vmoutoussamy at suse.com<mailto:vmoutoussamy at suse.com>> wrote:

Hi,

?zypper dup? is not a supported method to upgrade to Major SLE version,
thus not supported to upgrade from SLES 12 SP3 to SLES 15.

This is only supported for Service Pack Migration of a SLE version, and note
even in this case we recommend to use ?zypper migration? instead
https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.migr.zypper.onlinemigr

Note:
This is not new with SLE15, the same statement are true for migrating from SLE
11 to SLE 12. cf https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.methods

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

On 8 Mar 2018, at 20:59, Bahi, David <David.Bahi at dell.com<mailto:David.Bahi at dell.com>> wrote:

Is this zypper dup path bz worthy?

prompt > systemctl isolate graphical.target

Only gets the GDM up as well - doesn't allow me to login.

bahid at hw-and-os-97:~> zypper se -s -i wayland gnome-session gnome-shell-classic
Loading repository data...
Reading installed packages...

S  | Name                          | Type    | Version     | Arch   | Repository
---+-------------------------------+---------+-------------+--------+----------------------------
i+ | gnome-session                 | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
i  | gnome-session-core            | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
i  | gnome-session-default-session | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
i+ | gnome-shell-classic           | package | 3.26.2-4.1  | noarch | Module-Desktop-Applications
i  | libgstwayland-1_0-0           | package | 1.12.4-3.1  | x86_64 | Module-Desktop-Applications
i  | libwayland-client0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
i  | libwayland-cursor0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
i  | libwayland-egl1               | package | 18.0.0-20.1 | x86_64 | Module-Basesystem
i  | libwayland-server0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem



VNC session is just black... Is this a Wayland / X-display permissions issue ? Here's the log.

bahid at hw-and-os-97:~> cat ~/.vnc/hw-and-os-97\:1.log

Xvnc TigerVNC 1.8.0 - built ??? ?? ???? ??:??:??
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org<http://www.tigervnc.org/> for information on TigerVNC.
Underlying X server release 11906000, The X.Org<http://x.org/> Foundation


Thu Mar  8 14:27:47 2018
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
gnome-session-binary[1979]: WARNING: software acceleration check failed: Child process exited with code 1
Unable to init server: Could not connect: Connection refused

** (gnome-session-failed:2029): WARNING **: Cannot open display:

Thu Mar  8 14:27:53 2018
 Connections: accepted: 10.138.8.158::55122
 SConnection: Client needs protocol version 3.8

Thu Mar  8 14:27:56 2018
 SConnection: Client requests security type VncAuth(2)
 VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
 VNCSConnST:  Client pixel format depth 32 (32bpp) little-endian rgb max
              255,255,255 shift 16,8,0

_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com<mailto:sle-beta at lists.suse.com>
http://lists.suse.com/mailman/listinfo/sle-beta


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/346b4900/attachment.htm>

From David.Bahi at dell.com  Fri Mar  9 12:33:37 2018
From: David.Bahi at dell.com (Bahi, David)
Date: Fri, 9 Mar 2018 19:33:37 +0000
Subject: [sle-beta] SLES gnome-session-failed for SLES 12sp3 -> 15 via
 zypper dup
In-Reply-To: <A46165CC-3B02-416A-BF0A-0229E999E459@emc.com>
References: <7805E5E9-D8B3-41F4-B98F-D44CDA50E276@emc.com>
	<57546213-8B27-4091-8BC6-00DEF3B46CF5@suse.com>
	<A46165CC-3B02-416A-BF0A-0229E999E459@emc.com>
Message-ID: <334D9F34-9890-478B-96F8-9DF6299A8B52@emc.com>


> On Mar 9, 2018, at 14:20, Bahi, David <David.Bahi at dell.com> wrote:
> 
> (because there's no Yast2 tool for configuring it yet).

Mistake from a previous broken install - sorry for the mis-direct here.


From kastl at b1-systems.de  Fri Mar  9 13:01:45 2018
From: kastl at b1-systems.de (Johannes Kastl)
Date: Fri, 9 Mar 2018 21:01:45 +0100
Subject: [sle-beta] docbook2X missing in SLES15 on OBS?
Message-ID: <15671733-28d7-ab03-9b7c-f347440d4ad8@b1-systems.de>

Hi everybody,

when trying to build lxc against SLES15 in OBS, I get an "unresolvable"
due to missing docbook2x:

"nothing provides docbook-utils, nothing provides docbook2x"

https://build.opensuse.org/package/show/home:ojkastl_buildservice:LXC_Vanilla_stable-1.0/lxc

Is this just a (temporary) issue on the openSUSE OBS, or is this package
really missing in SLES15? Is my build target for SLES15 missing
something? Seems like SLES12 has this package, as I can successfully
build for SLES12...

Kind Regards,
Johannes

-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: kastl at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 864 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180309/23607eab/attachment.sig>

From Dick.Waite at softwareag.com  Sat Mar 10 04:49:26 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Sat, 10 Mar 2018 11:49:26 +0000
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>

Grand Saturday,

You clone rjw08-12-3-0 to rjw08-15-0-0 and hostnamectl to the new host name. It's got a new IP so one could think rjw08-12-3-0 and rjw08-15-0-0 are two unique virtual machines, why even their UUID's are different.....

On rjw08-15-0-0 I was surprised when a SUSEConnect --status-text gave output...

On the display behind me I had a ssc.suse.com running, I used the systems display to see what "rjw08" virtual machines were doing, rjw08-12-3-0 had an update time stamp, this good machine was very much off-line, it had not been used for many a day. There was no entry for rjw08-15-3-0, magic thinks I ..

A look at /etc/zypp/credentials.d/SCCcredentials shows USERNAME and PASSWORD of the good old rjw08-123-0 -- now yes a --cleanup will remove that name, but I would also expect a check to make sure you are working on the rjw08-15-0-0 host with it's UUID and if you get back a different host / UUID then a WARNING telling the good person, you are not interacting with your current host on the SCC. Maybe part of "hostnamectl --set-hostname" has a similar effect as  --cleanup, having two machines with the same hostname is the same issues of having code with the same name...

Knowing this I have now Migrated a number of virtual machines, but I think that simple check of "is this the right host?" would have save a lot of heartache. You can also have two machine in the SCC with the same hostname, different UUID's and different SCC USERNAME and PASSWORD, why would you wont that ?

Why not use the machines UUID as the SCC USERNAME, then you are sure to be sure your talking to who you think you are, well better than now.

Now for an afternoon a good Rugby.

__R

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180310/2c17c2a2/attachment.htm>

From kukuk at suse.de  Sat Mar 10 05:39:22 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Sat, 10 Mar 2018 13:39:22 +0100
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>
Message-ID: <20180310123922.GA32127@suse.de>

On Sat, Mar 10, Waite, Dick (External) wrote:

> A look at /etc/zypp/credentials.d/SCCcredentials shows USERNAME and PASSWORD of
> the good old rjw08-123-0 -- now yes a --cleanup will remove that name, but I
> would also expect a check to make sure you are working on the rjw08-15-0-0 host
> with it's UUID and if you get back a different host / UUID then a WARNING
> telling the good person, you are not interacting with your current host on the
> SCC.

Exactly this is for what SUSEConnect --cleanup is there: that you can
clone a machine and remove all registration references to register it new.
So a check for the "right machine" would be pretty useless.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From Dick.Waite at softwareag.com  Sat Mar 10 08:25:05 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Sat, 10 Mar 2018 15:25:05 +0000
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <20180310123922.GA32127@suse.de>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>,
	<20180310123922.GA32127@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076E739@daeexmbx1.eur.ad.sag>

Afternoon Thorsten,

Before you update a field in a database (SCC) you check, and check again that it's legal to do so. The host-names should match, in my case we had rjw08-12-3-0 as the host record and it's being updated by a host-name rjw08-15-0-0. Now at RC1 the understanding of the SUSEConnect is there for is getting clear but at Beta6 it was not. I don't see why the hostnamectl set-hostname can not clear the "old" stuff in /etc/zypp... It's quite often we will change the host-name of a virtual machine and now we have to "remember" we need to update the SCC database. We can also have two entries in the scc database with the same host-name, but different UUID's. How do you know which one is going to be updated.

We have now got a number of SLES12-SP3 machines that have to be restored as their SCC database entries have been over written. Having a SCC database means you have a new set of rules on how to handle writes and updates to it.

Now we know I'm sure we will remember each time you clone or use hostnamectl set-hostname you have to run a SUSEConnect --cleanup. *BUT* there are going to be a few times when it's not run and the SCC gets the wrong entry. Database don't work that way....

On the other hand that's what Beta testing is all about. We have identified a number of items around the migrate and SCC area, so looking forward to see how they are fixed for RC2

I think for the Docu, Very large and BOLD letters, if you clone or change the host-name until a better solution you must remember to "--cleanup" and I expect 98% of the time the good people will...

At the half Ireland 14 - 3 Scotland

__R
________________________________________
From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
Sent: 10 March 2018 13:39
To: sle-beta at lists.suse.com
Subject: Re: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup

On Sat, Mar 10, Waite, Dick (External) wrote:

> A look at /etc/zypp/credentials.d/SCCcredentials shows USERNAME and PASSWORD of
> the good old rjw08-123-0 -- now yes a --cleanup will remove that name, but I
> would also expect a check to make sure you are working on the rjw08-15-0-0 host
> with it's UUID and if you get back a different host / UUID then a WARNING
> telling the good person, you are not interacting with your current host on the
> SCC.

Exactly this is for what SUSEConnect --cleanup is there: that you can
clone a machine and remove all registration references to register it new.
So a check for the "right machine" would be pretty useless.

  Thorsten

--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From Dick.Waite at softwareag.com  Sun Mar 11 21:18:30 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Mon, 12 Mar 2018 03:18:30 +0000
Subject: [sle-beta] UUDI not tested - Wrong UUID updated.
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076ED9B@daeexmbx1.eur.ad.sag>

Grand New Monday Thorsten,

Agreed SUSEConnect --cleanup just acts on the client. But if that command has not been issued then other SUSEConnect commands issued by the cloned client will not act on the clone but on the clones Mother. I'm saying if you check the UUID of the caller of SUSEConnect is the same as the entry in the SCC database then you know the --cleanup has been done but it it's not, it's the clones Mother, then you issue an error and maybe in the response suggest --cleanup needs to be done.  We have a number of SCC Mothers entries that need work after being molested by their children where --cleanup had not been done. It a new command and will be forgotten.
"if it can go wrong, it will go wrong and the wrong time." 

Have a very good day.

__R

________________________________________
From: Thorsten Kukuk [kukuk at suse.de]
Sent: 10 March 2018 17:11
To: Waite, Dick (External)
Cc: sle-beta at lists.suse.com
Subject: Re: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup

Hi,

On Sat, Mar 10, Waite, Dick (External) wrote:

> Afternoon Thorsten,
>
> Before you update a field in a database (SCC) you check, and check again that it's legal to do so. The host-names should match, in my case we had rjw08-12-3-0 as the host record and it's being updated by a host-name rjw08-15-0-0. Now at RC1 the understanding of the SUSEConnect is there for is getting clear but at Beta6 it was not. I don't see why the hostnamectl set-hostname can not clear the "old" stuff in /etc/zypp... It's quite often we will change the host-name of a virtual machine and now we have to "remember" we need to update the SCC database. We can also have two entries in the scc database with the same host-name, but different UUID's. How do you know which one is going to be updated.

According to the documentation, SUSEConnect --cleanup should not
update a database entry on SCC, but remove the files on the host.
This is not --deregister.
And hostnames are completly irrelevant. You don't register hostnames,
you register machines. hostnames can change in a dhcp environment with
every reboot, if a hostname does exist at all for this dhcp client.

  Thorsten


>
> We have now got a number of SLES12-SP3 machines that have to be restored as their SCC database entries have been over written. Having a SCC database means you have a new set of rules on how to handle writes and updates to it.
>
> Now we know I'm sure we will remember each time you clone or use hostnamectl set-hostname you have to run a SUSEConnect --cleanup. *BUT* there are going to be a few times when it's not run and the SCC gets the wrong entry. Database don't work that way....
>
> On the other hand that's what Beta testing is all about. We have identified a number of items around the migrate and SCC area, so looking forward to see how they are fixed for RC2
>
> I think for the Docu, Very large and BOLD letters, if you clone or change the host-name until a better solution you must remember to "--cleanup" and I expect 98% of the time the good people will...
>
> At the half Ireland 14 - 3 Scotland
>
> __R
> ________________________________________
> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
> Sent: 10 March 2018 13:39
> To: sle-beta at lists.suse.com
> Subject: Re: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
>
> On Sat, Mar 10, Waite, Dick (External) wrote:
>
> > A look at /etc/zypp/credentials.d/SCCcredentials shows USERNAME and PASSWORD of
> > the good old rjw08-123-0 -- now yes a --cleanup will remove that name, but I
> > would also expect a check to make sure you are working on the rjw08-15-0-0 host
> > with it's UUID and if you get back a different host / UUID then a WARNING
> > telling the good person, you are not interacting with your current host on the
> > SCC.
>
> Exactly this is for what SUSEConnect --cleanup is there: that you can
> clone a machine and remove all registration references to register it new.
> So a check for the "right machine" would be pretty useless.
>
>   Thorsten
>
> --
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta
>
> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
>

--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From vmoutoussamy at suse.com  Mon Mar 12 07:49:47 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Mon, 12 Mar 2018 14:49:47 +0100
Subject: [sle-beta] docbook2X missing in SLES15 on OBS?
In-Reply-To: <15671733-28d7-ab03-9b7c-f347440d4ad8@b1-systems.de>
References: <15671733-28d7-ab03-9b7c-f347440d4ad8@b1-systems.de>
Message-ID: <27B4ADC0-864D-4EB1-B372-7D948D4D12EE@suse.com>

Hi,

Please create a bug report for this and post the bug number here.
Some docbook packages are clearly missing.

Thanks,

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> On 9 Mar 2018, at 21:01, Johannes Kastl <kastl at b1-systems.de> wrote:
> 
> Hi everybody,
> 
> when trying to build lxc against SLES15 in OBS, I get an "unresolvable"
> due to missing docbook2x:
> 
> "nothing provides docbook-utils, nothing provides docbook2x"
> 
> https://build.opensuse.org/package/show/home:ojkastl_buildservice:LXC_Vanilla_stable-1.0/lxc
> 
> Is this just a (temporary) issue on the openSUSE OBS, or is this package
> really missing in SLES15? Is my build target for SLES15 missing
> something? Seems like SLES12 has this package, as I can successfully
> build for SLES12...
> 
> Kind Regards,
> Johannes
> 
> --
> Johannes Kastl
> Linux Consultant & Trainer
> Tel.: +49 (0) 151 2372 5802
> Mail: kastl at b1-systems.de
> 
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/ed82520b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/ed82520b/attachment.sig>

From vmoutoussamy at suse.com  Mon Mar 12 07:54:29 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Mon, 12 Mar 2018 14:54:29 +0100
Subject: [sle-beta] Package openldap2-back-meta is missing
In-Reply-To: <5AA390080200004D0002D600@mail.triples.at>
References: <5AA390080200004D0002D600@mail.triples.at>
Message-ID: <EF040FC9-68CB-4BE7-9A07-9F8B181BE895@suse.com>

Hi,

Please create a bug report for this and post the bug number here.
Well it?s not really a library but yes it might fall into ldap tools in the
legacy module for SLE15.

Thanks,

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager


> On 10 Mar 2018, at 08:58, Peter jahn <pjahn at triples.at> wrote:
> 
> The Release Notes of SLE15 mention that the openLDAP libraries are still available.
> 
> On SLES12 there was a package called "openldap2-back-meta" which is not available in SLES15 RC1 anymore. This backend is an important piece of openLDAP which is needed to build meta directories. Many admins are using this backend for connections with Actice Directory, eDirectory, 389-ds and a lot of other directories
> 
> 
> 
> zypper output on SLES12
> 
> S  | Name                   | Summary                                                | Type
> ---+------------------------+--------------------------------------------------------+-----------
> i+ | openldap2              | The OpenLDAP Server                                    | package
>    | openldap2              | The OpenLDAP Server                                    | srcpackage
>    | openldap2-back-meta    | OpenLDAP Meta Back-End                                 | package
>    | openldap2-back-perl    | OpenLDAP Perl Back-End                                 | package
> i  | openldap2-client       | OpenLDAP client utilities                              | package
>    | openldap2-devel        | Libraries, Header Files and Documentation for OpenLDAP | package
>    | openldap2-devel-static | Static libraries for the OpenLDAP libraries            | package
> 
> 
> 
> zypper output on SLES15
> 
> S  | Name                   | Summary                                                     | Type
> ---+------------------------+-------------------------------------------------------------+--------
> i+ | openldap2              | An open source implementation of the Lightweight Director-> | package
> i  | openldap2-client       | OpenLDAP client utilities                                   | package
> i  | openldap2-devel        | Libraries, Header Files and Documentation for OpenLDAP      | package
>    | openldap2-devel-static | Static libraries for the OpenLDAP libraries                 | package
> 
> 
> 
> 
> Mit freundlichen Gruessen / Kind regards
> 
> JAHN Peter, MSc
> SCI, SCE, MCNE, CNI, MCSE, MAI, CTT, CLP, CCNA, SCA
> Mobil: +43(0)664 4692000, E-Mail: PJahn at TripleS.at <mailto:PJahn at TripleS.at>
>  <http://www.linuxcampus.net/linuxcampus-net-wir-im-ueberblick/video-linuxcampus-im-ueberblick><IMAGE.png> <https://www.linuxcampus.net/linuxcampus-net-wir-im-ueberblick/video-linuxcampus-im-ueberblick>
> Click on the Logo for seeing our LinuxCampus.net <https://www.linuxcampus.net/linuxcampus-net-wir-im-ueberblick/video-linuxcampus-im-ueberblick> Video
> 
> 
> This e-mail message has been scanned for Viruses and Content
> Diese Nachricht und allfaellige angehaengte Dokumente sind vertraulich und nur fuer den/die Adressaten bestimmt. Sollten Sie nicht der beabsichtigte Empfaenger sein, ist jede Offenlegung, Weiterleitung oder sonstige Verwendung dieser Information nicht gestattet. In diesem Fall bitten wir Sie, den Absender zu verstaendigen und die Information zu vernichten. Fuer Uebermittlungsfehler oder sonstige Irrtuemer bei Uebermittlung besteht keine Haftung.
> 
> This message and any attached files are confidential and intended solely for the addressee(s). Any publication, transmission or other use of the information by a person or entity other than the intended addressee is prohibited. If you receive this in error please contact the sender and delete the material. The sender does not accept liability for any errors or missions as a result of the transmission
> 
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/304044e2/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/304044e2/attachment.sig>

From hschmidt at suse.de  Mon Mar 12 07:53:07 2018
From: hschmidt at suse.de (=?ISO-8859-1?Q?Hern=E1n?= Schmidt)
Date: Mon, 12 Mar 2018 14:53:07 +0100
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>
Message-ID: <1520862787.4384.84.camel@suse.de>

Hi Dick,

Thanks for the write up and the suggestion.

> Why not use the machines UUID as the SCC USERNAME, then you are sure
> to be sure your talking to who you think you are, well better than
> now. 

Yes, that would be a good solution. Unfortunately, SUSEConnect needs to
work on a large variety of devices, and we found that a large portion
of devices do not provide a UUID. To keep things simple for all cases,
we decided to generate a system "login" which gets saved to the
filesystem (the SCCcredentials file).
For that reason it's necessary to call --cleanup on the cloned system,
or alternatively, call --cleanup on the original system before saving
the snapshot, so that all clones are "clean" already.

Best regards,
-- 
Hern?n Schmidt
SUSE Customer Center

SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
HRB 21284 (AG N?rnberg) 

From vmoutoussamy at suse.com  Mon Mar 12 09:01:33 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Mon, 12 Mar 2018 16:01:33 +0100
Subject: [sle-beta] SLES gnome-session-failed for SLES 12sp3 -> 15 via
 zypper dup
In-Reply-To: <A46165CC-3B02-416A-BF0A-0229E999E459@emc.com>
References: <7805E5E9-D8B3-41F4-B98F-D44CDA50E276@emc.com>
	<57546213-8B27-4091-8BC6-00DEF3B46CF5@suse.com>
	<A46165CC-3B02-416A-BF0A-0229E999E459@emc.com>
Message-ID: <FCD5D924-DB8F-4368-B099-7B1128B886C7@suse.com>

Hi,
> On 9 Mar 2018, at 20:20, Bahi, David <David.Bahi at dell.com> wrote:
> 
> A fresh install, using the Installer ISO and SLP for Packages + SLED / base / desktop_applications, made no difference.
> 
> Same result with a vncserver invocation (5901 - not the yast2 enable remote administration port 5900 thing) :
> 
> "Connection refused"
> 
> "cannot open display".
> 
> Nothing to do with firewall and this bz:
> 
> https://bugzilla.suse.com/show_bug.cgi?id=1081952 <https://bugzilla.suse.com/show_bug.cgi?id=1081952>
> 
> as firewall was entirely disabled for this attempt (because there's no Yast2 tool for configuring it yet).
> 
> 
> Opened:
> 
> https://bugzilla.suse.com/show_bug.cgi?id=1084756 <https://bugzilla.suse.com/show_bug.cgi?id=1084756>
> 
> db

Well thanks, creating the bug report was the right thing to do!

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> 
>> On Mar 9, 2018, at 11:37, Vincent Moutoussamy <vmoutoussamy at suse.com <mailto:vmoutoussamy at suse.com>> wrote:
>> 
>> Hi,
>> 
>> ?zypper dup? is not a supported method to upgrade to Major SLE version,
>> thus not supported to upgrade from SLES 12 SP3 to SLES 15.
>> 
>> This is only supported for Service Pack Migration of a SLE version, and note
>> even in this case we recommend to use ?zypper migration? instead
>> https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.migr.zypper.onlinemigr <https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.migr.zypper.onlinemigr>
>> 
>> Note:
>> This is not new with SLE15, the same statement are true for migrating from SLE
>> 11 to SLE 12. cf https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.methods <https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.methods>
>> 
>> Regards,
>> --
>> Vincent Moutoussamy
>> SUSE Beta Program and SDK Project Manager
>> 
>>> On 8 Mar 2018, at 20:59, Bahi, David <David.Bahi at dell.com <mailto:David.Bahi at dell.com>> wrote:
>>> 
>>> Is this zypper dup path bz worthy?
>>> 
>>> prompt > systemctl isolate graphical.target
>>> 
>>> Only gets the GDM up as well - doesn't allow me to login.
>>> 
>>> bahid at hw-and-os-97:~> zypper se -s -i wayland gnome-session gnome-shell-classic
>>> Loading repository data...
>>> Reading installed packages...
>>> 
>>> S  | Name                          | Type    | Version     | Arch   | Repository
>>> ---+-------------------------------+---------+-------------+--------+----------------------------
>>> i+ | gnome-session                 | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
>>> i  | gnome-session-core            | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
>>> i  | gnome-session-default-session | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
>>> i+ | gnome-shell-classic           | package | 3.26.2-4.1  | noarch | Module-Desktop-Applications
>>> i  | libgstwayland-1_0-0           | package | 1.12.4-3.1  | x86_64 | Module-Desktop-Applications
>>> i  | libwayland-client0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
>>> i  | libwayland-cursor0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
>>> i  | libwayland-egl1               | package | 18.0.0-20.1 | x86_64 | Module-Basesystem
>>> i  | libwayland-server0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
>>> 
>>> 
>>> 
>>> VNC session is just black... Is this a Wayland / X-display permissions issue ? Here's the log.
>>> 
>>> bahid at hw-and-os-97:~> cat ~/.vnc/hw-and-os-97\:1.log
>>> 
>>> Xvnc TigerVNC 1.8.0 - built ??? ?? ???? ??:??:??
>>> Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
>>> See http://www.tigervnc.org <http://www.tigervnc.org/> for information on TigerVNC.
>>> Underlying X server release 11906000, The X.Org <http://x.org/> Foundation
>>> 
>>> 
>>> Thu Mar  8 14:27:47 2018
>>>  vncext:      VNC extension running!
>>>  vncext:      Listening for VNC connections on all interface(s), port 5901
>>>  vncext:      created VNC server for screen 0
>>> /etc/X11/xim: Checking whether an input method should be started.
>>> sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
>>> INPUT_METHOD is not set or empty (no user selected input method).
>>> Trying to start a default input method for the locale en_US.UTF-8 ...
>>> There is no default input method for the current locale.
>>> Dummy input method "none" (do not use any fancy input method by default)
>>> gnome-session-binary[1979]: WARNING: software acceleration check failed: Child process exited with code 1
>>> Unable to init server: Could not connect: Connection refused
>>> 
>>> ** (gnome-session-failed:2029): WARNING **: Cannot open display:
>>> 
>>> Thu Mar  8 14:27:53 2018
>>>  Connections: accepted: 10.138.8.158::55122
>>>  SConnection: Client needs protocol version 3.8
>>> 
>>> Thu Mar  8 14:27:56 2018
>>>  SConnection: Client requests security type VncAuth(2)
>>>  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
>>>  VNCSConnST:  Client pixel format depth 32 (32bpp) little-endian rgb max
>>>               255,255,255 shift 16,8,0
>>> 
>>> _______________________________________________
>>> sle-beta mailing list
>>> sle-beta at lists.suse.com <mailto:sle-beta at lists.suse.com>
>>> http://lists.suse.com/mailman/listinfo/sle-beta <http://lists.suse.com/mailman/listinfo/sle-beta>
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/4b6d0761/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/4b6d0761/attachment.sig>

From Dick.Waite at softwareag.com  Mon Mar 12 09:17:47 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Mon, 12 Mar 2018 15:17:47 +0000
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <1520862787.4384.84.camel@suse.de>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>,
	<1520862787.4384.84.camel@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076EFEF@daeexmbx1.eur.ad.sag>

Many Thanks for the update Hernan,

We do update our "mother" SLES's machine each month with "security" patches could we do that if they are not registered, do you allow "security" patch update with out being registered ? There are quite a number of "mothers". We do run systemctl mask packagekit.service on the mothers to stop automatic updates. If the clone is not registered does this stop "zypper in some-need-function" running ?

Could you point me at a good Docu to read and understand what a SLES12 and SLES15 machine can do if it's not registered. Many of the clones only live a week or two... If we do registere them I can see the SCC filling up 'cos the good people are used to just deleting the clone when it's done it's task.

Needs more thought and words with SAG, but many thanks for the explanation UUID was not used. Beta testing is grand to find out these issues. Thoughts for SLES15 SP-1 having an option to allow UUDI as the handshake so that machines that do provide it are not pegged down to the lowest common method of the simple machines?

__R

________________________________________
From: Hern?n Schmidt [hschmidt at suse.de]
Sent: 12 March 2018 14:53
To: Waite, Dick (External); 'sle-beta at lists.suse.com'
Cc: 'Vincent Moutoussamy'; jsrain at suse.cz; Kay Tate; Christophe Le Dorze
Subject: Re: UUDI not tested - Wrong Hostname updated --cleanup

Hi Dick,

Thanks for the write up and the suggestion.

> Why not use the machines UUID as the SCC USERNAME, then you are sure
> to be sure your talking to who you think you are, well better than
> now.

Yes, that would be a good solution. Unfortunately, SUSEConnect needs to
work on a large variety of devices, and we found that a large portion
of devices do not provide a UUID. To keep things simple for all cases,
we decided to generate a system "login" which gets saved to the
filesystem (the SCCcredentials file).
For that reason it's necessary to call --cleanup on the cloned system,
or alternatively, call --cleanup on the original system before saving
the snapshot, so that all clones are "clean" already.

Best regards,
--
Hern?n Schmidt
SUSE Customer Center

SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
HRB 21284 (AG N?rnberg)

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From vmoutoussamy at suse.com  Mon Mar 12 10:01:57 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Mon, 12 Mar 2018 17:01:57 +0100
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076EFEF@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>
	<1520862787.4384.84.camel@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D012076EFEF@daeexmbx1.eur.ad.sag>
Message-ID: <31EB33A6-2056-4EDB-B40E-7D7D5C2A147A@suse.com>

Hi,
> On 12 Mar 2018, at 16:17, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
> 
> Many Thanks for the update Hernan,
> 
> We do update our "mother" SLES's machine each month with "security" patches could we do that if they are not registered, do you allow "security" patch update with out being registered ? There are quite a number of "mothers?.

The only official and supported ways to retrieve our patches and updates are
directly thought SCC, via SMT/RMT or a SUSE Manager. So you need to register
your server to SCC, SMT or SUSE Manager.

> We do run systemctl mask packagekit.service on the mothers to stop automatic updates. If the clone is not registered does this stop "zypper in some-need-function" running ?

if not register to SCC/SMT/SUMA, well not have SUSE Channels available.

> Could you point me at a good Docu to read and understand what a SLES12 and SLES15 machine can do if it's not registered. Many of the clones only live a week or two... If we do registere them I can see the SCC filling up 'cos the good people are used to just deleting the clone when it's done it's task.

Well I guess, you have all sort of processes to create and destroy clones and I
think registration and de-registration should fit perfectly into your processes.

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/10c71fbe/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/10c71fbe/attachment.sig>

From Donald.Vosburg at suse.com  Mon Mar 12 09:27:57 2018
From: Donald.Vosburg at suse.com (Donald Vosburg)
Date: Mon, 12 Mar 2018 15:27:57 +0000
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076EFEF@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>, 
	<1520862787.4384.84.camel@suse.de>,
	<46AC8C81C10B8C48820201DF2AE1D76D012076EFEF@daeexmbx1.eur.ad.sag>
Message-ID: <6F90E487-28DD-4F0E-84F4-DD1375E8633B@suse.com>

Isn?t this what SMT/RMT or SUSE Manager can help with?

Sent from my iPhone

> On Mar 12, 2018, at 11:17 AM, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
> 
> Many Thanks for the update Hernan,
> 
> We do update our "mother" SLES's machine each month with "security" patches could we do that if they are not registered, do you allow "security" patch update with out being registered ? There are quite a number of "mothers". We do run systemctl mask packagekit.service on the mothers to stop automatic updates. If the clone is not registered does this stop "zypper in some-need-function" running ?
> 
> Could you point me at a good Docu to read and understand what a SLES12 and SLES15 machine can do if it's not registered. Many of the clones only live a week or two... If we do registere them I can see the SCC filling up 'cos the good people are used to just deleting the clone when it's done it's task.
> 
> Needs more thought and words with SAG, but many thanks for the explanation UUID was not used. Beta testing is grand to find out these issues. Thoughts for SLES15 SP-1 having an option to allow UUDI as the handshake so that machines that do provide it are not pegged down to the lowest common method of the simple machines?
> 
> __R
> 
> ________________________________________
> From: Hern?n Schmidt [hschmidt at suse.de]
> Sent: 12 March 2018 14:53
> To: Waite, Dick (External); 'sle-beta at lists.suse.com'
> Cc: 'Vincent Moutoussamy'; jsrain at suse.cz; Kay Tate; Christophe Le Dorze
> Subject: Re: UUDI not tested - Wrong Hostname updated --cleanup
> 
> Hi Dick,
> 
> Thanks for the write up and the suggestion.
> 
>> Why not use the machines UUID as the SCC USERNAME, then you are sure
>> to be sure your talking to who you think you are, well better than
>> now.
> 
> Yes, that would be a good solution. Unfortunately, SUSEConnect needs to
> work on a large variety of devices, and we found that a large portion
> of devices do not provide a UUID. To keep things simple for all cases,
> we decided to generate a system "login" which gets saved to the
> filesystem (the SCCcredentials file).
> For that reason it's necessary to call --cleanup on the cloned system,
> or alternatively, call --cleanup on the original system before saving
> the snapshot, so that all clones are "clean" already.
> 
> Best regards,
> --
> Hern?n Schmidt
> SUSE Customer Center
> 
> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
> HRB 21284 (AG N?rnberg)
> 
> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

From Dick.Waite at softwareag.com  Mon Mar 12 10:53:41 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Mon, 12 Mar 2018 16:53:41 +0000
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <6F90E487-28DD-4F0E-84F4-DD1375E8633B@suse.com>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>, 
	<1520862787.4384.84.camel@suse.de>,
	<46AC8C81C10B8C48820201DF2AE1D76D012076EFEF@daeexmbx1.eur.ad.sag>,
	<6F90E487-28DD-4F0E-84F4-DD1375E8633B@suse.com>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076F02B@daeexmbx1.eur.ad.sag>

Grand Evening Donald,

SAG does not have SMT/RMT or SUSE Manager, but if they can help with the --cleanup issue please give a few words...

__R
________________________________________
From: Donald Vosburg [Donald.Vosburg at suse.com]
Sent: 12 March 2018 16:27
To: Waite, Dick (External)
Cc: Hern?n Schmidt; sle-beta at lists.suse.com; Christophe Le Dorze; Kay Tate
Subject: Re: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup

Isn?t this what SMT/RMT or SUSE Manager can help with?

Sent from my iPhone

> On Mar 12, 2018, at 11:17 AM, Waite, Dick (External) <Dick.Waite at softwareag.com> wrote:
>
> Many Thanks for the update Hernan,
>
> We do update our "mother" SLES's machine each month with "security" patches could we do that if they are not registered, do you allow "security" patch update with out being registered ? There are quite a number of "mothers". We do run systemctl mask packagekit.service on the mothers to stop automatic updates. If the clone is not registered does this stop "zypper in some-need-function" running ?
>
> Could you point me at a good Docu to read and understand what a SLES12 and SLES15 machine can do if it's not registered. Many of the clones only live a week or two... If we do registere them I can see the SCC filling up 'cos the good people are used to just deleting the clone when it's done it's task.
>
> Needs more thought and words with SAG, but many thanks for the explanation UUID was not used. Beta testing is grand to find out these issues. Thoughts for SLES15 SP-1 having an option to allow UUDI as the handshake so that machines that do provide it are not pegged down to the lowest common method of the simple machines?
>
> __R
>
> ________________________________________
> From: Hern?n Schmidt [hschmidt at suse.de]
> Sent: 12 March 2018 14:53
> To: Waite, Dick (External); 'sle-beta at lists.suse.com'
> Cc: 'Vincent Moutoussamy'; jsrain at suse.cz; Kay Tate; Christophe Le Dorze
> Subject: Re: UUDI not tested - Wrong Hostname updated --cleanup
>
> Hi Dick,
>
> Thanks for the write up and the suggestion.
>
>> Why not use the machines UUID as the SCC USERNAME, then you are sure
>> to be sure your talking to who you think you are, well better than
>> now.
>
> Yes, that would be a good solution. Unfortunately, SUSEConnect needs to
> work on a large variety of devices, and we found that a large portion
> of devices do not provide a UUID. To keep things simple for all cases,
> we decided to generate a system "login" which gets saved to the
> filesystem (the SCCcredentials file).
> For that reason it's necessary to call --cleanup on the cloned system,
> or alternatively, call --cleanup on the original system before saving
> the snapshot, so that all clones are "clean" already.
>
> Best regards,
> --
> Hern?n Schmidt
> SUSE Customer Center
>
> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
> HRB 21284 (AG N?rnberg)
>
> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
>
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

From ross.brunson at suse.com  Mon Mar 12 13:00:20 2018
From: ross.brunson at suse.com (Ross Brunson)
Date: Mon, 12 Mar 2018 19:00:20 +0000
Subject: [sle-beta] SLES gnome-session-failed for SLES 12sp3 -> 15 via
 zypper dup
In-Reply-To: <FCD5D924-DB8F-4368-B099-7B1128B886C7@suse.com>
References: <7805E5E9-D8B3-41F4-B98F-D44CDA50E276@emc.com>
	<57546213-8B27-4091-8BC6-00DEF3B46CF5@suse.com>
	<A46165CC-3B02-416A-BF0A-0229E999E459@emc.com>
	<FCD5D924-DB8F-4368-B099-7B1128B886C7@suse.com>
Message-ID: <5D9A195A-BCEF-43EF-A0AD-F541ED26B830@suse.com>

Just a quick thought, we had a bug like this and using :5902 worked while the main port and :5901 didn?t.

Still a bug, tho.

--
Ross Brunson
Senior Training Engineer
SUSE Inc.
ross.brunson at suse.com
training.suse.com
Ofc: 406-404-2005
From: <sle-beta-bounces at lists.suse.com> on behalf of Vincent Moutoussamy <vmoutoussamy at suse.com>
Date: Monday, March 12, 2018 at Mar 12, 2018 -9:01 AM
To: "Bahi, David" <David.Bahi at dell.com>
Cc: "sle-beta at lists.suse.com" <sle-beta at lists.suse.com>
Subject: Re: [sle-beta] SLES gnome-session-failed for SLES 12sp3 -> 15 via zypper dup

Hi,
On 9 Mar 2018, at 20:20, Bahi, David <David.Bahi at dell.com<mailto:David.Bahi at dell.com>> wrote:

A fresh install, using the Installer ISO and SLP for Packages + SLED / base / desktop_applications, made no difference.

Same result with a vncserver invocation (5901 - not the yast2 enable remote administration port 5900 thing) :

"Connection refused"

"cannot open display".

Nothing to do with firewall and this bz:

https://bugzilla.suse.com/show_bug.cgi?id=1081952

as firewall was entirely disabled for this attempt (because there's no Yast2 tool for configuring it yet).


Opened:

https://bugzilla.suse.com/show_bug.cgi?id=1084756

db

Well thanks, creating the bug report was the right thing to do!

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager



On Mar 9, 2018, at 11:37, Vincent Moutoussamy <vmoutoussamy at suse.com<mailto:vmoutoussamy at suse.com>> wrote:

Hi,

?zypper dup? is not a supported method to upgrade to Major SLE version,
thus not supported to upgrade from SLES 12 SP3 to SLES 15.

This is only supported for Service Pack Migration of a SLE version, and note
even in this case we recommend to use ?zypper migration? instead
https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.migr.zypper.onlinemigr

Note:
This is not new with SLE15, the same statement are true for migrating from SLE
11 to SLE 12. cf https://www.suse.com/documentation/sles-12/singlehtml/book_sle_deployment/book_sle_deployment.html#sec.update.sle.methods

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager


On 8 Mar 2018, at 20:59, Bahi, David <David.Bahi at dell.com<mailto:David.Bahi at dell.com>> wrote:

Is this zypper dup path bz worthy?

prompt > systemctl isolate graphical.target

Only gets the GDM up as well - doesn't allow me to login.

bahid at hw-and-os-97:~> zypper se -s -i wayland gnome-session gnome-shell-classic
Loading repository data...
Reading installed packages...

S  | Name                          | Type    | Version     | Arch   | Repository
---+-------------------------------+---------+-------------+--------+----------------------------
i+ | gnome-session                 | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
i  | gnome-session-core            | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
i  | gnome-session-default-session | package | 3.26.1-4.1  | x86_64 | Module-Desktop-Applications
i+ | gnome-shell-classic           | package | 3.26.2-4.1  | noarch | Module-Desktop-Applications
i  | libgstwayland-1_0-0           | package | 1.12.4-3.1  | x86_64 | Module-Desktop-Applications
i  | libwayland-client0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
i  | libwayland-cursor0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem
i  | libwayland-egl1               | package | 18.0.0-20.1 | x86_64 | Module-Basesystem
i  | libwayland-server0            | package | 1.14.0-1.5  | x86_64 | Module-Basesystem



VNC session is just black... Is this a Wayland / X-display permissions issue ? Here's the log.

bahid at hw-and-os-97:~> cat ~/.vnc/hw-and-os-97\:1.log

Xvnc TigerVNC 1.8.0 - built ??? ?? ???? ??:??:??
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org<http://www.tigervnc.org/> for information on TigerVNC.
Underlying X server release 11906000, The X.Org<http://x.org/> Foundation


Thu Mar  8 14:27:47 2018
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
gnome-session-binary[1979]: WARNING: software acceleration check failed: Child process exited with code 1
Unable to init server: Could not connect: Connection refused

** (gnome-session-failed:2029): WARNING **: Cannot open display:

Thu Mar  8 14:27:53 2018
 Connections: accepted: 10.138.8.158::55122
 SConnection: Client needs protocol version 3.8

Thu Mar  8 14:27:56 2018
 SConnection: Client requests security type VncAuth(2)
 VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
 VNCSConnST:  Client pixel format depth 32 (32bpp) little-endian rgb max
              255,255,255 shift 16,8,0

_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com<mailto:sle-beta at lists.suse.com>
http://lists.suse.com/mailman/listinfo/sle-beta




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/31e93c72/attachment.htm>

From kastl at b1-systems.de  Mon Mar 12 13:19:43 2018
From: kastl at b1-systems.de (Johannes Kastl)
Date: Mon, 12 Mar 2018 20:19:43 +0100
Subject: [sle-beta] docbook2X missing in SLES15 on OBS?
In-Reply-To: <27B4ADC0-864D-4EB1-B372-7D948D4D12EE@suse.com>
References: <15671733-28d7-ab03-9b7c-f347440d4ad8@b1-systems.de>
	<27B4ADC0-864D-4EB1-B372-7D948D4D12EE@suse.com>
Message-ID: <4275a26c-8fea-8585-30cc-60d4c65e5150@b1-systems.de>

Hi Vincent,

Vincent Moutoussamy schrieb:

> Please create a bug report for this and post the bug number here.
> Some docbook packages are clearly missing.

https://bugzilla.suse.com/show_bug.cgi?id=1084950

Kind regards,
Johannes

-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: kastl at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 864 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/6322659e/attachment.sig>

From kastl at b1-systems.de  Mon Mar 12 13:26:02 2018
From: kastl at b1-systems.de (Johannes Kastl)
Date: Mon, 12 Mar 2018 20:26:02 +0100
Subject: [sle-beta] Installing RC1 on VM with beta4 partitions: missing
 bios_boot partition
Message-ID: <d48279a0-6fcd-ab84-2e2f-1b58c475de55@b1-systems.de>

Hi all,

I installed RC1 over the beta4 installed in my Test-VM, just keeping the
partitions created during installation of Beta4. Formatting / and swap,
and just keeping /home brings up an error that the bios_boot partition
is missing.

Indeed I have a small 1MB partition in between, no idea if this is
really used. But I have no bios_boot partition.

I forced the installer to continue, and everything seems to work.
Machine boots.

I'll try to set the machine back to an earlier snapshot and redo the
installation.

Known issue? Worth a bug report?

Kind Regards,
Johannes

Addendum:
Trying to resize the partitions I triggered an error in Yast, asking me
to start the ruby debugger. I need to look into that and try to
reproduce it.

-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: kastl at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 864 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180312/2bdb6e95/attachment.sig>

From Dick.Waite at softwareag.com  Tue Mar 13 00:11:04 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Tue, 13 Mar 2018 06:11:04 +0000
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <1520862787.4384.84.camel@suse.de>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>,
	<1520862787.4384.84.camel@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076F2FA@daeexmbx1.eur.ad.sag>

Last word and then I shut up...

You can not update / write to a database / registry without any check that the caller is entitled to update / write that field. Even a Hostname check would be better that nothing. The  --cleanup option will be forgotten at some time by someone and then that lowly clone is going to update the SCC of a valuable Mother or maybe even a queen.

If the customer has forgotten the --cleanup and left the hostname the same as mother then you have done your due diligence. I expect in this case it's an deliberate attack to cause the site issues.

That's it.....now I can sleep at night ;o)

__R
________________________________________
From: Hern?n Schmidt [hschmidt at suse.de]
Sent: 12 March 2018 14:53
To: Waite, Dick (External); 'sle-beta at lists.suse.com'
Cc: 'Vincent Moutoussamy'; jsrain at suse.cz; Kay Tate; Christophe Le Dorze
Subject: Re: UUDI not tested - Wrong Hostname updated --cleanup

Hi Dick,

Thanks for the write up and the suggestion.

> Why not use the machines UUID as the SCC USERNAME, then you are sure
> to be sure your talking to who you think you are, well better than
> now.

Yes, that would be a good solution. Unfortunately, SUSEConnect needs to
work on a large variety of devices, and we found that a large portion
of devices do not provide a UUID. To keep things simple for all cases,
we decided to generate a system "login" which gets saved to the
filesystem (the SCCcredentials file).
For that reason it's necessary to call --cleanup on the cloned system,
or alternatively, call --cleanup on the original system before saving
the snapshot, so that all clones are "clean" already.

Best regards,
--
Hern?n Schmidt
SUSE Customer Center

SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
HRB 21284 (AG N?rnberg)

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From kukuk at suse.de  Tue Mar 13 00:28:08 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Tue, 13 Mar 2018 07:28:08 +0100
Subject: [sle-beta] UUDI not tested - Wrong Hostname updated --cleanup
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012076F2FA@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012076E552@daeexmbx1.eur.ad.sag>
	<1520862787.4384.84.camel@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D012076F2FA@daeexmbx1.eur.ad.sag>
Message-ID: <20180313062808.GA3534@suse.de>

On Tue, Mar 13, Waite, Dick (External) wrote:

> Last word and then I shut up...
> 
> You can not update / write to a database / registry without any check that the caller is entitled to update / write that field. Even a Hostname check would be better that nothing. The  --cleanup option will be forgotten at some time by someone and then that lowly clone is going to update the SCC of a valuable Mother or maybe even a queen.

Again: the hostname is completly useless for this case in most environments. 
Else: all other data used for registration got cloned by you and 
is identical on both machines. So any check we can do would tell
us: this is the same machine as registered against SCC.

If you clone a machine, you have to remove all host specific data.
And this is not only the SCC registration stuff, this are also
machine-id, dbus ID, ssh host key, maschine specific certificates, ...
If you don't do that, bad thinks can happen, not only with registration.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From kanderssen at suse.de  Tue Mar 13 07:26:13 2018
From: kanderssen at suse.de (=?UTF-8?Q?Knut_Alejandro_Anderssen_Gonz=c3=a1lez?=)
Date: Tue, 13 Mar 2018 13:26:13 +0000
Subject: [sle-beta]  Use correct base product name
Message-ID: <59000864-9c63-41a0-cbf3-6ec758126ac3@suse.de>

Cloned profiles were using a wrong base product name ("short_name").

<products config:type="list">
  <product>SLED15</product>
</products>

It has been fixed recently [1] and the documentation has been updated
accordingly [2]

Take it into account if cloned profiles are used and an error about not
product selected is reported. The profiles should use the name without
the version (SLES, SLED):

<products config:type="list">
  <product>SLED</product>
</products>


[1] https://github.com/yast/yast-autoinstallation/pull/411
[2] https://github.com/SUSE/doc-sle/pull/263

-- 
Knut Alejandro Anderssen Gonz?lez
YaST Team at SUSE Linux GmbH

From lslezak at suse.cz  Tue Mar 13 07:40:42 2018
From: lslezak at suse.cz (Ladislav Slezak)
Date: Tue, 13 Mar 2018 14:40:42 +0100
Subject: [sle-beta] Use correct base product name
In-Reply-To: <59000864-9c63-41a0-cbf3-6ec758126ac3@suse.de>
References: <59000864-9c63-41a0-cbf3-6ec758126ac3@suse.de>
Message-ID: <ef7ee890-b2dc-6ddf-1952-e7b3e701c550@suse.cz>

Dne 13.3.2018 v 14:26 Knut Alejandro Anderssen Gonz?lez napsal(a):
> Cloned profiles were using a wrong base product name ("short_name").
> 
> <products config:type="list">
>   <product>SLED15</product>
> </products>

JFYI: that happened in SLE15 RC1 (maybe in the previous Beta as well)
and it has been fixed in SLE15 RC2. (SLE12 is not affected, that key is
missing in the clone, but you might need to add it manually.)

That means the cloned RC1 systems need a small fix to work in RC2
(just remove the version):

> <products config:type="list">
>   <product>SLED</product>
> </products>


-- 
Ladislav Slez?k
YaST Developer

SUSE LINUX, s.r.o.
Corso IIa
K?i??kova 148/34
18600 Praha 8

From Dick.Waite at softwareag.com  Tue Mar 13 08:19:51 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Tue, 13 Mar 2018 14:19:51 +0000
Subject: [sle-beta] Use correct base product name
In-Reply-To: <ef7ee890-b2dc-6ddf-1952-e7b3e701c550@suse.cz>
References: <59000864-9c63-41a0-cbf3-6ec758126ac3@suse.de>,
	<ef7ee890-b2dc-6ddf-1952-e7b3e701c550@suse.cz>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012076F6DA@daeexmbx1.eur.ad.sag>

Grand Afternoon,

Many thanks for the update good YaST people. I'll look forward to RC2 and see how well Migration has moved on.

Wishing you well.

__R

________________________________________
From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Ladislav Slezak [lslezak at suse.cz]
Sent: 13 March 2018 14:40
To: sle-beta at lists.suse.com
Subject: Re: [sle-beta] Use correct base product name

Dne 13.3.2018 v 14:26 Knut Alejandro Anderssen Gonz?lez napsal(a):
> Cloned profiles were using a wrong base product name ("short_name").
>
> <products config:type="list">
>   <product>SLED15</product>
> </products>

JFYI: that happened in SLE15 RC1 (maybe in the previous Beta as well)
and it has been fixed in SLE15 RC2. (SLE12 is not affected, that key is
missing in the clone, but you might need to add it manually.)

That means the cloned RC1 systems need a small fix to work in RC2
(just remove the version):

> <products config:type="list">
>   <product>SLED</product>
> </products>


--
Ladislav Slez?k
YaST Developer

SUSE LINUX, s.r.o.
Corso IIa
K?i??kova 148/34
18600 Praha 8
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From vmoutoussamy at suse.com  Tue Mar 13 09:02:33 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Tue, 13 Mar 2018 16:02:33 +0100
Subject: [sle-beta] Installing RC1 on VM with beta4 partitions: missing
 bios_boot partition
In-Reply-To: <d48279a0-6fcd-ab84-2e2f-1b58c475de55@b1-systems.de>
References: <d48279a0-6fcd-ab84-2e2f-1b58c475de55@b1-systems.de>
Message-ID: <4CB64CFB-4651-4BC0-86A4-318482C65D72@suse.com>

Hi,
> On 12 Mar 2018, at 20:26, Johannes Kastl <kastl at b1-systems.de> wrote:
> 
> Hi all,
> 
> I installed RC1 over the beta4 installed in my Test-VM, just keeping the
> partitions created during installation of Beta4. Formatting / and swap,
> and just keeping /home brings up an error that the bios_boot partition
> is missing.

The yast partitioner and especially libstorage-ng have received a lot of fixes
and enhancement since Beta4 (cf. Highlights of YaST Development Sprint#).
So I would suggest to remove the beta4 existing partitions completely or base
your test on a SLE12SP3 migration with a similar partition layout.

> 
> Indeed I have a small 1MB partition in between, no idea if this is
> really used. But I have no bios_boot partition.
> 
> I forced the installer to continue, and everything seems to work.
> Machine boots.
> 
> I'll try to set the machine back to an earlier snapshot and redo the
> installation.
> 
> Known issue? Worth a bug report?

The only thing similar to your issue that I was able to find is:
bsc#1082349, specially comment#5:
https://bugzilla.suse.com/show_bug.cgi?id=1082349#c5 <https://bugzilla.suse.com/show_bug.cgi?id=1082349#c5>

Please note that this is a openSUSE Leap 15 Beta bug.
If you happen to be able to reproduce this issue (without the beta 4 legacy
setup), please create a new SLES 15 bug report.

> 
> Kind Regards,
> Johannes
> 
> Addendum:
> Trying to resize the partitions I triggered an error in Yast, asking me
> to start the ruby debugger. I need to look into that and try to
> reproduce it.

Same advice: I would suggest to remove the beta4 existing partitions completely
or base your test on a SLE12SP3 migration with a similar partition layout.

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

> 
> --
> Johannes Kastl
> Linux Consultant & Trainer
> Tel.: +49 (0) 151 2372 5802
> Mail: kastl at b1-systems.de
> 
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> 
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180313/ca07da50/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180313/ca07da50/attachment.sig>

From jlopez at suse.com  Thu Mar 15 02:52:23 2018
From: jlopez at suse.com (Jose Lopez)
Date: Thu, 15 Mar 2018 02:52:23 -0600
Subject: [sle-beta] Installing RC1 on VM with beta4 partitions: missing
 bios_boot partition
Message-ID: <5AAA34470200000D00840E8B@prv-mh.provo.novell.com>


Hi,

Partitioner in RC1 comes equipped with sanity checks for the 
partitioning layout. Before accepting all changes you have done in the 
Partitioner, warning/error messages could be shown to indicate what is 
wrong in your configuration. In your case, you are getting a warning due 
to missing BIOS BOOT partition. Partitioner considers a BIOS BOOT 
partition as needed when the BIOS is working on Legacy mode (not UEFI) 
and the boot disk is partitioned using a GPT partition table. In that 
scenario, you get the BIOS BOOT warning message if there is not a BIOS 
BOOT partition with at least 2 MiB of total size. In the case of a 
missing BIOS BOOT, the message is only a warning and you can continue 
with the installation if you are sure.

Are you testing with a different scenario? In that case, please, report 
a bug with corresponding y2log to debug what is happening.

With regard to the resizing error, I am afraid we need a bug report with 
y2logs.

Regards,
Iv?n

YaST Team


----

Hi,

> On 12 Mar 2018, at 20:26, Johannes Kastl <kastl at b1-systems.de> wrote:

>

> Hi all,

>

> I installed RC1 over the beta4 installed in my Test-VM, just keeping the

> partitions created during installation of Beta4. Formatting / and swap,

> and just keeping /home brings up an error that the bios_boot partition

> is missing.



The yast partitioner and especially libstorage-ng have received a lot of

fixes

and enhancement since Beta4 (cf. Highlights of YaST Development Sprint#).

So I would suggest to remove the beta4 existing partitions completely or

base

your test on a SLE12SP3 migration with a similar partition layout.



>

> Indeed I have a small 1MB partition in between, no idea if this is

> really used. But I have no bios_boot partition.

>

> I forced the installer to continue, and everything seems to work.

> Machine boots.

>

> I'll try to set the machine back to an earlier snapshot and redo the

> installation.

>

> Known issue? Worth a bug report?



The only thing similar to your issue that I was able to find is:

bsc#1082349, specially comment#5:

https://bugzilla.suse.com/show_bug.cgi?id=1082349#c5



Please note that this is a openSUSE Leap 15 Beta bug.

If you happen to be able to reproduce this issue (without the beta 4 legacy

setup), please create a new SLES 15 bug report.



>

> Kind Regards,

> Johannes

>

> Addendum:

> Trying to resize the partitions I triggered an error in Yast, asking me

> to start the ruby debugger. I need to look into that and try to

> reproduce it.



Same advice: I would suggest to remove the beta4 existing partitions

completely

or base your test on a SLE12SP3 migration with a similar partition layout.



Regards,

--

Vincent Moutoussamy

SUSE Beta Program and SDK Project Manager








From wengel at suse.de  Fri Mar 16 10:27:28 2018
From: wengel at suse.de (Wolfgang Engel)
Date: Fri, 16 Mar 2018 17:27:28 +0100
Subject: [sle-beta] Package Hub for SLE-15
Message-ID: <86ce991b-55d8-2ab2-5ab2-441cbf4dc3a8@suse.de>

Dear beta users,

Package Hub for SLE-15 shows up on the horizon and is currently under
heavy development.

If you wants to get hands on packages from Package Hub, there is an easy
way to test the packages that are currently available.

Since the packages are built in the Open Build Service* you can add the
repository manually with the following zypper command:

Code:

zypper ar -fc
https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15/standard/openSUSE:Backports:SLE-15.repo

The availability thru the SUSE Customer Center to beta users will follow
soon.

Please also note that since it is currently under heavy development, not
all packages you might expect to be there are currently available.
They might also not be available to all platforms at this point in time.

Last but not least, remember that "The software delivered by the SUSE
Package Hub comes without guarantees of functionality and without
commercial support services from SUSE.? (cf
https://packagehub.suse.com/support/).
However do not hesitate to report any of your finding here on
sle-beta at lists.suse.com but put the official PackageHub contact in CC:
packagehub at suse.com

Have fun!

Wolfgang
* https://build.opensuse.org/project/show/openSUSE:Backports:SLE-15

From kastl at b1-systems.de  Mon Mar 19 13:45:47 2018
From: kastl at b1-systems.de (Johannes Kastl)
Date: Mon, 19 Mar 2018 20:45:47 +0100
Subject: [sle-beta] Building SLES15 docker images: PreInstall of skopeo
	misses libgpgme11
Message-ID: <787b6f31-09b7-aa6f-159d-07bb5bdacf1b@b1-systems.de>

Hi guys,

we are building SLES15 docker images on our private OBS instance.

PreInstall'ing skopeo, as this is needed for docker images, leads to an
error where a shared library from libgpgme11 is not found.
PreInstall'ing libgpgme11 in addition fixes the issue.

<https://bugzilla.suse.com/show_bug.cgi?id=1085911>

Kind Regards,
Johannes
-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: kastl at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 864 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180319/4318e57e/attachment.sig>

From beta-programs at lists.suse.com  Fri Mar 23 08:24:59 2018
From: beta-programs at lists.suse.com (SUSE Beta Program)
Date: Fri, 23 Mar 2018 15:24:59 +0100
Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 Release Candidate 2
	is out!
Message-ID: <5ab50e3b210b9_6f7cb05324826eb@boucane.mail>

Here it comes! Release Candidate 1 of SUSE Linux Enterprise 15:
  SUSE Linux Enterprise Server (SLES),
  SUSE Linux Enterprise Just Enough Operating System(JeOS),
  SUSE Linux Enterprise Desktop (SLED),
  SUSE Linux Enterprise High Availability (SLE-HA),
  SUSE Linux Enterprise Workstation Extension (SLE-WE)
  and SUSE Linux Enterprise High Performance Computing (SLE-HPC)

Download[1]

== Important Notice
=Packages DVD
When using Packages DVD to install SLE modules, please make sure to also add the 
Product repository you are installing (SLES / SLED / HA / ...) from Packages DVD.
Not doing so might result in missing system roles during installation.

=Notable changes
- Migration from SLE 12 to SLE 15:
Please refer to our new "Upgrade Guide" available as a beta documentation[2]
- SLE 15 HPC now fully part of the SLE15 Beta Program. You can now request
Beta Registration Code for SLE 15 HPC on x86_64 and aarch64[3].
- OpenSSL 1.0 is no longer installed by default, all packages have been migrated
to OpenSSL 1.1. OpenSSL 1.0 will be available in Legacy module.
- We will provide Firefox 59 in replacement of Firefox 52 ESR as maintenance
update after RC2 is released. Next Firefox ESR version (60) will be integrated
in SLE15 before GM release. In the mean time, please report regressions with 
current Firefox release.
- tigervnc, libvirt, apache2, yast2-firewall, yast2-network and yast http-server
better integrate with firewalld.
- drop /etc/xinetd.d directory [bsc#1084457]
- The 31-bit environment for s390 was dropped from the current media
- nginx available in the Server Application Module
- Updated SUSEConnect (0.3.8)
  - Fix list-extensions to show the full SLE 15 tree [bsc#1064264]
  - Enable automatic activation of recommended extensions/modules
  - Automatically deregister all installed extensions/modules when deregistering
  a system.
- Our Release Notes received a lot of updates[5]

=Package changes
- Added packages:
adwaita-qt, container-suseconnect, cppunit, cross-nvptx-gcc7, docbook2x, docbook-utils,
emacs-apel, glm, gnome-online-miners, gom, grilo-plugins, intel-vaapi-driver, itstool,
kiwi-template-sap, libmpeg2, libqt5-qtdoc, libqt5-qtgraphicaleffects, libqt5-qtimageformats,
libqt5-qtquickcontrols, libqt5-qtscript, libqt5-qttranslations, libsmbios2, mercurial, meson,
mpich, mpitests-mpich, mpitests-mvapich2, mpitests-openmpi2, mpitests, mvapich2-psm2, nasm,
ninja, novnc, nvptx-tools, opensc, osinfo-db-tools, QGnomePlatform, raspberrypi-firmware-config,
raspberrypi-firmware-dt, raspberrypi-firmware, systemtap-headers, tidy, u-boot-rpi3, vhostmd, 
wol, xdg-desktop-portal-gtk, xdg-desktop-portal, yast2-boot-server, yast2-scanner,
yubikey-manager-qt, yubikey-manager
- Removed packages:
docbook_5, docbook5-xsl-stylesheets, ffado, ft2demos, gegl, ghostscript-cjk, gmime2_6, hdf, imap,
libavc1394, libdbus-c++, libiec61883, libsmbios, libxml++26, lua51-luajit, netcdf, openssl-1_1_0, 
petsc, SuSEfirewall2, wodim, yubikey-personalization-gui
- Updated packages (selection):
  - ledmon updated to 0.90 (bsc#1081125)
  - libstorage-ng and mksh received a lot of bugfixes
  - firewalld updated to 0.5.2
  - GnuTLS updated to 3.6.2
  - GnuPG updated to 2.2.5
  - clamav security update (bsc#1083915)
  - Thunderbird updated to 52.6
  - nodejs8: npm: upgrade npm to 3.9.5
  - postgresql10 updated to 10.3
  - rear update to 2.3a (HA)
  - vim update to 8.0.1568

=Fixed bugs in RC 2 (selection):
- A subvolume is not created for home if /home is not a separate partition and root
partition is using btrfs. This might cause data loss if rollback is used [bsc#1084261].
- Evolution (and webkit2gtk applications) crashes when used on wayland with unaccelerated
drivers (mostly VT related) [bsc#1079512]
- Kernel reports error "BUG: Bad page state in process xx" [BSC#1082743] 
- No default pattern selected when installing Workstation extension on SLES [bsc#1083611]

== More information
SLE Beta Page[4]
Release Notes[5]
Known Issues[6]

  Your SUSE Linux Enterprise Team

== Beta Program
Please refer to our dedicated SLE Beta Program webpage[1] for any general
information. However, do not hesitate to contact us at
beta-programs at lists.suse.com if you have any questions.

You received this email because you're signed up to get updates from us.
Please send an email to beta-programs at lists.suse.com if you want to
unsubscribe.

[1] https://www.suse.com/betaprogram/sle-beta/#download
[2] https://susedoc.github.io/doc-sle/develop/SLES-upgrade/single-html/
[3] https://www.suse.com/betaprogram/sle-beta/#faq-reg
[4] https://www.suse.com/betaprogram/sle-beta
[5] https://www.suse.com/betaprogram/sle-beta/#releasenotes
[6] https://www.suse.com/betaprogram/sle-beta/#knownissues
[7] https://www.suse.com/betaprogram/sle-beta/#releases
[8] https://www.suse.com/betaprogram/sle-beta/#faq-update1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180323/36eb8006/attachment.htm>

From nathankoch at tutanota.de  Sun Mar 25 00:34:23 2018
From: nathankoch at tutanota.de (Nathan Koch)
Date: Sun, 25 Mar 2018 08:34:23 +0200 (CEST)
Subject: [sle-beta] Activation Key Query
Message-ID: <L8QrLoW--B-0@tutanota.de>

Hello,
I have more than one computer and was wondering if I could use the same key for multiple computers?

Thank you,
Nate


-- 
 Securely sent with Tutanota. Claim your encrypted mailbox today! 
 https://tutanota.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180325/2fbc4f69/attachment.htm>

From dkohler at cray.com  Mon Mar 26 07:31:17 2018
From: dkohler at cray.com (David Kohler)
Date: Mon, 26 Mar 2018 13:31:17 +0000
Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 Release
 Candidate 2	is out!
In-Reply-To: <5ab50e3b210b9_6f7cb05324826eb@boucane.mail>
References: <5ab50e3b210b9_6f7cb05324826eb@boucane.mail>
Message-ID: <DM3PR11MB098749708218D304BFD426A5CFAD0@DM3PR11MB0987.namprd11.prod.outlook.com>

Object not found! 404

SLE-15-Packages-x86_64-RC2-DVD2.iso

From: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] On Behalf Of SUSE Beta Program
Sent: Friday, March 23, 2018 9:25 AM
To: sle-beta at lists.suse.com
Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 Release Candidate 2 is out!


Having trouble viewing this email? Please check the plain text version of it with your mailer.







[Image removed by sender.]






[Image removed by sender.]<https://www.suse.com/betaprogram/sle-beta/>







Here it comes! Release Candidate 2 of SUSE Linux Enterprise 15 for:

  *   SUSE Linux Enterprise Server (SLES),
  *   SUSE Linux Enterprise Just Enough Operating System (JeOS),
  *   SUSE Linux Enterprise Desktop (SLED),
  *   SUSE Linux Enterprise Workstation Extension (SLE-WE),
  *   SUSE Linux Enterprise High Availablility (SLE-HA)
  *   SUSE Linux Enterprise High Performance Computing (SLE-HPC)
Download ?<https://www.suse.com/betaprogram/sle-beta/#download>





Important Notice



Packages DVD

When using Packages DVD to install SLE modules, please make sure to also add the Product repository you are installing (SLES / SLED / HA / ...) from Packages DVD. Not doing so might result in missing system roles during installation.

Migration from SLE 12 to SLE 15

Please refer to our new Upgrade Guide<https://susedoc.github.io/doc-sle/develop/SLES-upgrade/single-html/> available as a beta documentation

Notable changes

  *   SLE 15 HPC now fully part of the SLE15 Beta Program. You can now request Beta Registration Code for SLE 15 HPC<https://www.suse.com/betaprogram/sle-beta/#faq-reg> on x86_64 and aarch64.
  *   OpenSSL 1.0 is no longer installed by default, all packages have been migrated to OpenSSL 1.1. OpenSSL 1.0 will be available in Legacy module.
  *   We will provide Firefox 59 in replacement of Firefox 52 ESR as maintenance update after RC2 is released. Next Firefox ESR version (60) will be integrated in SLE15 before GM release. In the mean time, please report regressions with current Firefox release.
  *   tigervnc, libvirt, apache2, yast2-firewall, yast2-network and yast http-server better integrate with firewalld.
  *   drop /etc/xinetd.d directory [bsc#1084457]
  *   The 31-bit environment for s390 was dropped from the current media
  *   nginx available in the Server Application Module
  *   Updated SUSEConnect (0.3.8)
     *   Fix list-extensions to show the full SLE 15 tree [bsc#1064264]
     *   Enable automatic activation of recommended extensions/modules
     *   Automatically deregister all installed extensions/modules when deregistering a system.
  *   Our Release Notes<https://www.suse.com/betaprogram/sle-beta/#releasenotes> received a lot of updates

Package changes
Added packages

adwaita-qt, container-suseconnect, cppunit, cross-nvptx-gcc7, docbook2x, docbook-utils, emacs-apel, glm, gnome-online-miners, gom, grilo-plugins, intel-vaapi-driver, itstool, kiwi-template-sap, libmpeg2, libqt5-qtdoc, libqt5-qtgraphicaleffects, libqt5-qtimageformats, libqt5-qtquickcontrols, libqt5-qtscript, libqt5-qttranslations, libsmbios2, mercurial, meson, mpich, mpitests-mpich, mpitests-mvapich2, mpitests-openmpi2, mpitests, mvapich2-psm2, nasm, ninja, novnc, nvptx-tools, opensc, osinfo-db-tools, QGnomePlatform, raspberrypi-firmware-config, raspberrypi-firmware-dt, raspberrypi-firmware, systemtap-headers, tidy, u-boot-rpi3, vhostmd, wol, xdg-desktop-portal-gtk, xdg-desktop-portal, yast2-boot-server, yast2-scanner, yubikey-manager-qt, yubikey-manager

Removed packages

docbook_5, docbook5-xsl-stylesheets, ffado, ft2demos, gegl, ghostscript-cjk, gmime2_6, hdf, imap, libavc1394, libdbus-c++, libiec61883, libsmbios, libxml++26, lua51-luajit, netcdf, openssl-1_1_0, petsc, SuSEfirewall2, wodim, yubikey-personalization-gui

Updated packages (selection)

  *   ledmon updated to 0.90 (bsc#1081125)
  *   libstorage-ng and mksh received a lot of bugfixes
  *   firewalld updated to 0.5.2
  *   GnuTLS updated to 3.6.2
  *   GnuPG updated to 2.2.5
  *   clamav security update (bsc#1083915)
  *   Thunderbird updated to 52.6
  *   nodejs8: npm: upgrade npm to 3.9.5
  *   postgresql10 updated to 10.3
  *   rear update to 2.3a (HA)
  *   vim update to 8.0.1568

Fixed bug in RC2 (selection)

  *   A subvolume is not created for home if /home is not a separate partition and root partition is using btrfs. This might cause data loss if rollback is used [bsc#1084261].
  *   Evolution (and webkit2gtk applications) crashes when used on wayland with unaccelerated drivers (mostly VT related) [bsc#1079512]
  *   Kernel reports error "BUG: Bad page state in process xx" [BSC#1082743]
  *   No default pattern selected when installing Workstation extension on SLES [bsc#1083611]



More information



SLE Beta Page ?<https://www.suse.com/betaprogram/sle-beta>




Release Notes ?<https://www.suse.com/betaprogram/sle-beta/#releasenotes>




Known Issues ?<https://www.suse.com/betaprogram/sle-beta/#knownissues>









Your SUSE Linux Enterprise Team







Do not hesitate to contact us at beta-programs at lists.suse.com<mailto:beta-programs at lists.suse.com> if you have any questions.

You received this email because you're signed up to get updates from us. Click here to unsubscribe.<mailto:beta-programs at lists.suse.com?subject=Unsubscribe%20from%20SLE%20Beta&body=Unsubscribe%20Unsubscribe%20from%20SLE%20Beta>






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180326/a73fb927/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180326/a73fb927/attachment.jpg>

From kukuk at suse.de  Tue Mar 27 04:03:00 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Tue, 27 Mar 2018 12:03:00 +0200
Subject: [sle-beta] Autoyast Addons
In-Reply-To: <5AB975230200001500025B7B@prv-mh.provo.novell.com>
References: <5AB975230200001500025B7B@prv-mh.provo.novell.com>
Message-ID: <20180327100300.GA9767@suse.de>


Hi,

On Mon, Mar 26, Jason Record wrote:

> I'm having trouble including addons in my autoyast control file.

Hm, your addon section does not look like as described in this
documentation:
https://github.com/yast/yast-autoinstallation/blob/master/doc/profile_changes_SLE15.md

  Thorsten


-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From kukuk at suse.de  Tue Mar 27 04:04:25 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Tue, 27 Mar 2018 12:04:25 +0200
Subject: [sle-beta] Autoyast Addons
In-Reply-To: <20180327100300.GA9767@suse.de>
References: <5AB975230200001500025B7B@prv-mh.provo.novell.com>
	<20180327100300.GA9767@suse.de>
Message-ID: <20180327100425.GA32014@suse.de>

On Tue, Mar 27, Thorsten Kukuk wrote:

> 
> Hi,
> 
> On Mon, Mar 26, Jason Record wrote:
> 
> > I'm having trouble including addons in my autoyast control file.
> 
> Hm, your addon section does not look like as described in this
> documentation:
> https://github.com/yast/yast-autoinstallation/blob/master/doc/profile_changes_SLE15.md

Sorry, missed the first part of the docu, according to it it should
be correct.

So: bug report with log files, please.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From jpupava at suse.cz  Tue Mar 27 03:23:56 2018
From: jpupava at suse.cz (Jozef Pupava)
Date: Tue, 27 Mar 2018 11:23:56 +0200
Subject: [sle-beta] Autoyast Addons
In-Reply-To: <5AB975230200001500025B7B@prv-mh.provo.novell.com>
References: <5AB975230200001500025B7B@prv-mh.provo.novell.com>
Message-ID: <20180327112356.39fd2848@dzedro.suse.cz>

Hello Jason,

SLE 15 add-ons still Beta, check this site
https://github.com/yast/yast-registration/wiki/Available-SCC-Extensions-for-Use-in-Autoyast

Best Regrds,
Jozef

On Mon, 26 Mar 2018 16:33:07 -0600
"Jason Record" <Jason.Record at suse.com> wrote:

> I'm having trouble including addons in my autoyast control file. 
> 
> I included:
> 
>   <suse_register>
>     <do_registration config:type="boolean">true</do_registration>
>     <email>email at me.com</email>
>     <reg_code>VALID_SLES_REGCODE</reg_code>
>     <install_updates config:type="boolean">true</install_updates>
>     <slp_discovery config:type="boolean">false</slp_discovery>
>   </suse_register>
>   <addons config:type="list">
>     <addon>
>       <name>sle-ha</name>
>       <version>15</version>
>       <arch>x86_64</arch>
>       <reg_code>VALID_HA_REGCODE</reg_code>
>     </addon>
>     <addon>
>       <name>sle-module-basesystem</name>
>       <version>15</version>
>       <arch>x86_64</arch>
>     </addon>
>     <addon>
>       <name>sle-module-server-applications</name>
>       <version>15</version>
>       <arch>x86_64</arch>
>     </addon>
>   </addons>
> 
> The update will register for SLES, but does not include any of the
> addons or HAE.
> 
> Any ideas?
> 
> -jason
> 


From Jason.Record at suse.com  Tue Mar 27 07:34:10 2018
From: Jason.Record at suse.com (Jason Record)
Date: Tue, 27 Mar 2018 07:34:10 -0600
Subject: [sle-beta] Autoyast Addons
In-Reply-To: <20180327100300.GA9767@suse.de>
References: <5AB975230200001500025B7B@prv-mh.provo.novell.com>
	<20180327100300.GA9767@suse.de>
Message-ID: <5ABA48520200001500025C8F@prv-mh.provo.novell.com>

Thanks Thorsten, that was it. <addons> are a subtag for <suse_register>. It's like doing a calculus problem and forgetting how to add :/
-jason

>>> Thorsten Kukuk <kukuk at suse.de> 03/27/18 4:02 AM >>>

Hi,

On Mon, Mar 26, Jason Record wrote:

> I'm having trouble including addons in my autoyast control file.

Hm, your addon section does not look like as described in this
documentation:
https://github.com/yast/yast-autoinstallation/blob/master/doc/profile_changes_SLE15.md

  Thorsten


-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta



From malcolmlewis at cableone.net  Tue Mar 27 17:26:29 2018
From: malcolmlewis at cableone.net (Malcolm)
Date: Tue, 27 Mar 2018 18:26:29 -0500
Subject: [sle-beta] SLED 15 RC2 - Unable to install gnome-shell extensions
	integration
Message-ID: <20180327182629.5b66b784@grover.homelinux.org>

Hi
If I go to https://extensions.gnome.org and try to install the browser
extension it downloads, but is unable to install because it's not
compatible with Firefox 52.7.2. The installed version of
chrome-gnome-shell is 10-1.3 on Leap 42.3 which also uses the same
browser version is 9-1.1 and works fine.

This was working in RC1...

-- 
Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3 | GNOME 3.20.2 | 4.4.120-45-default
HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4
up 1 day 18:36, 1 user, load average: 0.95, 1.04, 1.26

From kukuk at suse.de  Tue Mar 27 23:33:59 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Wed, 28 Mar 2018 07:33:59 +0200
Subject: [sle-beta] Issue with SLED15 RC2
In-Reply-To: <46d4388afb1e43b7aa1a5bb3d7329dc6@EXUSDAGORL02.INTERNAL.ROOT.TES>
References: <46d4388afb1e43b7aa1a5bb3d7329dc6@EXUSDAGORL02.INTERNAL.ROOT.TES>
Message-ID: <20180328053359.GA4243@suse.de>


Hi,

On Wed, Mar 28, Bong Koo wrote:

> Hi,
> 
>  
> 
> I found 2 issues with SLED/S 15 RC2.
> 
>  
> 
> 1.       glibc-devel-2.26-8.21.x86_64 is missing the following 2 groups of
> header files.
> 
> /usr/include/rpcsvc/yp*.h
> 
>                 /usr/include/rpcsvc/nis*.h

They are removed from glibc, you need to install libnsl-devel.
glibc was IPv4 only, libnsl has IPv6 support.
But that's documented in the glibc documentation.

> 2.       /usr/lib64/libnsl.so is missing.

Same as 1.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From Dick.Waite at softwareag.com  Wed Mar 28 01:32:54 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Wed, 28 Mar 2018 07:32:54 +0000
Subject: [sle-beta] SUSEConnect --rollback
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D0120776F73@daeexmbx1.eur.ad.sag>

Grand Wet Morning,

I have a virtual machine at SLES12 SP-3 with up-2-pdate patches applied. It's SCC entry is attached, without keys, showing the full story.

Using a RC-2 installer I run an UPDATE (Migration) to SLES15 RC-2. bar some V3 keys nags which we have had for months, it worked.

I run a couple of tests, looked grand.

I issue SUSEConnect --rollback which from the messages on the virtual machine and the SCC worked but not as I thought, or maybe as I thought.

I wanted to "rollback" the SLES15 RC-2 environment to the original SLES12 SP-3, so that I can amend the SP-3 enviroment and try the UPDATE (Migration) again. It's simple to put the virtual machine back to SP-3 from the snap-shot, but I want to have the SCC back in-sync too so that I could try again.

The SCC did some work, but in the end it's still at SLES15 RC-2, shown in the attached files.

The attached files show the full story.

Question: should the SUSEConnect --rollback command put the SCC back to SLES12 SP-3 after a UPDATE (Migration), if so then I'll create a bug report, if not then how does one get the SCC back in-sync with the virtual machine when it's reloaded with the SLES12 SP-23 snap shot. I did suggest another SCC command which loads the SCC from the machines /etc/zypp area, which would reflect the correct environment, but --rollback was suggested.

Wishing you all a grand day...

__R

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180328/e8aa5983/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: SCC_Log.txt
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180328/e8aa5983/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Rollback-Help.txt
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180328/e8aa5983/attachment-0001.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Members.zip
Type: application/octet-stream
Size: 809901 bytes
Desc: Members.zip
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180328/e8aa5983/attachment.dll>

From kukuk at suse.de  Wed Mar 28 02:10:07 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Wed, 28 Mar 2018 10:10:07 +0200
Subject: [sle-beta] SUSEConnect --rollback
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D0120776F73@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D0120776F73@daeexmbx1.eur.ad.sag>
Message-ID: <20180328081007.GA20886@suse.de>


Hi,

On Wed, Mar 28, Waite, Dick (External) wrote:

> Grand Wet Morning,
> 
> I have a virtual machine at SLES12 SP-3 with up-2-pdate patches applied. It's
> SCC entry is attached, without keys, showing the full story.
> 
> Using a RC-2 installer I run an UPDATE (Migration) to SLES15 RC-2. bar some V3
> keys nags which we have had for months, it worked.
> 
> I run a couple of tests, looked grand.
> 
> I issue SUSEConnect --rollback which from the messages on the virtual machine
> and the SCC worked but not as I thought, or maybe as I thought.
>
> I wanted to "rollback" the SLES15 RC-2 environment to the original SLES12 SP-3,
> so that I can amend the SP-3 enviroment and try the UPDATE (Migration) again.

I suggest to start reading out SLES12 SP3 documentation about rollback:
https://www.suse.com/documentation/sles-12/singlehtml/book_sle_admin/book_sle_admin.html#sec.snapper.snapshot-boot

Nothing has changed there.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From vmoutoussamy at suse.com  Wed Mar 28 03:58:30 2018
From: vmoutoussamy at suse.com (Vincent Moutoussamy)
Date: Wed, 28 Mar 2018 11:58:30 +0200
Subject: [sle-beta] Highlights of YaST Development Sprint 53
Message-ID: <3D24FB54-6EA4-4383-BB21-F9F28A087BB2@suse.com>

"As the release dates for SUSE Linux Enterprise 15 and openSUSE Leap 15 approach,
we keep adapting YaST to make easier for our users to take advantage of all the
new features that these rock-solid operating systems will bring.

During the last two weeks that has implied, apart from regular bug fixing that
we usually don?t cover here, working on AutoYaST, improving Storage-ng and
polishing several aspects related to modules and extensions, like their
registration and licenses.

Let?s start with the rewritten Partitioner that is part of yast2-storage-ng.?

Read more at:
https://lizards.opensuse.org/2018/03/23/yast-sprint-53/

Regards,
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180328/9ed629a7/attachment.sig>

From Dick.Waite at softwareag.com  Wed Mar 28 06:51:05 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Wed, 28 Mar 2018 12:51:05 +0000
Subject: [sle-beta] SUSEConnect --rollback
In-Reply-To: <20180328081007.GA20886@suse.de>
References: <46AC8C81C10B8C48820201DF2AE1D76D0120776F73@daeexmbx1.eur.ad.sag>,
	<20180328081007.GA20886@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D01207772F4@daeexmbx1.eur.ad.sag>

It's a little Brighter,

So  SUSEConnect --rollback is not the way to go. I had been down the path back in early SLES12 so not surprised, but better to try than not try.

So Thorsten what are your thoughts on my solution, the 2nd part of the question. We can very easy and quickly put the virtual machine back to SLES12 SP-3 status from in my case a VMware snap shot. But we have a SCC that reflects the migrated state.

<< Question: should the SUSEConnect --rollback command put the SCC back to SLES12 SP-3 after a UPDATE (Migration), if so then I'll create a bug report, if not then how does one get the SCC back in-sync with the virtual machine when it's reloaded with the SLES12 SP-23 snap shot. I did suggest another SCC command which loads the SCC from the machines /etc/zypp area, which would reflect the correct environment, but --rollback was suggested. >>

The /etc/zypp area seems to have the information, maybe not all ? so a SUSEConnect --sync-scc could be a quick and simple way of bringing the status of the machine and SCC together.  We will have to be doing this often, for each Beta in SLES15 and the SLES releases. At the moment one has to run a series of commands when the data needed I expect is there and just has to be written to the SCC....

Regards,

__R

________________________________________
From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
Sent: 28 March 2018 10:10
To: sle-beta at lists.suse.com
Subject: Re: [sle-beta] SUSEConnect --rollback

Hi,

On Wed, Mar 28, Waite, Dick (External) wrote:

> Grand Wet Morning,
>
> I have a virtual machine at SLES12 SP-3 with up-2-pdate patches applied. It's
> SCC entry is attached, without keys, showing the full story.
>
> Using a RC-2 installer I run an UPDATE (Migration) to SLES15 RC-2. bar some V3
> keys nags which we have had for months, it worked.
>
> I run a couple of tests, looked grand.
>
> I issue SUSEConnect --rollback which from the messages on the virtual machine
> and the SCC worked but not as I thought, or maybe as I thought.
>
> I wanted to "rollback" the SLES15 RC-2 environment to the original SLES12 SP-3,
> so that I can amend the SP-3 enviroment and try the UPDATE (Migration) again.

I suggest to start reading out SLES12 SP3 documentation about rollback:
https://www.suse.com/documentation/sles-12/singlehtml/book_sle_admin/book_sle_admin.html#sec.snapper.snapshot-boot

Nothing has changed there.

  Thorsten

--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From kukuk at suse.de  Wed Mar 28 07:10:18 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Wed, 28 Mar 2018 15:10:18 +0200
Subject: [sle-beta] SUSEConnect --rollback
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D01207772F4@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D0120776F73@daeexmbx1.eur.ad.sag>
	<20180328081007.GA20886@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D01207772F4@daeexmbx1.eur.ad.sag>
Message-ID: <20180328131018.GA5282@suse.de>

On Wed, Mar 28, Waite, Dick (External) wrote:

> It's a little Brighter,
> 
> So  SUSEConnect --rollback is not the way to go. I had been down the path back in early SLES12 so not surprised, but better to try than not try.

If you assume that "SUSEConnect --rollback" will rollback the data on your
disk, too, then this is not the way to go. "SUSEConnect --rollback" will read
/etc/zypp and tell SCC what is really installed, nothing else.
If you do the filesystem rollback first, e.g. with btrfs and snapper, then 
you don't need to care, the system is clever enough to run the command for
you during first boot.
If you use something different, like VMware snapshots, you need to call
SUSEConnect --rollback. But it is important, that you do the filesystem
rollback first and that the filesystem is really at SLES12 SP3 level, 
including the service and other files in /etc/zypp.

And this works fine, we tested this often enough the last days with RC2
to hunt another bug.

Rollback is really great to debug problems :)

> So Thorsten what are your thoughts on my solution, the 2nd part of the question. We can very easy and quickly put the virtual machine back to SLES12 SP-3 status from in my case a VMware snap shot. But we have a SCC that reflects the migrated state.

See above. But you did not mention in your first Mail that you did a
filesystem rollback before you did call "SUSEConnect --rollback", and
normally, if people don't mention this, they really didn't do that.

And you still don't mention what your problem is, except that the
outcome is not what you expect. But you did neither wrote what you
expect nor what the difference is.
So there is no way for us to help you since we don't know your problem.

>From our testing here I can only say: it's working as expected.

  Thorsten

> 
> << Question: should the SUSEConnect --rollback command put the SCC back to SLES12 SP-3 after a UPDATE (Migration), if so then I'll create a bug report, if not then how does one get the SCC back in-sync with the virtual machine when it's reloaded with the SLES12 SP-23 snap shot. I did suggest another SCC command which loads the SCC from the machines /etc/zypp area, which would reflect the correct environment, but --rollback was suggested. >>
> 
> The /etc/zypp area seems to have the information, maybe not all ? so a SUSEConnect --sync-scc could be a quick and simple way of bringing the status of the machine and SCC together.  We will have to be doing this often, for each Beta in SLES15 and the SLES releases. At the moment one has to run a series of commands when the data needed I expect is there and just has to be written to the SCC....
> 
> Regards,
> 
> __R
> 
> ________________________________________
> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
> Sent: 28 March 2018 10:10
> To: sle-beta at lists.suse.com
> Subject: Re: [sle-beta] SUSEConnect --rollback
> 
> Hi,
> 
> On Wed, Mar 28, Waite, Dick (External) wrote:
> 
> > Grand Wet Morning,
> >
> > I have a virtual machine at SLES12 SP-3 with up-2-pdate patches applied. It's
> > SCC entry is attached, without keys, showing the full story.
> >
> > Using a RC-2 installer I run an UPDATE (Migration) to SLES15 RC-2. bar some V3
> > keys nags which we have had for months, it worked.
> >
> > I run a couple of tests, looked grand.
> >
> > I issue SUSEConnect --rollback which from the messages on the virtual machine
> > and the SCC worked but not as I thought, or maybe as I thought.
> >
> > I wanted to "rollback" the SLES15 RC-2 environment to the original SLES12 SP-3,
> > so that I can amend the SP-3 enviroment and try the UPDATE (Migration) again.
> 
> I suggest to start reading out SLES12 SP3 documentation about rollback:
> https://www.suse.com/documentation/sles-12/singlehtml/book_sle_admin/book_sle_admin.html#sec.snapper.snapshot-boot
> 
> Nothing has changed there.
> 
>   Thorsten
> 
> --
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta
> 
> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
> 

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From Dick.Waite at softwareag.com  Wed Mar 28 15:47:24 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Wed, 28 Mar 2018 21:47:24 +0000
Subject: [sle-beta] SUSEConnect --rollback
In-Reply-To: <20180328131018.GA5282@suse.de>
References: <46AC8C81C10B8C48820201DF2AE1D76D0120776F73@daeexmbx1.eur.ad.sag>
	<20180328081007.GA20886@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D01207772F4@daeexmbx1.eur.ad.sag>,
	<20180328131018.GA5282@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012077765F@daeexmbx1.eur.ad.sag>

Grand Evening Thorsten,

Now I understand how to use SUSEConnect --rollback it's working as designed. We did try this in Beta4 / 5 time frame but had issues. These could well have been the issues we had Beta 7 and fixed / understood.

I also had the idea --rollback was close connected to Brtrs which we don't use. But it is working with VMware as you state and I thank you for the good words.

I have ran two Migrations and then switched back to SLES12 via VMware snapshot and running --rollback and no issues with the operation.

I'm seeing a lot more message about key V3 but they have been around for some time. By using "solver.onlyRequired = true" the Migration fits on the disks.

I'll try some more tomorrow and keep the nag warnings and messages. A zypper ve is giving the build the Okay.

Again many thanks for the update.

__R

 ________________________________________
From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
Sent: 28 March 2018 15:10
To: sle-beta at lists.suse.com
Subject: Re: [sle-beta] SUSEConnect --rollback

On Wed, Mar 28, Waite, Dick (External) wrote:

> It's a little Brighter,
>
> So  SUSEConnect --rollback is not the way to go. I had been down the path back in early SLES12 so not surprised, but better to try than not try.

If you assume that "SUSEConnect --rollback" will rollback the data on your
disk, too, then this is not the way to go. "SUSEConnect --rollback" will read
/etc/zypp and tell SCC what is really installed, nothing else.
If you do the filesystem rollback first, e.g. with btrfs and snapper, then
you don't need to care, the system is clever enough to run the command for
you during first boot.
If you use something different, like VMware snapshots, you need to call
SUSEConnect --rollback. But it is important, that you do the filesystem
rollback first and that the filesystem is really at SLES12 SP3 level,
including the service and other files in /etc/zypp.

And this works fine, we tested this often enough the last days with RC2
to hunt another bug.

Rollback is really great to debug problems :)

> So Thorsten what are your thoughts on my solution, the 2nd part of the question. We can very easy and quickly put the virtual machine back to SLES12 SP-3 status from in my case a VMware snap shot. But we have a SCC that reflects the migrated state.

See above. But you did not mention in your first Mail that you did a
filesystem rollback before you did call "SUSEConnect --rollback", and
normally, if people don't mention this, they really didn't do that.

And you still don't mention what your problem is, except that the
outcome is not what you expect. But you did neither wrote what you
expect nor what the difference is.
So there is no way for us to help you since we don't know your problem.

>From our testing here I can only say: it's working as expected.

  Thorsten

>
> << Question: should the SUSEConnect --rollback command put the SCC back to SLES12 SP-3 after a UPDATE (Migration), if so then I'll create a bug report, if not then how does one get the SCC back in-sync with the virtual machine when it's reloaded with the SLES12 SP-23 snap shot. I did suggest another SCC command which loads the SCC from the machines /etc/zypp area, which would reflect the correct environment, but --rollback was suggested. >>
>
> The /etc/zypp area seems to have the information, maybe not all ? so a SUSEConnect --sync-scc could be a quick and simple way of bringing the status of the machine and SCC together.  We will have to be doing this often, for each Beta in SLES15 and the SLES releases. At the moment one has to run a series of commands when the data needed I expect is there and just has to be written to the SCC....
>
> Regards,
>
> __R
>
> ________________________________________
> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Thorsten Kukuk [kukuk at suse.de]
> Sent: 28 March 2018 10:10
> To: sle-beta at lists.suse.com
> Subject: Re: [sle-beta] SUSEConnect --rollback
>
> Hi,
>
> On Wed, Mar 28, Waite, Dick (External) wrote:
>
> > Grand Wet Morning,
> >
> > I have a virtual machine at SLES12 SP-3 with up-2-pdate patches applied. It's
> > SCC entry is attached, without keys, showing the full story.
> >
> > Using a RC-2 installer I run an UPDATE (Migration) to SLES15 RC-2. bar some V3
> > keys nags which we have had for months, it worked.
> >
> > I run a couple of tests, looked grand.
> >
> > I issue SUSEConnect --rollback which from the messages on the virtual machine
> > and the SCC worked but not as I thought, or maybe as I thought.
> >
> > I wanted to "rollback" the SLES15 RC-2 environment to the original SLES12 SP-3,
> > so that I can amend the SP-3 enviroment and try the UPDATE (Migration) again.
>
> I suggest to start reading out SLES12 SP3 documentation about rollback:
> https://www.suse.com/documentation/sles-12/singlehtml/book_sle_admin/book_sle_admin.html#sec.snapper.snapshot-boot
>
> Nothing has changed there.
>
>   Thorsten
>
> --
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
> _______________________________________________
> sle-beta mailing list
> sle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta
>
> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
>

--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta

From fcrozat at suse.com  Thu Mar 29 02:39:53 2018
From: fcrozat at suse.com (Frederic Crozat)
Date: Thu, 29 Mar 2018 10:39:53 +0200
Subject: [sle-beta] Broadcast message with wall not working on SLE15RC2
In-Reply-To: <5ABC7A860200004D00061000@mail.triples.at>
References: <5ABC7A860200004D00061000@mail.triples.at>
Message-ID: <1522312793.16059.1.camel@suse.com>

Le jeudi 29 mars 2018 ? 07:32 +0200, Peter jahn a ?crit :
> Hi everyone
> 
> The wall command is used to send a message to all users. On SLES15RC2
> the command:
> 
> wall "My Message"
> 
> finish without error but none of the logged in users is receiving the
> broadcast message.

Please open a bug report.

Thanks !

-- 
Frederic Crozat
Enterprise Desktop Release Manager
SUSE


From kukuk at suse.de  Thu Mar 29 02:43:59 2018
From: kukuk at suse.de (Thorsten Kukuk)
Date: Thu, 29 Mar 2018 10:43:59 +0200
Subject: [sle-beta] Broadcast message with wall not working on SLE15RC2
In-Reply-To: <5ABC7A860200004D00061000@mail.triples.at>
References: <5ABC7A860200004D00061000@mail.triples.at>
Message-ID: <20180329084359.GA21043@suse.de>

On Thu, Mar 29, Peter jahn wrote:

> 
> Hi everyone
> The wall command is used to send a message to all users. On SLES15RC2 the command:
> wall "My Message" 
> finish without error but none of the logged in users is receiving the broadcast message.

Does not help you, but works fine for me with RC2.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From Dick.Waite at softwareag.com  Sat Mar 31 09:19:49 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Sat, 31 Mar 2018 15:19:49 +0000
Subject: [sle-beta] Gnome and a good Script
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D012077863E@daeexmbx1.eur.ad.sag>

Happy Easter,

We have some young people starting with us after Easter and the will be working on SLES15.. Gnome is the display manager and for us old people it's not our DM of choice, but I need the help to find a good "script" for Gnome that we can use with the new people. It needs to be able to write the terminal output to a file in /tmp/logs with a file name that has the "hostname" - Date - time and what ever you think is helpful. We need to be able to guide and help the good people and also pass results back to the Universality in Darmstadt. From my look around the web there are quite a few, but I was thinking on this forum I'm sure there is the best of the best.

We will of course also give them a ride around the block on KDE, but later in the year, keeping the best of last ;o)

__R

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180331/40b2c0cc/attachment.htm>

From malcolmlewis at cableone.net  Sat Mar 31 10:31:43 2018
From: malcolmlewis at cableone.net (Malcolm)
Date: Sat, 31 Mar 2018 11:31:43 -0500
Subject: [sle-beta] Gnome and a good Script
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D012077863E@daeexmbx1.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D012077863E@daeexmbx1.eur.ad.sag>
Message-ID: <20180331113143.4ad12110@grover.homelinux.org>

On Sat, 31 Mar 2018 15:19:49 +0000
"Waite, Dick (External)" <Dick.Waite at softwareag.com> wrote:

> Happy Easter,
> 
> We have some young people starting with us after Easter and the will
> be working on SLES15.. Gnome is the display manager and for us old
> people it's not our DM of choice, but I need the help to find a good
> "script" for Gnome that we can use with the new people. It needs to
> be able to write the terminal output to a file in /tmp/logs with a
> file name that has the "hostname" - Date - time and what ever you
> think is helpful. We need to be able to guide and help the good
> people and also pass results back to the Universality in Darmstadt.
> From my look around the web there are quite a few, but I was thinking
> on this forum I'm sure there is the best of the best.
> 
> We will of course also give them a ride around the block on KDE, but
> later in the year, keeping the best of last ;o)
> 
Hi
Do you mean a key/command logger? Or just a history of what was
typed in the terminal session? What is the default shell in use?

-- 
Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3 | GNOME 3.20.2 | 4.4.120-45-default
HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4
up 5 days 11:39, 1 user, load average: 1.28, 1.05, 1.18

From Dick.Waite at softwareag.com  Sat Mar 31 10:45:12 2018
From: Dick.Waite at softwareag.com (Waite, Dick (External))
Date: Sat, 31 Mar 2018 16:45:12 +0000
Subject: [sle-beta] Gnome and a good Script
In-Reply-To: <20180331113143.4ad12110@grover.homelinux.org>
References: <46AC8C81C10B8C48820201DF2AE1D76D012077863E@daeexmbx1.eur.ad.sag>,
	<20180331113143.4ad12110@grover.homelinux.org>
Message-ID: <20180331164511.5632087.158.33739@softwareag.com>

We need the history of what was typed in on their terminal. I don't think there is a default? But we older people are all KDE and not very familiar with grand cpu eater Gnome ;o)
__R

Sent from my BlackBerry 10 smartphone.
  Original Message
From: Malcolm
Sent: Saturday, 31 March 2018 18:32
To: sle-beta at lists.suse.com
Subject: Re: [sle-beta] Gnome and a good Script


On Sat, 31 Mar 2018 15:19:49 +0000
"Waite, Dick (External)" <Dick.Waite at softwareag.com> wrote:

> Happy Easter,
>
> We have some young people starting with us after Easter and the will
> be working on SLES15.. Gnome is the display manager and for us old
> people it's not our DM of choice, but I need the help to find a good
> "script" for Gnome that we can use with the new people. It needs to
> be able to write the terminal output to a file in /tmp/logs with a
> file name that has the "hostname" - Date - time and what ever you
> think is helpful. We need to be able to guide and help the good
> people and also pass results back to the Universality in Darmstadt.
> From my look around the web there are quite a few, but I was thinking
> on this forum I'm sure there is the best of the best.
>
> We will of course also give them a ride around the block on KDE, but
> later in the year, keeping the best of last ;o)
>
Hi
Do you mean a key/command logger? Or just a history of what was
typed in the terminal session? What is the default shell in use?

--
Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3 | GNOME 3.20.2 | 4.4.120-45-default
HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4
up 5 days 11:39, 1 user, load average: 1.28, 1.05, 1.18
_______________________________________________
sle-beta mailing list
sle-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sle-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From malcolmlewis at cableone.net  Sat Mar 31 13:28:30 2018
From: malcolmlewis at cableone.net (Malcolm)
Date: Sat, 31 Mar 2018 14:28:30 -0500
Subject: [sle-beta] Gnome and a good Script
In-Reply-To: <20180331164511.5632087.158.33739@softwareag.com>
References: <46AC8C81C10B8C48820201DF2AE1D76D012077863E@daeexmbx1.eur.ad.sag>
	<20180331113143.4ad12110@grover.homelinux.org>
	<20180331164511.5632087.158.33739@softwareag.com>
Message-ID: <20180331142830.557b16aa@grover.homelinux.org>

On Sat, 31 Mar 2018 16:45:12 +0000
"Waite, Dick (External)" <Dick.Waite at softwareag.com> wrote:

> We need the history of what was typed in on their terminal. I don't
> think there is a default? But we older people are all KDE and not
> very familiar with grand cpu eater Gnome ;o) __R
> 
<snip>
Hi
It's nothing to do with desktop environment in use, so it's alright for
the moment since you won't melt your system with a plasma ray.... ;)

The default shell is /bin/bash, doesn't matter witch terminal is used,
xterm, gnome-terminal, konsole etc and the end of the terminal session
it will write out to the ~/.bash_history.....

Unfortunately if a user runs history -c it's all gone for that
session.....

Or are you wanting the user to run something when requested?

FWIW, I would suggest a tool like sysdig may be easier for the admin to
use (Available via package hub, maybe not ready for SLE 15)?
https://www.tecmint.com/sysdig-system-monitoring-and-troubleshooting-tool-for-linux/

Use the command;
sysdig -c spy_users

-- 
Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3 | GNOME 3.20.2 | 4.4.120-45-default
HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4
up 5 days 14:36, 1 user, load average: 5.87, 5.30, 3.79