Bug 1218084

Summary: Setup rmt server by yast2 rmt popup error: Caller: /usr/lib64/ruby/2.5.0/net/protocol.rb:181:in 'rbuf_fill' ReadTimeout
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: Chenzi Cao <chcao>
Component: YaST2Assignee: SCC Bugs <scc-bugs>
Status: NEW --- QA Contact:
Severity: Normal    
Priority: P3 - Medium CC: chcao, richard.fan, rtsvetkov, scc-bugs, tschmidt
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://openqa.suse.de/tests/13070868/modules/rmt_chinese/steps/87
See Also: https://bugzilla.suse.com/show_bug.cgi?id=1224809
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log_for_rmt_case

Description Chenzi Cao 2023-12-15 03:55:48 UTC 
Created attachment 871375 [details]
y2log_for_rmt_case

Steps:
- Boot SLES15SP6 build44.1 image
- Change language to Chinese via yast2 language
- Install packages rmt-server by zypper
- Setup rmt server by "yast2 rmt"

Observed:

After input the Organization Credentials Username and Password, click 'next', it starts to check whether the Organization Credentials is valid, then an error popup:

========================================
Error:

Internal error, Please report a bug report with logs.
Run save_y2log to get the complete logs.

Caller: /usr/lib64/ruby/2.5.0/net/protocol.rb:181:in 'rbuf_fill'

Details: Net::ReadTimeout
=========================================

Cut from y2log:
2023-12-14 22:11:01 <2> susetest(7480) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):89 Not enough widgets with valid shortcut characters - no check
2023-12-14 22:13:01 <3> susetest(7480) [Ruby] yast/wfm.rb(handle_exception):271 Client /usr/share/YaST2/clients/rmt.rb failed with 'Net::ReadTimeout' (Net::ReadTimeout).
Backtrace:
/usr/lib64/ruby/2.5.0/net/protocol.rb:181:in `rbuf_fill'
/usr/lib64/ruby/2.5.0/net/protocol.rb:157:in `readuntil'
/usr/lib64/ruby/2.5.0/net/protocol.rb:167:in `readline'
/usr/lib64/ruby/2.5.0/net/http/response.rb:40:in `read_status_line'
/usr/lib64/ruby/2.5.0/net/http/response.rb:29:in `read_new'
/usr/lib64/ruby/2.5.0/net/http.rb:1497:in `block in transport_request'
/usr/lib64/ruby/2.5.0/net/http.rb:1494:in `catch'
/usr/lib64/ruby/2.5.0/net/http.rb:1494:in `transport_request'
/usr/lib64/ruby/2.5.0/net/http.rb:1467:in `request'
/usr/share/YaST2/lib/rmt/wizard_scc_page.rb:133:in `block in scc_credentials_valid?'
/usr/lib64/ruby/2.5.0/net/http.rb:910:in `start'
/usr/lib64/ruby/2.5.0/net/http.rb:609:in `start'
/usr/share/YaST2/lib/rmt/wizard_scc_page.rb:133:in `scc_credentials_valid?'
/usr/share/YaST2/lib/rmt/wizard_scc_page.rb:99:in `next_handler'
/usr/share/YaST2/lib/ui/event_dispatcher.rb:47:in `public_send'
/usr/share/YaST2/lib/ui/event_dispatcher.rb:47:in `block in event_loop'
/usr/share/YaST2/lib/ui/event_dispatcher.rb:43:in `loop'
/usr/share/YaST2/lib/ui/event_dispatcher.rb:43:in `event_loop'
/usr/share/YaST2/lib/rmt/wizard_scc_page.rb:113:in `run'
/usr/share/YaST2/lib/rmt/wizard.rb:50:in `block in run'
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/builtins.rb:546:in `eval'
/usr/share/YaST2/modules/Sequencer.rb:247:in `WS_run'
/usr/share/YaST2/modules/Sequencer.rb:318:in `block in Run'
/usr/share/YaST2/modules/Sequencer.rb:310:in `loop'
/usr/share/YaST2/modules/Sequencer.rb:310:in `Run'
/usr/share/YaST2/lib/rmt/wizard.rb:72:in `run'
/usr/share/YaST2/clients/rmt.rb:21:in `<top (required)>'
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:345:in `eval'
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:345:in `run_client'
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin'
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin_wrapper'
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:195:in `CallFunction'
/usr/lib/YaST2/bin/y2start:68:in `<main>'
2023-12-14 22:13:01 <3> susetest(7480) [Ruby] yast/wfm.rb(handle_exception):308 Internal error. Please report a bug report with logs.<br>Run save_y2logs to get complete logs.<br><br>Caller:  /usr/lib64/ruby/2.5.0/net/protocol.rb:181:in `rbuf_fill&#39;<br><br>Details: Net::ReadTimeout

Please find the attached y2log for this case and the openqa test case as below:

openQA test in scenario sle-15-SP6-Migration-from-SLE15-SPx-Milestone-x86_64-rmt_chinese@64bit fails in
[rmt_chinese](https://openqa.suse.de/tests/13070868/modules/rmt_chinese/steps/87)
Comment 1 Chenzi Cao 2023-12-15 06:10:31 UTC 
Related package version:

yast2-rmt-1.3.4-150200.3.8.1.x86_64
rmt-server-2.14-150500.3.6.1.x86_64
Comment 2 Thomas Schmidt 2023-12-15 08:47:57 UTC 
Is this reproducible? Net::ReadTimeout sounds like a local network issue. We did not have any SCC downtime recently.
Comment 3 Chenzi Cao 2023-12-15 08:56:11 UTC 
(In reply to Thomas Schmidt from comment #2)
> Is this reproducible? Net::ReadTimeout sounds like a local network issue. We
> did not have any SCC downtime recently.

It is not always reproducible, it happened several times when I re-run some openqa test cases yesterday and this morning, but not always, sometimes it didn't happen.
Comment 4 Lukas Ocilka 2023-12-15 11:42:05 UTC 
(In reply to Thomas Schmidt from comment #2)
> Is this reproducible? Net::ReadTimeout sounds like a local network issue. We
> did not have any SCC downtime recently.

Anyway, it's an exception and as such, it should be caught and reported to the user instead of throwing an error. This is done by https://www.rubyguides.com/2019/06/ruby-rescue-exceptions/

begin
rescue
end

I don't think that YaST RMT belongs to my team, Thomas?
Comment 5 Thomas Schmidt 2023-12-15 13:31:40 UTC 
That module is maintained by us, I'll re-assign.
Comment 6 Richard Fan 2024-02-04 01:34:25 UTC 
(In reply to Thomas Schmidt from comment #5)
> That module is maintained by us, I'll re-assign.

The issue can be seen more times in recent tests. and re-try seems can't fix the issue. 

Can you please help?
Comment 7 Richard Fan 2024-02-04 01:47:15 UTC 
[sle15sp4-openqa results]https://openqa.suse.de/tests/13415975#next_previous
[sle15sp5-openqa results]https://openqa.suse.de/tests/13415992#next_previous
Comment 8 Richard Fan 2024-02-04 01:47:27 UTC 
[sle15sp4-openqa results]https://openqa.suse.de/tests/13415975#next_previous
[sle15sp5-openqa results]https://openqa.suse.de/tests/13415992#next_previous
Comment 11 Thomas Schmidt 2024-02-19 07:41:18 UTC 
Hi Chenzi, we have automated cleanup tasks running that delete proxies from your test org after not seeing them for 3 months.
Comment 12 OBSbugzilla Bot 2024-03-27 17:35:03 UTC 
This is an autogenerated message for OBS integration:
This bug (1218084) was mentioned in
https://build.opensuse.org/request/show/1162941 Factory / yast2-rmt