[Bug 272829] New: Open Suse Updater - Corruption in application and error responses
https://bugzilla.novell.com/show_bug.cgi?id=272829 Summary: Open Suse Updater - Corruption in application and error responses Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: scocoo@tpg.com.au QAContact: jsrain@novell.com Open Suse Update Application was fully functional without errors The only change to the environment was activating the Automatic Online Update application in Yast at a later point in time. After a 24 hour period expired the applet changed to a triangle with exclamation mark - see attached. Initial error response whilst hovering over alert was Error The updater could not access the packet manager engine. This usually happens when you have another application (like Yast) using it at the same time. Please close other application. The Yast configured automatic update was de-activated. The applet was closed and then re-opened into system tray with same outcome. The applet was then closed and system rebooted. *Applet remained on alert. The applet was opened and add/remove update source was opened with initial error response run is not in path Followed by the usual display of installation source and optional advanced configuration details which were greyed out. The applet was accessed and the "configure applet" was opened. A change was made from default to Novell Zenworks and oked. Applet then changed to normal functionality. The applet was accessed and the "configure applet" was re-opened and set to "default" *An unfortunate event then took place, the previous update source was non responsive and indicated update source was down and or possible corruption in DNS resolution of site. (Update source selected by automated registration was in Russia and functioned perfectly at first.) I opened Yast and opened installation sources. Error response was received indicating update source was not responsive and asked if I wanted to remove update source. I deliberately chose NO and closed the application, however the source was removed. The applet appeared to be functioning without errors now and a new source I opened Yast to auto register a new update source and a mirror in Australia was chosen. *Update functionality was not restored and applet issued no error responses, however when accessing the add/delete installation source was accessed instead of the usual green configuration screen Yast opened the Yast Catalogues and other open suse configuration details were not accessible. I understand this is an enormous sequence of events, some of which * are not logically understood. However it is theorised the it is possible to faithfully reproduce the corruption by activating the Yast Automatic Online Update - time initiated application whilst the open suse online update application has its own time initiated update schedule in place. Attached is Yast log files and image of open suse update application icon. Every care has been taken to state the sequence of events clearly and consistently - whether or not some * of the process has anything to do with the initial and presumable re-producible of corruption is severely questionable. Please advise if any further log files are required IF this cannot be re-produced in a test environment. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 ------- Comment #1 from scocoo@tpg.com.au 2007-05-09 11:25 MST ------- Created an attachment (id=138743) --> (https://bugzilla.novell.com/attachment.cgi?id=138743&action=view) 1 of 3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 ------- Comment #2 from scocoo@tpg.com.au 2007-05-09 11:26 MST ------- Created an attachment (id=138744) --> (https://bugzilla.novell.com/attachment.cgi?id=138744&action=view) 2 of 3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 ------- Comment #3 from scocoo@tpg.com.au 2007-05-09 11:26 MST ------- Created an attachment (id=138745) --> (https://bugzilla.novell.com/attachment.cgi?id=138745&action=view) 3 of 3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 dmacvicar@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |scocoo@tpg.com.au ------- Comment #4 from dmacvicar@novell.com 2007-05-09 14:17 MST ------- Can you try deleting /var/lib/zypp/cache/updates_* and select "check now" in the applet's menu? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|scocoo@tpg.com.au | ------- Comment #5 from alpha096@tpg.com.au 2007-05-10 00:28 MST ------- Quotue: I opened Yast to auto register a new update source and a mirror in Australia was chosen. The applet appeared to be functioning without errors now and a new source. By chiefly disengaging the yast automatic update time and changing the open applet source from default and back again. I have been able to fix this issue - however I feel the same error is easily duplicated by opensusupdater and Yast online updater sked at 23:00 hours to be both engaged and in competition will be evident the next time both attempt to use different initiation schedules - hence the primary error response. Please let me know IF you cannot duplicate this i the lab -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 jkupec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jkupec@novell.com Severity|Major |Minor Status|NEW |ASSIGNED Summary|Open Suse Updater - |[opensuse-updater] [zypp-check-patches] - can't |Corruption in application |check patches if another zypp app is running |and error responses | ------- Comment #6 from jkupec@novell.com 2007-05-10 03:46 MST ------- Hi Scott, i reproduced the problem. It will be fixed in openSUSE 10.3 by fixing repository management issues in libzypp (package management library which YaST and the updater applet uses). However, note that even if you will be able to use YaST Automatic Online Update (which uses zypper in 10.3) and Updater Applet at the same time, you will not be able to actually do the update at the same time. While Automatic Online Update actually installs available patches at scheduled time, Updater Applet only notifies you about available patches and you have to click Install, which executes YaST Online Update to do the update itself. Thus, if you click Install in the very moment when Automatic Online Update is updating your system, you will get the same warning as you got this time, too. However there's no sense in using two update applications at the same time. Just decide between the two. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #7 from alpha096@tpg.com.au 2007-05-10 07:16 MST ------- Yes I totally agree - hover a default current install installs ZEN updater and the opensuseupdater icon that never remain in the system tray. It is not until you remove the Zen updater then and only then does the susopen update function correctly. Happy at new detection in 10.3 and happt to closed as fixed in 10.3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 ------- Comment #8 from alpha096@tpg.com.au 2007-05-10 07:17 MST ------- Happy at new detection in 10.3 and happy to closed as fixed in 10.3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 jkupec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | Fixed in Milestone|--- |openSUSE 10.3 ------- Comment #9 from jkupec@novell.com 2007-05-10 07:56 MST ------- Not fixed yet, but soon :O) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 jkupec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 ------- Comment #10 from alpha096@tpg.com.au 2007-05-14 04:21 MST ------- I am also able to corrupt the open suse applet by the following: Yast>Security and Users>Local Security>Custom>set file permissions to "secure" * Re-boot system. Applet should now be a triangle with question mark. *. Possible variable. It is unknown how long time interval session must remain with either "secure" or "easy" settings before re-boot. Unknown variable in background initiation of global file changes -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=272829 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=272829#c12 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com, visnov@novell.com, | |aschnell@novell.com, dmacvicar@novell.com, | |ma@novell.com Component|Update Problems |libzypp Product|openSUSE 10.2 |openSUSE 10.3 Target Milestone|openSUSE 10.3 |--- --- Comment #12 from Ján Kupec <jkupec@novell.com> 2008-01-24 03:41:14 MST --- It appears we haven't dealt with this problem yet. ZYpp locking mechanism has to be changed in order to solve 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.
https://bugzilla.novell.com/show_bug.cgi?id=272829 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[opensuse-updater] [zypp-check-patches] - can't |[opensuse-updater] [zypper] - can't check |check patches if another zypp app is running |patches if another zypp app is running -- 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=272829 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=272829#c13 --- Comment #13 from Ján Kupec <jkupec@novell.com> 2008-01-24 03:54:33 MST --- In short: user uses YaST Automatic Online Update, which installs a cron job using zypper to perform the update. At the same time, the user uses the updater applet, which reports an error while checking for updates in the event the zypper executed by the cron job is still running. This is not very sane use case though. But the question is whether we just improve the help text in the Automatic Online Update to make the user aware of the possibility of conflict with another update application or we do something about the zypp locks. -- 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=272829 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=272829#c14 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jkupec@novell.com |zypp-maintainers@forge.provo.novell.com Status|ASSIGNED |NEW --- Comment #14 from Ján Kupec <jkupec@novell.com> 2008-03-21 06:39:16 MST --- Do we already have a bug for the zypp locks improvement? -- 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=272829 Duncan Mac-Vicar <dmacvicar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- 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=272829 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=272829#c15 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #15 from Michael Andres <ma@novell.com> 2008-08-07 08:10:51 MDT --- *** This bug has been marked as a duplicate of bug 373165 *** https://bugzilla.novell.com/show_bug.cgi?id=373165 -- 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.
participants (1)
-
bugzilla_noreply＠novell.com