Bug 1044254 - YaST2 UI Freeze after accepting License Agreement
YaST2 UI Freeze after accepting License Agreement
Status: RESOLVED NORESPONSE
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/Pvclh2O5
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-14 09:40 UTC by Ettore Di Giacinto
Modified: 2017-11-24 10:05 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
lslezak: needinfo? (edigiacinto)


Attachments
YaST2 logs and video (3.76 MB, application/x-xz)
2017-06-14 09:40 UTC, Ettore Di Giacinto
Details
Zypper install of a package (21.88 KB, image/png)
2017-06-16 08:34 UTC, Ettore Di Giacinto
Details
Test 1 - Do also a zypper install in different tty (5.93 MB, application/x-xz)
2017-06-20 13:44 UTC, Ettore Di Giacinto
Details
Test 2 (5.54 MB, application/x-xz)
2017-06-20 13:49 UTC, Ettore Di Giacinto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ettore Di Giacinto 2017-06-14 09:40:07 UTC
Created attachment 728888 [details]
YaST2 logs and video

During the install process, repositories gets added correctly, but when accepting the first license (non-oss) the YaST UI freezes, making impossible to continue or abort the installation.

I'm attaching the YaST2 logs and the openQA video.

Some background:

I'm writing a component for OpenQA that handles http network request from the guest machine and route them to another host. In this test, d.o.o repositories (non-oss and oss) are routed to the OpenQA mirrored assets for the build (serving then same repositories content for both). 
Progress issue: https://progress.opensuse.org/issues/17436
Comment 1 Michal Filka 2017-06-16 07:24:16 UTC
According the logs, installer is in loop of:

2017-06-14 04:04:01 <0> install(3895) [Pkg] Callbacks.YCP.cc(evaluate):234 Evaluating callback (registered funciton: ruby_reference)
2017-06-14 04:04:01 <0> install(3895) [Ruby] packages/dummy_callbacks.rb:331 Empty ProgressDownload callback, returning true

@Ettore
Could you pls check that your "proxy" is forwarding everything as expected.

@Lada
Any other notes?
Comment 2 Ettore Di Giacinto 2017-06-16 08:34:00 UTC
Created attachment 729209 [details]
Zypper install of a package

To test if the proxy component is working, i chrooted in the environment that needed to be upgraded and performed a zypper install, which worked. Even tho, i'm not sure UI should freeze, but instead should return an error - if can be helpful i can setup another test and give more logs to trace back the error.
Comment 3 Ettore Di Giacinto 2017-06-16 11:18:55 UTC
not sure if it's related to the problem, but from the logs i noticed this line:

2017-06-14 04:02:12 <3> install(3895) [Ruby] modules/ProductLicense.rb:119 Wrong license ID ''

Could be that two repos that are supplying the same repository content ( and license too) are conflicting someway? 
Anyway i'll attach more logs as soon as i prepare another testing environment.
Comment 4 Ettore Di Giacinto 2017-06-20 13:44:06 UTC
Created attachment 729524 [details]
Test 1 - Do also a zypper install in different tty
Comment 5 Ettore Di Giacinto 2017-06-20 13:49:27 UTC
Created attachment 729526 [details]
Test 2

Both tests contains the video of the UI freezes - the second one is "cleaner", without chrooting and testing if zypper installs are successful. Not sure, but it seems the culprit can be also that having a failure in returning directory.yast served in the repository may get the UI freeze.
Comment 6 Ladislav Slezák 2017-09-14 07:12:39 UTC
Sorry for late answer, are you still able to reproduce the issue with the latest Tumbleweed?

Can you reproduce it without the proxy component?

Can I somehow reproduce it locally (outside openQA)?
Comment 7 Ladislav Slezák 2017-11-24 10:05:35 UTC
I do not know if it still valid, if you can still reproduce it in the latest TW then reopen and provide the requested info. Thank you.