A new version is finally out. We need to test it and see if anything is broken. Also need to evaluate if we should recommended it instead of SLE 11.
The aim is to test out SLE12 with Workstation extension, the workstation extension adds desktop parts of SLED to SLES. There are indications that workstation extension is select upon installation from standard SLE12 media and that it should be available for evaluation. So first step is to install an 60days eval to verify this.
(In reply to comment #1) > There are indications that workstation extension is select upon installation > from standard SLE12 media and that it should be available for evaluation. So > first step is to install an 60days eval to verify this. During installation I could not select anything named "Workstation Extension", however a graphical environment (GNOME) is selected by default and should work as expected for the test of SLE12.
tl-setup fails resolve packages for installation, zypper backend seems to have changed: 2015-01-14 16:46:22,704: Adding package lsb-core-amd64 2015-01-14 16:46:22,704: Adding package lsb-graphics-amd64 2015-01-14 16:46:25,573: Resolving packages... 2015-01-14 16:46:25,574: Creating zypper lock... 2015-01-14 16:46:25,574: Locked zypper 2015-01-14 16:46:25,574: Verifying package name lsb-core-amd64 2015-01-14 16:46:25,575: Unlocking zypper... 2015-01-14 16:46:25,575: Removed zypper lock 2015-01-14 16:46:26,595: zypper: Command 'what-provides' is replaced by 'search --provides --match-exact'. 2015-01-14 16:46:26,597: zypper: See 'help search' for all available options. 2015-01-14 16:46:26,597: zypper: Loading repository data... 2015-01-14 16:46:26,597: zypper: Reading installed packages... 2015-01-14 16:46:26,597: zypper: No packages found. 2015-01-14 16:46:26,598: Creating zypper lock... 2015-01-14 16:46:26,598: Locked zypper 2015-01-14 16:46:26,598: No package found providing lsb-core-amd64 2015-01-14 16:46:26,598: Failed to resolve dependencies, one or more packages are unavailable on this distribution 2015-01-14 16:46:26,599: Failure resolving packages. 2015-01-14 16:46:32,758: Unlocking zypper...
(In reply to comment #3) > tl-setup fails resolve packages for installation, > zypper backend seems to have changed: > Note that ThinLinc installer works as expected, looking up installed packages and installs thinlinc packages correctly.
pygtk is not installed per default and text mode installation/setup is forced. If one installs package 'python-gtk' the graphical interface works as expected.
thinlinc services are defined, added and enabled in firewall, however sshd is not.
(In reply to comment #6) > thinlinc services are defined, added and enabled in firewall, however sshd is > not. The reason for that is that system type is not detected as it should using out systemtype.py. The problem is easily fixed, /etc/novell-release has been renamed to /etc/SuSE-release so i just created the symbolic link /etc/novell-release. The link above fixes the detection of the OS and tlsetup.log shows correct values are identified and the ssh firewall service is now enabled; 2015-01-15 12:52:42,771: Operating system: Linux 2015-01-15 12:52:42,771: Architecture: x86_64 2015-01-15 12:52:42,771: Distribution: SLES 2015-01-15 12:52:42,771: Distribution version: 12 2015-01-15 12:52:42,771: Distribution family: SLE
I can't find any information about SLES12 being LSB certified. The only official LSB related information is that SLES12 is SysV LSB complient. There are only one package related to lsb in repos which provides the lsb_release command which reports "LSB Version: N/A".
(In reply to comment #7) > (In reply to comment #6) > > thinlinc services are defined, added and enabled in firewall, however sshd is > > not. > > The reason for that is that system type is not detected as it should using out > systemtype.py. The problem is easily fixed, /etc/novell-release has been > renamed to /etc/SuSE-release so i just created the symbolic link > /etc/novell-release. > > The link above fixes the detection of the OS and tlsetup.log shows correct > values are identified and the ssh firewall service is now enabled; > > 2015-01-15 12:52:42,771: Operating system: Linux > 2015-01-15 12:52:42,771: Architecture: x86_64 > 2015-01-15 12:52:42,771: Distribution: SLES > 2015-01-15 12:52:42,771: Distribution version: 12 > 2015-01-15 12:52:42,771: Distribution family: SLE SLES 12 doesn't ship a /etc/system-release-cpe however the file /etc/os-release contains a cpe entry; CPE_NAME="cpe:/o:suse:sles:12"
(In reply to comment #3) > 2015-01-14 16:46:26,595: zypper: Command 'what-provides' is replaced by 'search > --provides --match-exact'. > 2015-01-14 16:46:26,597: zypper: See 'help search' for all available options. > 2015-01-14 16:46:26,597: zypper: Loading repository data... > 2015-01-14 16:46:26,597: zypper: Reading installed packages... > 2015-01-14 16:46:26,597: zypper: No packages found. Bug #5403 added for this issue, the message about 'what-provides' is irrelevant, the main problem is that the xml output format has changed for the command.
(In reply to comment #8) > I can't find any information about SLES12 being LSB certified. The only > official LSB related information is that SLES12 is SysV LSB complient. > > There are only one package related to lsb in repos which provides the > lsb_release command which reports "LSB Version: N/A". Bug #5404 added for this issue.
HTML5 client can't authenticate a user.
(In reply to comment #12) > HTML5 client can't authenticate a user. Bug #5407 was added for this issue.
No issues was found in tlwebadm and it's functionality. Tested start/stop of service, killing session and verified that information present was sane such as load. No issues was found connecting and using a session with a native client Tested thinlocal printing, local drives, smartcard redirection and audio..
Verified basic functionality using a client such as local drive, smartcard, sound etc.
