|
Bugzilla – Full Text Bug Listing |
| Summary: | update to tumbleweed snapshot 12.06.2015 from a freshly installed 13.2 fails reliably. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Stakanov Schufter <stakanov> |
| Component: | Upgrade Problems | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | ancor, chcao, jreidinger, stakanov |
| Version: | 13.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
last yast2log
following all yast 2 logs of the installed system (fresh) thirs log (crnologically they are older as numbers are growing. System installed in a day) yast to log number 4 yast2 startlog this is history from /var/log/zypp in temp I also found this file last I have, from /var/log/yast2 |
||
Created attachment 639433 [details]
following all yast 2 logs of the installed system (fresh)
Created attachment 639434 [details]
thirs log (crnologically they are older as numbers are growing. System installed in a day)
Created attachment 639435 [details]
yast to log number 4
Created attachment 639436 [details]
yast2 startlog
Looks like abort cause that logs are not copied to running system. Can you please provide installation logs? Howto is written in wiki - https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22_.28for_package_installation_also_.22libzypp_logging.22.29._What_does_that_mean.2C_and_how_do_I_do_that.3F Thanks Created attachment 639575 [details]
this is history from /var/log/zypp
Created attachment 639576 [details]
in temp I also found this file
Created attachment 639577 [details]
last I have, from /var/log/yast2
this is all I have. If you need yast in debug mode I will try to save on usb
As Josef already wrote we need the logs from the failed installation. To put this to logical terms: if Joseph said what he said, and I did not understand and you still do not have what you need, either you set this as "invalid" and I have a good day or you tell me what exactly you need me to do. Since if I WOULD have understood what Joseph said, you WOULD now have what you need. Straightforward, no? So, I do repeat the question: I will run the installation again. The error will appear. From this moment, since I do not have access to the CLI in the installer, how can I perform the command for yast2log in that case in order to have the log written. Currently I do not understand what I have to do, but I am still here to give you whatever I can. So please do an effort and write two lines instead of one? Just for the less "gifted" of us? Thank you. The document explains how to switch to a console, start a xterm, how to redirect to logs to a different computer or to an usb stick. That already makes four possibilities to get the logs. Without knowing you setup and why you cannot access the cli I cannot help in more details. if you see wiki page I send you can use you can see that there is possible to use shift+F8 another option is to use mentioned logging to remote location or usb disk. Another option is to add to installer parameter "startshell=1" that return you after errror to terminal and allows you to copy logs to any locations ( packing it with save_y2logs command ) thank you, both of you. With that info and the wiki I will try to do a run tonight and will post the result. Stakanov. Looks like you didn't get the logs and the 12.06.2015 snapshots is long ago superseded by several newer ones. Should I close this bug report or are you still planning to work on it? Closing as stated in previous comment. Feel free to reopen if you disagree. |
Created attachment 639432 [details] last yast2log Trying to update a 13.2 fresh install to tumbleweed. The first error I was able to capture was: undefined method split for it_IT:Array caller /usr/lib64/addr ruby/2.20/yast/builtimg.rb:455:in "splitsting" Then there comes a second error and it all aborts anyway. The installer calls for bugreport and requests yast2logs. Well, I attach you all I have. Interrupting the installation gives a normal 13.2 system.