[sles-beta] SLES 12 SP1 BETA2 - Update from path ..

[Joe Doupnik]

On 26/08/2015 17:04, Joe Doupnik wrote:
> On 26/08/2015 16:54, Frederic Crozat wrote:
>> Le mercredi 26 août 2015 à 16:44 +0100, Joe Doupnik a écrit :
>>>       Upgrading from SLES11SP3, my part of the story.
>> Thanks for your report.
>>
>>>       As Thorsten said: insert DVD, select Upgrade, pray.
>>>        I followed that advice. SLES11SP3 was the starting point, with
>>> loads of Apache apps installed and whatnot, a faithful test machine. I
>>> inserted the SLES12SP1 beta 2 iso (doing this in ESXi). This time I
>>> elected to register and receive updates during installation, something
>>> which I normally avoid. "Some time later" the process finished with no
>>> complaints.
>>>       Testing. GUI works (if one can call Gnome working). Apache
>>> rebelled. The reason is it changed from v2.2 to 2.4 and Apache folks
>>> changed regular "Order allow,deny" to less useful terminology, just
>>> because they could I presume.   Similar Apache annoyances pop up as we
>>> smooth things. I added module access_compat, but there remains many
>>> other version specific changes to Apache config files, thus prepare for
>>> a bit of rewriting.
>>>       My iptables material works. The network functions (copper, static
>>> addressing).
>>>       The mouse no longer works in the GUI, and it does not appear in
>>> text mode YaST.
>> Hmm, strange. Could you open two separate SR for this ?
>> - for text mode in yast, I would assume gpm is not running (or it was
>> not properly enabled, if it was enabled before)
>> - for GUI, I don't know. Maybe an issue with open-vm-tools ?
>>
>>
> ------------
>     Yes, I can do that. Before taking that step, tomorrow I will 
> repeat the exercise, without the real time updates. This is done with 
> ESXi snapshot enabled so that I can retreat to the SLES11 starting point.
>     On the mouse. I note that in /etc/sysconfig the VMware tools (not 
> the open source variety) tweaked the mousetype setting from "imps2" to 
> imps2. It was thus changed in SLES11SP3. Returning the quotes and 
> restarting SLES12 made no improvement. Thus there is something else 
> causing the mouse difficulty, and competition between VMware and open 
> source tools is a possibility to be explored (i.e., turn off the 
> VMware tools version before starting the upgrade). The mouse runs 
> correctly in the SLES11 starting point.
>     More tomorrow when that test completes.
>     Thanks,
>     Joe D.
========
     Adding a postscript tonight.
     I returned to the SLES11SP3 starting point. I disabled VMware 
tools, shut down the machine, and then repeated the installation process 
in Upgrade mode. Install time updates were enabled again. Thus only 
VMware tools changed in this test.
     Same results. No mouse in the Gnome GUI.
     Again, this is a virtual machine in ESXi.
     A btw, as systemd obscures things which we need, I looked about and 
found the rcWhatever scripts, and started GroupWise 2014. It ran! I did 
not test GW further because Apache material needs much changing for 
Apache v2.4 and I am out of time.
     SR writing is for tomorrow. Tonight we know that VMware tools is 
not the guilty party for mouse problems.
     Thanks,
     Joe D.