[Bug 873962] New: AutoYast blocks waiting for input.
https://bugzilla.novell.com/show_bug.cgi?id=873962 https://bugzilla.novell.com/show_bug.cgi?id=873962#c0 Summary: AutoYast blocks waiting for input. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: autoyast-maintainers@suse.de ReportedBy: osynge@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=586651) --> (http://bugzilla.novell.com/attachment.cgi?id=586651) tgz containing autoyast file yast logs and pictures. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 Blocking popups should never happen when doing a fully automated install. Reproducible: Always Steps to Reproduce: 1.pxeboot with settings attached. 2.wait. Actual Results: it will popup a dialog that will hang booting. Expected Results: System will fully install automatically. I realize that this is probably down to me trying and failing to install additional repositories and then install packages from them. That does not stop it from being a bug due to the need for better error handling. This bug effects SLE 11ps3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=873962 https://bugzilla.novell.com/show_bug.cgi?id=873962#c1 Thomas Göttlicher <tgoettlicher@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |tgoettlicher@suse.com InfoProvider| |osynge@suse.com --- Comment #1 from Thomas Göttlicher <tgoettlicher@suse.com> 2014-04-24 09:51:27 UTC --- The error popup is caused by an unknown repository signature. Please retry with following signature-handling section in the autoyast xml file: <signature-handling> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_non_trusted_gpg_key config:type="boolean">true</accept_non_trusted_gpg_key> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <import_gpg_key config:type="boolean">true</import_gpg_key> </signature-handling> Does this work? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=873962 https://bugzilla.novell.com/show_bug.cgi?id=873962#c2 Thomas Göttlicher <tgoettlicher@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|autoyast-maintainers@suse.d |yast2-maintainers@suse.de |e | --- Comment #2 from Thomas Göttlicher <tgoettlicher@suse.com> 2014-04-24 12:01:51 UTC --- Comment #1 explains how not to run in an error popup in this specific case. This bug report is about preventing blocking popup windows in non-interactive workflows. The installation hangs in the error popup created by Report.ycp. YaST maintainers, could you please decide if you can fix this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=873962 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |schubi@suse.com Resolution|--- |NORESPONSE --- Comment #5 from Stefan Schubert <schubi@suse.com> --- There is also a report section in the general section to handle this in general: <report> <messages> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </messages> <errors> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </errors> <warnings> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </warnings> </report> This bug is quite old and we have not gotten an answer about the question of Thomas. So I assume that is has been solved meanwhile. Feel free to reopen the bug if you have still problems in that area. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com