|
Bugzilla – Full Text Bug Listing |
| Summary: | firewall_auto breaks progress bar in autoinstall mode | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Thomas Fehr <fehr> |
| Component: | YaST2 | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | jreidinger, locilka, mfilka |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2log file of autoyast installation
autoyast profile |
||
Created attachment 563366 [details]
y2log file of autoyast installation
Created attachment 563368 [details]
autoyast profile
I've just learned that the backtrace is not ruby exception but feature of y2warning( -1, ...) call which is issued in Progress#on Anyway, according this line clients/firewall_auto.rb:118 Firewall auto finished firewall is done, so problem is probably somewhere out there. Please discuss with maintainer of Progress.rb if what firewall code does or Progress bar code is wrong. What would you suggest autoyast could to against that? Autoyast not calling firewall_auto.rb any more would certainly help but is unfortunately not an option. BTW: When I comment Progress::on and Progress::off out from firewall module the problem does not appear. fix is in review https://github.com/yast/yast-firewall/pull/15 reviewed @Josef: thanks for taking over. thanks, lets close it |
When an autoyast xml profile contains a section <firewall> </firewall> inst_autoconfigure calls firewall_auto with "Write". there is following code in firewall_auto.rb elsif @func == "Write" Yast.import "Progress" Progress.off @ret = SuSEFirewall.Write Progress.on else There is an ruby exception in y2log file: 013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/share/YaST2/modules/Progress.rb:308:in `on' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/share/YaST2/clients/firewall_auto.rb:111:in `main' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/share/YaST2/clients/firewall_auto.rb:128:in `<top (required)>' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/lib/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/lib/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/lib/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/lib/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/lib/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/share/YaST2/modules/Call.rb:45:in `Function' 2013-10-14 15:40:39 <2> f74(4235) [Ruby] modules/Progress.rb:308 /usr/share/YaST2/clients/inst_autoconfigure.rb:192:in `block in main' Unfortunately this results in a indefinite hang of the next call to UI.ChangeWidget(Id(:progress), :Value, @current_step) in inst_autoconfigure.rb I am not sure but it might be the case that the hang only occurs with qt UI. I will attach complete y2log file. Will attach y2log file and autoyast profile Lukas assigning to you since yast-firewall does not have a maintainer. Please reassign accordingly.