From Dick.Waite at softwareag.com Tue Mar 10 05:36:23 2015 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Tue, 10 Mar 2015 11:36:23 +0000 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> Grand Day, My checks with x86_64 on SLES have gone well. So looking at a zLinux update this week, which is good news. What has been APITA is the grand Ping_Pong being played between VMware and SUSE with ?Tools?. With SP3 one used VMware tools for Workstation and one was happy. You run an update and the good people of SUSE say, we can do better and pop into the mix their ?open-vm-tools and libvmtools?, You have not asked for this, it?s just done, not check to see if this is a ?VMware Workstation?. So you finish the update and all looks Okay, so you then run a VMware tools update ?cos you know you have a new kernel. I?m running VMware Workstation 11.1.0 which has tools 9.9.2_2496486 and it?s not given me any issues, so far. Re-load after the tools update and Wow? what?s has my mouse been smoking !!!!! It?s all over the shop, umm better close down, Wow why is the stop script saying it?s not a happy badger?. One does look around and after the fun and games with SLE12 it?s quite easy to see the ?open-vm-tools? are back again giving my mouse something that sends it in circles? If you kill the open-vm-tools and set it to never again darken your door, run the VMware tools again and reload then you have a mouse the is back under control and scripts that start and stop when asked. I do not understand what the open-vm-tools are there for. If you are running VMware software then you have their tools, which get updated quite often. If your not running VMware why would you want open-vm-tools ? __R From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of urs.frey at post.ch Sent: Montag, 9. M?rz 2015 16:59 To: sles-beta at lists.suse.com Subject: [sles-beta] SLES11-SP4 beta2 x86_64 Hi all Did some fist installation SLES-11-SP4-beta2 x86_64 using autoyast on a HP Proliant Blade BL460cGen8 attached to SAN EMC. No problems so far. Autoyast, FCoE and multipathing working as it worked on SP3 Saw new kernel version: 3.0.101-50-default == OK, big difference in version numbering from the existing SP3 3.0.101-0.46-default, so difficulties when doing upgrades will not occur concerning kernel versioning. Best regards Urs Frey Post CH AG Informationstechnologie IT Betrieb Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlatimer at suse.com Tue Mar 10 08:20:21 2015 From: mlatimer at suse.com (Mike Latimer) Date: Tue, 10 Mar 2015 08:20:21 -0600 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> Message-ID: <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> Hi, On Tuesday, March 10, 2015 11:36:23 AM Waite, Dick wrote: > What has been APITA is the grand Ping_Pong being played between VMware and > SUSE with ?Tools?. With SP3 one used VMware tools for Workstation and one > was happy. You run an update and the good people of SUSE say, we can do > better and pop into the mix their ?open-vm-tools and libvmtools?, You have > not asked for this, it?s just done, not check to see if this is a ?VMware > Workstation?. Thanks for reporting this, and sorry for the troubles. Last time I tested VMware-workstation, installing VMware tools was done through a tarball, rather than an RPM, so I was not expecting the update process to find anything to update. > So you finish the update and all looks Okay, so you then run a VMware tools > update ?cos you know you have a new kernel. I?m running VMware Workstation > 11.1.0 which has tools 9.9.2_2496486 and it?s not given me any issues, so > far. Re-load after the tools update and Wow? what?s has my mouse been > smoking !!!!! It?s all over the shop, umm better close down, Wow why is the > stop script saying it?s not a happy badger?. > One does look around and after the fun and games with SLE12 it?s quite easy > to see the ?open-vm-tools? are back again giving my mouse something that > sends it in circles? I thought we had everything worked out in the SLE12 environment - other than the gtkmm-2.4/3.0 issue. If there are any outstanding issues, I'd like to understand them and get a bug filed. > If you kill the open-vm-tools and set it to never again darken your door, > run the VMware tools again and reload then you have a mouse the is back > under control and scripts that start and stop when asked. > I do not understand what the open-vm-tools are there for. If you are running > VMware software then you have their tools, which get updated quite often. > If your not running VMware why would you want open-vm-tools ? In theory, including the tools with the distribution should have helped users avoid the step of installing additional software after the installation has completed. If conflicts are continuing to be seen, we need to get them resolved or rethink this approach. I'll do some testing today, but any further details you can provide (probably off-list) would be appreciated. Thanks! Mike From urs.frey at post.ch Tue Mar 10 08:54:24 2015 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 10 Mar 2015 14:54:24 +0000 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B1AEC3889@HXMB12.pnet.ch> Hi all Until now SLES11-SP3 hat no open-vm-tools included, fact. Now when I do an online update from SLES11-SP3 to SLES11-SP4 using zypper --non-interactive dist-upgrade --auto-agree-with-licenses I find open-vm-tools installed ================= Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW packages are going to be installed: crash-eppic libevent-1_4-2 libgmodule-2_0-0 libiptc0 liblzmadec0 libnfnetlink0 libvmtools0 libxtables9 lzma nfs-client nfsidmap open-vm-tools release-notes-sles rpcbind The following package is going to be REMOVED: crash-sial The following packages are going to be upgraded: at audit audit-libs bash bash-doc bind-libs bind-utils boost-license brocade-firmware cifs-utils cpupower crash desktop-translations e2fsprogs efibootmgr elilo gfxboot gfxboot-branding-SLES hwinfo iproute2 iptables kdump kernel-default kernel-default-base kernel-default-devel kernel-source libboost_regex1_36_0 libcom_err2 libext2fs2 libgcc43 libgcc46 libgcc_s1 libgomp1 libnuma1 libreadline5 libstdc++43 libstdc++46 libstdc++6 libzypp linux-kernel-headers makedumpfile mcelog mdadm mkinitrd ntp numactl openssh parted pciutils-ids perl-Bootloader pwdutils readline-doc satsolver-tools sles-release sles-release-DVD syslinux sysvinit xorg-x11-libX11 xorg-x11-libXext xorg-x11-libXfixes xorg-x11-libXp xorg-x11-libXrender xorg-x11-libXt xorg-x11-libXv xorg-x11-libs xorg-x11-xauth yast2 yast2-bootloader yast2-http-server yast2-installation yast2-iscsi-client yast2-iscsi-server yast2-network yast2-nfs-client yast2-ntp-client yast2-online-update yast2-online-update-frontend yast2-packager yast2-pkg-bindings yast2-samba-server yast2-storage yast2-storage-lib yast2-trans-en_US yast2-update yast2-vm zypper zypper-log The following product is going to be upgraded: SUSE Linux Enterprise Server 11 SP3 The following packages are not supported by their vendor: liblzmadec0 lzma 87 packages to upgrade, 14 new, 1 to remove. Overall download size: 164.6 MiB. After the operation, additional 14.6 MiB will be used. Continue? [y/n/? shows all options] (y): y Automatically agreeing with SUSE Linux Enterprise Server 11 SP4 product license. ================ I do now have two sorts of VMWare Tools installed, which is really not wanted vtsteh:~ # rpm -qa | grep -i vm | grep -i tools pst-VMwareTools-9.4.11-2400950 libvmtools0-9.4.6-1.1 open-vm-tools-9.4.6-1.1 vtsteh:~ # The problem is now, that within a simple service pack update absolutely NO architecture change must be done. Else there should also be updates to perl 5.16, Apache 2.4, Tomcat 7, java 8, php5.5 etc. So in my mind SLES11 should keep being without open-vm-tools and let us keep the original ESX VMwareTools OK, I could write a script to remove the previously installed ESX Tools, change all system settings back to native and let the door open to open-vm-tools. But this is lot of engineering reverting and has nothing to do anymore with a simple service-pack. BUT: how much can we then say "it is only a service-pack update". In my mind service pack does mean solely security fixes, HW enablement and minor updates, but no architecture, no methods change please. No automated installation of new things where one has to reverse-engineer to know where it comes from and find an own way to work around. So please think the subject with these open-vm-tools over. And if you come to a result, that open-vm-tools is a must, then declare SLES11-SP4 as a new release with major changes please. Not only a service-pack update Thanks Best regards Urs Frey????????????????????????????????????????????? Post CH AG Informationstechnologie IT Betrieb Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Mike Latimer Gesendet: Tuesday, March 10, 2015 3:20 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... Hi, On Tuesday, March 10, 2015 11:36:23 AM Waite, Dick wrote: > What has been APITA is the grand Ping_Pong being played between VMware and > SUSE with ?Tools?. With SP3 one used VMware tools for Workstation and one > was happy. You run an update and the good people of SUSE say, we can do > better and pop into the mix their ?open-vm-tools and libvmtools?, You have > not asked for this, it?s just done, not check to see if this is a ?VMware > Workstation?. Thanks for reporting this, and sorry for the troubles. Last time I tested VMware-workstation, installing VMware tools was done through a tarball, rather than an RPM, so I was not expecting the update process to find anything to update. > So you finish the update and all looks Okay, so you then run a VMware tools > update ?cos you know you have a new kernel. I?m running VMware Workstation > 11.1.0 which has tools 9.9.2_2496486 and it?s not given me any issues, so > far. Re-load after the tools update and Wow? what?s has my mouse been > smoking !!!!! It?s all over the shop, umm better close down, Wow why is the > stop script saying it?s not a happy badger?. > One does look around and after the fun and games with SLE12 it?s quite easy > to see the ?open-vm-tools? are back again giving my mouse something that > sends it in circles? I thought we had everything worked out in the SLE12 environment - other than the gtkmm-2.4/3.0 issue. If there are any outstanding issues, I'd like to understand them and get a bug filed. > If you kill the open-vm-tools and set it to never again darken your door, > run the VMware tools again and reload then you have a mouse the is back > under control and scripts that start and stop when asked. > I do not understand what the open-vm-tools are there for. If you are running > VMware software then you have their tools, which get updated quite often. > If your not running VMware why would you want open-vm-tools ? In theory, including the tools with the distribution should have helped users avoid the step of installing additional software after the installation has completed. If conflicts are continuing to be seen, we need to get them resolved or rethink this approach. I'll do some testing today, but any further details you can provide (probably off-list) would be appreciated. Thanks! Mike _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From mlatimer at suse.com Tue Mar 10 10:17:47 2015 From: mlatimer at suse.com (Mike Latimer) Date: Tue, 10 Mar 2015 10:17:47 -0600 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <40637DBB36AF3941B243A286A432CA0B1AEC3889@HXMB12.pnet.ch> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> <40637DBB36AF3941B243A286A432CA0B1AEC3889@HXMB12.pnet.ch> Message-ID: <3696080.UuFptH8s86@mlatimer1.dnsdhcp.provo.novell.com> On Tuesday, March 10, 2015 02:54:24 PM urs.frey at post.ch wrote: > Hi all > > Until now SLES11-SP3 hat no open-vm-tools included, fact. That's correct. > Now when I do an online update from SLES11-SP3 to SLES11-SP4 using zypper > --non-interactive dist-upgrade --auto-agree-with-licenses I find > open-vm-tools installed ================= > Warning: You are about to do a distribution upgrade with all enabled > repositories. Make sure these repositories are compatible before you > continue. See 'man zypper' for more information about this command. > Loading repository data... > Reading installed packages... > Computing distribution upgrade... > > The following NEW packages are going to be installed: > crash-eppic libevent-1_4-2 libgmodule-2_0-0 libiptc0 liblzmadec0 > libnfnetlink0 libvmtools0 libxtables9 lzma nfs-client nfsidmap > open-vm-tools release-notes-sles rpcbind That was not expected (at least from my side), and is certainly not desirable. Can of you open a service request so we can get a bug to track this? > I do now have two sorts of VMWare Tools installed, which is really not > wanted > vtsteh:~ # rpm -qa | grep -i vm | grep -i tools > pst-VMwareTools-9.4.11-2400950 > libvmtools0-9.4.6-1.1 > open-vm-tools-9.4.6-1.1 > > The problem is now, that within a simple service pack update absolutely NO > architecture change must be done. Else there should also be updates to > perl 5.16, Apache 2.4, Tomcat 7, java 8, php5.5 etc. > So in my mind SLES11 should keep being without open-vm-tools and let us keep > the original ESX VMwareTools > OK, I could write a script to remove the previously installed ESX Tools, > change all system settings back to native and let the door open to > open-vm-tools. But this is lot of engineering reverting and has nothing to > do anymore with a simple service-pack. > BUT: > how much can we then say "it is only a service-pack update". > In my mind service pack does mean solely security fixes, HW enablement and > minor updates, but no architecture, no methods change please. No automated > installation of new things where one has to reverse-engineer to know where > it comes from and find an own way to work around. > So please think the subject with these open-vm-tools over. > And if you come to a result, that open-vm-tools is a must, then declare > SLES11-SP4 as a new release with major changes please. Not only a > service-pack update The inclusion of open-vm-tools was intended as a convenience change - not a challenge to overcome. ;) I'll finish my testing and we will either drop the package, or fix the dependency so it is not automatically installed (which was the original intent). Thanks again for making me aware of this. -Mike From hare at suse.com Tue Mar 10 11:54:13 2015 From: hare at suse.com (Hannes Reinecke) Date: Tue, 10 Mar 2015 13:54:13 -0400 Subject: [sles-beta] SLES11-SP4 multipath problems, SAN path does not get reinstated after path failure In-Reply-To: <40637DBB36AF3941B243A286A432CA0B1AEC38BF@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B1AEC38BF@HXMB12.pnet.ch> Message-ID: <54FF2FC5.20406@suse.com> On 03/10/2015 11:34 AM, urs.frey at post.ch wrote: > Hi all > > I have installed SLES11-SP4 x86_64 on a HP Proliant BL460cgen8 attached to SAN EMC, FCoE. > > When failing a SAN path, I can observe, that the SAN path does not get reinstated after SAN link up again. > Multipath tools do loose all LUNs > > h05cni:~ # multipath -ll > 360000970000295700687533031374132 dm-2 > size=34G features='0' hwhandler='0' wp=rw > 360000970000295700687533031374131 dm-1 > size=34G features='0' hwhandler='0' wp=rw > 360000970000295700687533031374130 dm-0 > size=34G features='0' hwhandler='0' wp=rw > 360000970000295700687533031443339 dm-3 > size=34G features='0' hwhandler='0' wp=rw > h05cni:~ # > > Mar 10 14:14:11 h05cni kernel: [79258.113860] lpfc 0000:04:00.3: 1:(0):0203 Devloss timeout on WWPN 50:00:09:75:00:0a:bd:a1 NPort x5c0080 Data: x0 x8 x3 > Mar 10 14:14:11 h05cni kernel: [79258.113900] lpfc 0000:04:00.3: 1:(0):0203 Devloss timeout on WWPN 50:00:09:75:00:0a:bd:18 NPort x5c0060 Data: x0 x8 x2 > Mar 10 14:16:50 h05cni kernel: [79417.676167] lpfc 0000:04:00.2: 0:1305 Link Down Event x3 received Data: x3 x20 x800110 x0 x0 > Mar 10 14:17:11 h05cni kernel: [79438.138987] lpfc 0000:04:00.2: 0:1303 Link Up Event x8 received Data: x8 x0 x40 x0 x0 x0 0 > Mar 10 14:17:11 h05cni kernel: [79438.139749] lpfc 0000:04:00.2: 0:2546 New FCF event, evt_tag:x9, index:x0 > Mar 10 14:17:21 h05cni kernel: [79447.751373] lpfc 0000:04:00.2: 0:(0):0203 Devloss timeout on WWPN 50:00:09:75:00:0a:bd:90 NPort xc00060 Data: x0 x8 x2 > Mar 10 14:17:21 h05cni kernel: [79447.751413] lpfc 0000:04:00.2: 0:(0):0203 Devloss timeout on WWPN 50:00:09:75:00:0a:bd:29 NPort xc00080 Data: x0 x8 x3 > That looks like an issue with the driver. If the devices disappear after a LIP the driver isn't able to correctly attach the devices again. Please open a bugzilla to track this properly. Cheers, Hannes From allen at ua.edu Tue Mar 10 12:35:12 2015 From: allen at ua.edu (Beddingfield, Allen) Date: Tue, 10 Mar 2015 18:35:12 +0000 Subject: [sles-beta] SP4 Beta2 preliminary test results Message-ID: <0ED539A8-4C6F-4FE2-BE47-A066314306BD@ua.edu> So, I?ve done a few fresh installations of SLES 11 SP4 Beta2 (x86_64): For the most part, all looks good, but I?m just getting started testing. The addition of ?open-vmtools? is a welcomed addition in our datacenter! No errors/problems on install, aside from sshd not being set to start up, as was described in the release notes. I was able to configure a system against our LDAP with no issues. I was able to Install the Tripwire Enterprise agent with no issues. I was able to get the Zabbix monitoring agent to work with no issues. I as able to add the system to SUSE Manager 2.1.x. The 11/4 repos don?t exist, so it complained about that and obviously couldn?t add the ?spacewalk-client-setup? repo. Otherwise, it added and worked. There were a couple of issues: First issue: On boot, after firewall initialization, the following error is seen repeatedly: ?WARNING: The state match is obsolete. Use contract instead.? Second issue: This one has actually existed in every release since SP1 (was not an issue in 11.0 and 11 SP1, but is also an issue in SP2 and SP3). Details/steps to reproduce. VMware VM has a disk layout as follows: /dev/sda1 /boot (ext3, 1GB) /dev/sda2 swap (4GB) /dev/sda3 / (XFS, 55GB) In VMware, expand the size of the virtual disk from 60GB to 80GB. Boot VM from SLES 11 SP4 Beta 2 disk Select ?Repair Installed System? Select ?Expert Tools? Select ?Start Partitioning Tool? Select the ?+? to the left of ?Hard Disks? to expand the list Select the ?+? to the left of ?sda? to list the partitions Select ?sda3? Select ?Resize? This produces the following error: ?Partition /dev/sda3 cannot be resized because the filesystem seems to be inconsistent.? This will work to resize if booting from a SLES11 SP1 disk, but not 2, 3, or now 4 Beta2. Is this something that could be corrected in this release? It can be reproduced consistently 100% of the time. Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama From mge at suse.com Tue Mar 10 19:59:40 2015 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 11 Mar 2015 02:59:40 +0100 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <3696080.UuFptH8s86@mlatimer1.dnsdhcp.provo.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> <40637DBB36AF3941B243A286A432CA0B1AEC3889@HXMB12.pnet.ch> <3696080.UuFptH8s86@mlatimer1.dnsdhcp.provo.novell.com> Message-ID: <20150311015940.GA29326@suse.com> Hello Urs, Mike and all, On 2015-03-10 T 10:17 -0600 Mike Latimer wrote: > > > > The following NEW packages are going to be installed: > > crash-eppic libevent-1_4-2 libgmodule-2_0-0 libiptc0 liblzmadec0 > > libnfnetlink0 libvmtools0 libxtables9 lzma nfs-client nfsidmap > > open-vm-tools release-notes-sles rpcbind > That was not expected (at least from my side), and is > certainly not desirable. Can of you open a service > request so we can get a bug to track this? Well. In my view, this behaviour is consistent and correct, and here is why: 1. An Upgrade from SLES 11 SP3 to SLES 11 SP4 should deliver an identical result as a fresh installation of SLES 11 SP4. 2. Automatically installing the open-vm-tools is recommended in a fresh installation, as only this way we get the best user experience. 3. If we include the open-vm-tools and install it, if a VMware environment is found during an initial installation, this should also be done during an update. > > I do now have two sorts of VMWare Tools installed, > > which is really not wanted I understand the problem. > > In my mind service pack does mean solely security > > fixes, HW enablement and minor updates, but no > > architecture, no methods change please. In my perspective, the open-vm-tools are (virtual) hardware enablement, and thus definitely in scope for a Service Pack, now that we have it available and supported as an open source package. > > No automated installation of new things where one has > > to reverse-engineer to know where it comes from and > > find an own way to work around. See below for a suggestion. > > So please think the subject with these open-vm-tools > > over. And if you come to a result, that open-vm-tools > > is a must, then declare SLES11-SP4 as a new release > > with major changes please. Not only a service-pack > > update > > The inclusion of open-vm-tools was intended as a > convenience change - not a challenge to overcome. ;) > I'll finish my testing and we will either drop the > package, or fix the dependency so it is not > automatically installed (which was the original intent). I am afraid that solution contradicts the consistency requirement described in the beginning of this E-Mail. My proposed solution is to document the new availability of the open-vm-tools in the release notes and add also add an autoyast snippet there, how to prevent the installation, if the old vmware tools are installed. So long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile/DE: +49 179 2949448 Mobile/US: +1 917 607 4687 SUSE LINUX GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: F.Imend?rffer,J.Smithard,J.Guild,D.Upmanyu,G.Norton, HRB 21284(AG N?rnberg) From mlatimer at suse.com Tue Mar 10 21:39:02 2015 From: mlatimer at suse.com (Mike Latimer) Date: Tue, 10 Mar 2015 21:39:02 -0600 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <20150311015940.GA29326@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <3696080.UuFptH8s86@mlatimer1.dnsdhcp.provo.novell.com> <20150311015940.GA29326@suse.com> Message-ID: <2047898.3JZMYrCJ3y@mlatimer1.dnsdhcp.provo.novell.com> Hi Matthias, On Wednesday, March 11, 2015 02:59:40 AM Matthias G. Eckermann wrote: > Well. In my view, this behaviour is consistent and > correct, and here is why: > > 1. An Upgrade from SLES 11 SP3 to SLES 11 SP4 should > deliver an identical result as a fresh installation > of SLES 11 SP4. > > 2. Automatically installing the open-vm-tools is > recommended in a fresh installation, as only this > way we get the best user experience. > > 3. If we include the open-vm-tools and install it, > if a VMware environment is found during an initial > installation, this should also be done during an update. While the above comments make sense, we were specifically concerned about residual files which might conflict with open-vm-tools components. Based on these concerns, the original intent for SLES11SP4 was to make installing open- vm-tools a choice - rather than an automatic installation. (See FATE#318106, comment #10). (We also specifically decided that removing VMware tools prior to the open-vm-tools package was not a safe option.) The automatic installation of open-vm-tools is due to a 'Supplements' statement in the open-vm-tools package which matches a VMware pci device ID. I made this change for SLES12, and removing it for SLES11SP4 should "fix" it (if we decide to go that route). > I am afraid that solution contradicts the consistency > requirement described in the beginning of this E-Mail. > > My proposed solution is to document the new availability > of the open-vm-tools in the release notes and add also add > an autoyast snippet there, how to prevent the > installation, if the old vmware tools are installed. This may be a possibility, but it would only impact autoyast installations. Is this worth the effort - at the risk of breaking non-autoyast based upgrades? Thanks for the comments, Mike From sreeves at suse.com Tue Mar 10 23:40:55 2015 From: sreeves at suse.com (Scott Reeves) Date: Tue, 10 Mar 2015 23:40:55 -0600 Subject: [sles-beta] After autoyast installation, sshd is not active In-Reply-To: References: Message-ID: <54FF8107020000760000E7B4@prv-mh.provo.novell.com> >>> On 3/10/2015 at 02:19 AM, "Bienwald, Martin" wrote: > Hi all, > > I ran an autoyast installation of SLES11 SP4, using the same XML file and > settings we've been using for SP3. > After booting the installed system, sshd is not running, and "chkconfig -l > sshd" shows "off" in all runlevels. > This is different from SP3, where the default seems to be to activate and > start sshd. Just to update you on this change of behavior. This was listed on the known issues for Beta2 and has been fixed for Beta3. - SSH not enabled even if SSH used for installation [bnc#920398] From Dick.Waite at softwareag.com Wed Mar 11 00:50:32 2015 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 11 Mar 2015 06:50:32 +0000 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DBD184AB3@hqmbx6.eur.ad.sag> Grand Morning Mike, The issues I noted quickly was the Mouse running a little wild, not being able to click on what you wanted. When I used VMware "Shutdown" it said it had an issue with the script below it. I'm using VMware Workstation 11.1.0 which has tools VMware Tools 9-9-2-2496486 I have now deleted open-vm-tools and libvm and marked them "not to be installed". I did this on a couple of SP3-SP4 updates I ran at my home_office and it's looking good. At least I can work on testing SAG Apps and not chasing my mouse around the screen. More than will to run some checks for you on a best available time base. __R -----Original Message----- From: Mike Latimer [mailto:mlatimer at suse.com] Sent: Dienstag, 10. M?rz 2015 15:20 To: sles-beta at lists.suse.com Cc: Waite, Dick Subject: Re: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... Hi, On Tuesday, March 10, 2015 11:36:23 AM Waite, Dick wrote: > What has been APITA is the grand Ping_Pong being played between VMware > and SUSE with ?Tools?. With SP3 one used VMware tools for Workstation > and one was happy. You run an update and the good people of SUSE say, > we can do better and pop into the mix their ?open-vm-tools and > libvmtools?, You have not asked for this, it?s just done, not check to > see if this is a ?VMware Workstation?. Thanks for reporting this, and sorry for the troubles. Last time I tested VMware-workstation, installing VMware tools was done through a tarball, rather than an RPM, so I was not expecting the update process to find anything to update. > So you finish the update and all looks Okay, so you then run a VMware > tools update ?cos you know you have a new kernel. I?m running VMware > Workstation > 11.1.0 which has tools 9.9.2_2496486 and it?s not given me any issues, > so far. Re-load after the tools update and Wow? what?s has my mouse > been smoking !!!!! It?s all over the shop, umm better close down, Wow > why is the stop script saying it?s not a happy badger?. > One does look around and after the fun and games with SLE12 it?s quite > easy to see the ?open-vm-tools? are back again giving my mouse > something that sends it in circles? I thought we had everything worked out in the SLE12 environment - other than the gtkmm-2.4/3.0 issue. If there are any outstanding issues, I'd like to understand them and get a bug filed. > If you kill the open-vm-tools and set it to never again darken your > door, run the VMware tools again and reload then you have a mouse the > is back under control and scripts that start and stop when asked. > I do not understand what the open-vm-tools are there for. If you are > running VMware software then you have their tools, which get updated quite often. > If your not running VMware why would you want open-vm-tools ? In theory, including the tools with the distribution should have helped users avoid the step of installing additional software after the installation has completed. If conflicts are continuing to be seen, we need to get them resolved or rethink this approach. I'll do some testing today, but any further details you can provide (probably off-list) would be appreciated. Thanks! Mike Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Dick.Waite at softwareag.com Wed Mar 11 01:22:46 2015 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 11 Mar 2015 07:22:46 +0000 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DBD184AB3@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> <46AC8C81C10B8C48820201DF2AE1D76DBD184AB3@hqmbx6.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DBD185AF9@hqmbx6.eur.ad.sag> Mike the part I don?t see working in this two horse race is: VWware Workstation bring out a 11.2.0 which has Tools at say 9-9-3-123456. They control both halves of the interface so they can test this works. I update to 11.2.0 and try and run with "open-vm-tools", now I know SUSE and VMware are good friends but will then let you know in advance whet has changed in their update ? The other part is, on some systems I run Workstation 10.n for our own reasons, this runs grand with VMware tools built with 10.n but which version of "open-vm-tools" would I use ? or do you hope the latest "open-vm-tools" will fit all the versions of Workstation that VMware support ? I don?t see with what application you (SUSE) would expect "open-vm-tools" to run with, maybe knowing that would remove some of the Shades of Grey. __R -----Original Message----- From: Waite, Dick Sent: Mittwoch, 11. M?rz 2015 07:51 To: 'Mike Latimer'; sles-beta at lists.suse.com Subject: RE: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... Grand Morning Mike, The issues I noted quickly was the Mouse running a little wild, not being able to click on what you wanted. When I used VMware "Shutdown" it said it had an issue with the script below it. I'm using VMware Workstation 11.1.0 which has tools VMware Tools 9-9-2-2496486 I have now deleted open-vm-tools and libvm and marked them "not to be installed". I did this on a couple of SP3-SP4 updates I ran at my home_office and it's looking good. At least I can work on testing SAG Apps and not chasing my mouse around the screen. More than will to run some checks for you on a best available time base. __R -----Original Message----- From: Mike Latimer [mailto:mlatimer at suse.com] Sent: Dienstag, 10. M?rz 2015 15:20 To: sles-beta at lists.suse.com Cc: Waite, Dick Subject: Re: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... Hi, On Tuesday, March 10, 2015 11:36:23 AM Waite, Dick wrote: > What has been APITA is the grand Ping_Pong being played between VMware > and SUSE with ?Tools?. With SP3 one used VMware tools for Workstation > and one was happy. You run an update and the good people of SUSE say, > we can do better and pop into the mix their ?open-vm-tools and > libvmtools?, You have not asked for this, it?s just done, not check to > see if this is a ?VMware Workstation?. Thanks for reporting this, and sorry for the troubles. Last time I tested VMware-workstation, installing VMware tools was done through a tarball, rather than an RPM, so I was not expecting the update process to find anything to update. > So you finish the update and all looks Okay, so you then run a VMware > tools update ?cos you know you have a new kernel. I?m running VMware > Workstation > 11.1.0 which has tools 9.9.2_2496486 and it?s not given me any issues, > so far. Re-load after the tools update and Wow? what?s has my mouse > been smoking !!!!! It?s all over the shop, umm better close down, Wow > why is the stop script saying it?s not a happy badger?. > One does look around and after the fun and games with SLE12 it?s quite > easy to see the ?open-vm-tools? are back again giving my mouse > something that sends it in circles? I thought we had everything worked out in the SLE12 environment - other than the gtkmm-2.4/3.0 issue. If there are any outstanding issues, I'd like to understand them and get a bug filed. > If you kill the open-vm-tools and set it to never again darken your > door, run the VMware tools again and reload then you have a mouse the > is back under control and scripts that start and stop when asked. > I do not understand what the open-vm-tools are there for. If you are > running VMware software then you have their tools, which get updated quite often. > If your not running VMware why would you want open-vm-tools ? In theory, including the tools with the distribution should have helped users avoid the step of installing additional software after the installation has completed. If conflicts are continuing to be seen, we need to get them resolved or rethink this approach. I'll do some testing today, but any further details you can provide (probably off-list) would be appreciated. Thanks! Mike Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From allen at ua.edu Wed Mar 11 08:17:43 2015 From: allen at ua.edu (Beddingfield, Allen) Date: Wed, 11 Mar 2015 14:17:43 +0000 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DBD185AF9@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> <46AC8C81C10B8C48820201DF2AE1D76DBD184AB3@hqmbx6.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76DBD185AF9@hqmbx6.eur.ad.sag> Message-ID: I would assume that SUSE is primarily targeting SLES for use under VMware vSphere, and that the workstation version is not the primary focus. Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama On 3/11/15, 2:22 AM, "Waite, Dick" wrote: >Mike the part I don?t see working in this two horse race is: > >VWware Workstation bring out a 11.2.0 which has Tools at say 9-9-3-123456. They control both halves of the interface so they can test this works. > >I update to 11.2.0 and try and run with "open-vm-tools", now I know SUSE and VMware are good friends but will then let you know in advance whet has changed in their update ? > >The other part is, on some systems I run Workstation 10.n for our own reasons, this runs grand with VMware tools built with 10.n but which version of "open-vm-tools" would I use ? or do you hope the latest "open-vm-tools" will fit all the versions of Workstation that VMware support ? > >I don?t see with what application you (SUSE) would expect "open-vm-tools" to run with, maybe knowing that would remove some of the Shades of Grey. > >__R > From mkrapp at suse.com Wed Mar 11 10:29:25 2015 From: mkrapp at suse.com (Michael Krapp) Date: Wed, 11 Mar 2015 17:29:25 +0100 Subject: [sles-beta] SLES11-SP4 multipath problems, SAN path does not get reinstated after path failure In-Reply-To: <54FF2FC5.20406@suse.com> References: <40637DBB36AF3941B243A286A432CA0B1AEC38BF@HXMB12.pnet.ch> <54FF2FC5.20406@suse.com> Message-ID: <20150311162925.GA14220@wawa.suse.de> * Hannes Reinecke schrieb 20150310 18:55: > On 03/10/2015 11:34 AM, urs.frey at post.ch wrote: > > I have installed SLES11-SP4 x86_64 on a HP Proliant BL460cgen8 attached to SAN EMC, FCoE. > > > > When failing a SAN path, I can observe, that the SAN path does not get reinstated after SAN link up again. > > Multipath tools do loose all LUNs [...] > That looks like an issue with the driver. If the devices disappear after > a LIP the driver isn't able to correctly attach the devices again. > Please open a bugzilla to track this properly. https://bugzilla.suse.com/show_bug.cgi?id=921814 > Cheers, > > Hannes > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Kind regards / Cordialement / Mit freundlichen Gr??en Michael Krapp, Technical Support Engineer Worldwide Support Services Linux SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) Maxfeldstr. 5, D-90409 N?rnberg From Dick.Waite at softwareag.com Wed Mar 11 12:01:06 2015 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 11 Mar 2015 18:01:06 +0000 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <2030214.V3PZLOttCg@mlatimer1.dnsdhcp.provo.novell.com> <46AC8C81C10B8C48820201DF2AE1D76DBD184AB3@hqmbx6.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76DBD185AF9@hqmbx6.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76DBD188F29@hqmbx6.eur.ad.sag> Sounds good Allen. Would be grand if they added a quick test to see who they were possibly working with. __R -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Beddingfield, Allen Sent: Mittwoch, 11. M?rz 2015 15:18 To: 'sles-beta at lists.suse.com' Subject: Re: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... I would assume that SUSE is primarily targeting SLES for use under VMware vSphere, and that the workstation version is not the primary focus. Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama On 3/11/15, 2:22 AM, "Waite, Dick" wrote: >Mike the part I don?t see working in this two horse race is: > >VWware Workstation bring out a 11.2.0 which has Tools at say 9-9-3-123456. They control both halves of the interface so they can test this works. > >I update to 11.2.0 and try and run with "open-vm-tools", now I know SUSE and VMware are good friends but will then let you know in advance whet has changed in their update ? > >The other part is, on some systems I run Workstation 10.n for our own reasons, this runs grand with VMware tools built with 10.n but which version of "open-vm-tools" would I use ? or do you hope the latest "open-vm-tools" will fit all the versions of Workstation that VMware support ? > >I don?t see with what application you (SUSE) would expect "open-vm-tools" to run with, maybe knowing that would remove some of the Shades of Grey. > >__R > _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From mlatimer at suse.com Wed Mar 11 18:27:55 2015 From: mlatimer at suse.com (Mike Latimer) Date: Wed, 11 Mar 2015 18:27:55 -0600 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76DBD185AF9@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76DBD184AB3@hqmbx6.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76DBD185AF9@hqmbx6.eur.ad.sag> Message-ID: <3252415.78Xex8icXG@mlatimer1.dnsdhcp.provo.novell.com> On Wednesday, March 11, 2015 07:22:46 AM Waite, Dick wrote: > Mike the part I don?t see working in this two horse race is: > > VWware Workstation bring out a 11.2.0 which has Tools at say 9-9-3-123456. > They control both halves of the interface so they can test this works. As Allen mentioned, I think the ESX environment is a more important target. However, I think it is possible to have tools that work in both environments. The versioning difference between VMware Tools and open-vm-tools is challenging, but I think VMware is working toward bridging any gaps that might exist. > I update to 11.2.0 and try and run with "open-vm-tools", now I know SUSE and > VMware are good friends but will then let you know in advance whet has > changed in their update ? In this case, the confusion is at least largely due to the conflicting tools versions. As I mentioned before, the open-vm-tools package was not intended to be automatically installed, and I'm taking steps to change that in Beta3. > The other part is, on some systems I run Workstation 10.n for our own > reasons, this runs grand with VMware tools built with 10.n but which > version of "open-vm-tools" would I use ? or do you hope the latest > "open-vm-tools" will fit all the versions of Workstation that VMware > support ? > I don?t see with what application you (SUSE) would expect "open-vm-tools" to > run with, maybe knowing that would remove some of the Shades of Grey. I'm not completely sure I can answer that. There are environments where open- vm-tools may not be complete enough to fully replace VMware Tools. However, we do believe they should work and offer enough functionality that the availability of open-vm-tools in the distribution itself is a nice improvement. It may come down to you evaluating your environment and determining which solution is better suited than the other. If you have any specific comments or suggestions, I'd be happy to discuss this further offline. (Any testing, bug reporting, etc, are always appreciated.) Thanks again for the comments. -Mike From mge at suse.com Wed Mar 11 11:09:18 2015 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 11 Mar 2015 18:09:18 +0100 Subject: [sles-beta] SLES11-SP4 beta2 x86_64 - VMware Tools Again ... In-Reply-To: <2047898.3JZMYrCJ3y@mlatimer1.dnsdhcp.provo.novell.com> References: <46AC8C81C10B8C48820201DF2AE1D76DBD184557@hqmbx6.eur.ad.sag> <3696080.UuFptH8s86@mlatimer1.dnsdhcp.provo.novell.com> <20150311015940.GA29326@suse.com> <2047898.3JZMYrCJ3y@mlatimer1.dnsdhcp.provo.novell.com> Message-ID: <20150311170918.GD24754@suse.com> Hello Urs, Mike and all, On 2015-03-10 T 21:39 -0600 Mike Latimer wrote: > The automatic installation of open-vm-tools is due to > a 'Supplements' statement in the open-vm-tools package > which matches a VMware pci device ID. I made this > change for SLES12, and removing it for SLES11SP4 > should "fix" it (if we decide to go that route). we discussed the pros and cons, and I got convinced that this is the least disruptive approach, as it does not break existing installations, and the inconvenience of manually adding the open-vm-tools is acceptable. Thanks for raising this. So long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile/DE: +49 179 2949448 Mobile/US: +1 917 607 4687 SUSE LINUX GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: F.Imend?rffer,J.Smithard,J.Guild,D.Upmanyu,G.Norton, HRB 21284(AG N?rnberg)