[Bug 540587] New: If Yast MUST NOT kill SQUID in middle of system update!
http://bugzilla.novell.com/show_bug.cgi?id=540587 Summary: If Yast MUST NOT kill SQUID in middle of system update! Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse@tlinx.org QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 I was doing a system update. Normally my web requests go through squid to take advantage of a large local (6GB) disk cache for various downloaded objects. However, yast also pays attention to the global vars HTTP_PROXY and friends, and uses them during its operations. Normally not a problem. However I was doing a Factory update. That just happened to include squid this time. About half way through a 500MB download/update it suddenly lost its connection -- and hung. Restarting squid didn't help. It was dead and required restart -- at which point trying to redo the factory update was futile -- it thought everything was done -- BUT the configuration of every service it updated was *wiped* and set to 'off'. I'm having to go through each service as I find which ones it killed and wiped and reconfig or at least restart them. But in a few cases, the config files have been reinitialized to non-workable values. Examples: xinetd was setup with no tcpmux builtin configure, so installed services like vnc generated errors because the standard vnc-server needs TCPMUX. The arpwatchd was no longer looking on my inside net, but on my outside and talking about bogons because it lost it's local group list. It also was no longer in its own group. named is now generating messages about not having write access to its working directory (don't know if this is a new message, or something was changed). The squid startup script was replaced and the old one wasn't saved -- I had it set to filter some common error messages (restored from an edit backup). Might be a few others -- several services were just 'stopped (chkconfiged 'off') when they had been on. Have yet to do an exhaustive search for problems, as I'm still in firefighting mode. But Yast really needs to be smart enough to check, if it is using a proxy server, AND proxy server is on same system, it needs to be "very circumspect about restarting it (if it should restart it at all, maybe it should ask user or wait for reboot?)...but if it closed all connections and was sure it would restart, then it could auto-restart it just like when log-rotation happens periodically. Marking this Critical, as it has cost a large amount of time to recover from this (still in progress).... and did lose some data (though I probably have earlier backups I could restore from, I'm taking opportunity to recheck configs. I am noticing some (1-2?) incompatible config files with the new versions that were installed. Will try to remember to file more bugs later...but filing bugs takes me away from fixing, and my email is another service that is broken right now. (was trying to fix some configuration problem and I've made things worse! --- ;^) so what else is new...but if it hadn't been broken in the first place, I probably wouldn't have been mucking w/it!...but hey, it *is* a learning experience, so I'm not "angry", more like 'annoyed'...and wanting to create this bug as a notice of the problem. Reproducible: Didn't try Steps to Reproduce: 1. have "alot" of updates (I didn't see all the updates -- it autoselected "A bunch" more than I had picked out...(as usual ;^/ )...dependency hell! 2. I was updating through a proxy server (squid) running on the machine being updated -- I didn't explicitly ask yast todo this, it just took the values from my environment vars (HTTP_PROXY & such)... 3. One of the packages updated, "apparently" was squid...right in the middle of the updates. It left my system in an inconsistent and ill-or-unconfiged state with many serviced turned off (that had been on ). Actual Results: System way messed up. Expected Results: Normal factory upgrade. -- Configure bugmail: http://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=540587 User rszhu@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c1 zhu rensheng <rszhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |locilka@novell.com |ovo.novell.com | --- Comment #1 from zhu rensheng <rszhu@novell.com> 2009-09-20 21:50:18 MDT --- I think this a bug with update. If you are not the maintainer of this bug, please help me reassign it to the proper maintainer. Thank you. -- Configure bugmail: http://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=540587 Lukas Ocilka <locilka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|locilka@novell.com |mls@novell.com -- Configure bugmail: http://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=540587 Michael Schröder <mls@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mls@novell.com |zypp-maintainers@forge.prov | |o.novell.com -- Configure bugmail: http://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=540587 User ma@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c2 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com, | |ma@novell.com AssignedTo|zypp-maintainers@forge.prov |hvogel@novell.com |o.novell.com | --- Comment #2 from Michael Andres <ma@novell.com> 2009-09-21 08:27:28 MDT --- With 11.2 you will be able to configure libzypp to download all packages before the installation is actually started - provided you have enough diskspace. If so, there's at least less risk that the installation fails and leaves your system in an inconsistent state. But those service restarts are triggered by the packages %pre/post scripts itself, not by yast. Dont't know if this can be done smoother. Assigning to the sqid maintainer. -- Configure bugmail: http://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=540587 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c3 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER+ --- Comment #3 from Stephan Kulow <coolo@novell.com> 2009-09-21 10:19:45 MDT --- marking ship stopper - we need at least to document it. -- Configure bugmail: http://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=540587 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c4 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hvogel@novell.com |aj@novell.com --- Comment #4 from Stephan Kulow <coolo@novell.com> 2009-10-13 08:36:05 MDT --- I assign this action item to AJ, lack of time ;( -- Configure bugmail: http://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=540587 User aj@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c5 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aj@novell.com |ke@novell.com --- Comment #5 from Andreas Jaeger <aj@novell.com> 2009-10-13 08:51:44 MDT --- Karl, please add the following to the release notes: If you update with zypper dup, packages might get restarted during the process and it can happen that the restart does not succeed before you adjust the config files. This is especially critical if your system uses services needed for downloading the update, e.g. a local proxy (squid) on the machine you update. Set commit.downloadMode = DownloadInAdvance in /etc/zypp/zypp.conf so that first everything is downloaded and then packages get installed. This needs enough space on the /var partition to hold all downloaded packages. Afterwards, let's reassign to Henne for fixing squid. -- Configure bugmail: http://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=540587 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c6 --- Comment #6 from Stephan Kulow <coolo@novell.com> 2009-10-13 09:30:46 MDT --- should we make the release notes really a "things to note when you zypper dup"? I would think this should be split. -- Configure bugmail: http://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=540587 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER+ |SHIP_STOPPER- -- Configure bugmail: http://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=540587 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c7 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #7 from Karl Eichwalder <ke@novell.com> 2009-10-19 03:46:42 MDT --- (In reply to comment #5)
Karl, please add the following to the release notes:
If you update with zypper dup, packages might get restarted during the process and it can happen that the restart does not succeed before you adjust the config files. This is especially critical if your system uses services needed for downloading the update, e.g. a local proxy (squid) on the machine you update.
Set commit.downloadMode = DownloadInAdvance in /etc/zypp/zypp.conf so that first everything is downloaded and then packages get installed. This needs enough space on the /var partition to hold all downloaded packages.
Afterwards, let's reassign to Henne for fixing squid.
Thanks for the draft! -- Configure bugmail: http://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=540587 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c8 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |fs@novell.com --- Comment #8 from Karl Eichwalder <ke@novell.com> 2009-10-19 03:51:38 MDT --- (In reply to comment #6)
should we make the release notes really a "things to note when you zypper dup"? I would think this should be split.
Yeah. Basic info about "zypper dup" is already in the manual (11.2)--see the section about zypper and the update chapter. I think for the moment this should go into the release notes. The books are already locdrop'ed (sent to Dublin for translation). -- Configure bugmail: http://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=540587 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c9 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |hvogel@novell.com, | |ke@novell.com Info Provider| |aj@novell.com --- Comment #9 from Karl Eichwalder <ke@novell.com> 2009-10-22 00:31:19 MDT --- Reading the bug again, I think it is not about "zypper dup", but the usual online updates with yast (on 11.1). I'm not sure whether it is a yast or squid issue, though. Of course, we could document the new zypper config option nevertheless... -- Configure bugmail: http://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=540587 User aj@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c10 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|aj@novell.com |suse@tlinx.org --- Comment #10 from Andreas Jaeger <aj@novell.com> 2009-10-22 01:31:30 MDT --- I doubt this happens during YaST update since then squid would not run. Let's ask the original reporter. -- Configure bugmail: http://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=540587 User suse@tlinx.org added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c11 --- Comment #11 from L. A. Walsh <suse@tlinx.org> 2009-10-22 01:07:43 PDT ---
From first few of initial report...
I was doing a system update. Normally my web requests go through squid to take advantage of a large local (6GB) disk cache for various downloaded objects. However, >>>yast<< also pays attention to the global vars HTTP_PROXY and friends, and uses them during its operations. Normally not a problem. -------- I was running the GUI version of YaST -- the same would likely happen with zypper -- I mean they have to pay attention to the proxy, it just so happens if they are updating the proxy package AND it is running on the same machine, ... *cough*; *choke*. Probably need to check if running through a proxy, does proxy addr reverse DNS evaluate to the reverse DNS of the current machine?... That would have prevented my 'hiccup'..., but better would be to loop through all the interface addresses and see if any match the proxy in case I was using a name associated with a different interface ?? Is this the information you were looking for? Should be able to download squid, run the install, then restart it, then continue with downloading more packages....just have to be sure to not be downloading while squid is restarting. Ideally closing the connection ... doesn't usually take squid long to restart if there are no connections -- a few seconds. Should be able to update squid while it is running unless the update deletes the cache directory or something. -- Configure bugmail: http://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=540587 User suse@tlinx.org added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c12 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|suse@tlinx.org | --- Comment #12 from L. A. Walsh <suse@tlinx.org> 2009-10-22 01:09:52 PDT --- clear Needinfo -- Configure bugmail: http://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=540587 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c13 --- Comment #13 from Karl Eichwalder <ke@novell.com> 2009-10-22 03:36:04 MDT --- I still think you did a manual on-line update to update your system ;) That's not what we normally call "system update" or "system upgrade". For sure, you did not call "zypper dup" or "zypper dist-upgrade". OTOH, the last squid update for 11.1 was this one (rather old): ------------------------------------------------------------------- Wed Feb 18 03:31:00 CET 2009 - crrodriguez@suse.de - fix CVE-2009-0478 [bnc#472834] ==================================================================== BTW, are you running squid or squid3? Are you really using 11.1? Or some kind of openSUSE:Factory? -- Configure bugmail: http://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=540587 User suse@tlinx.org added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c14 --- Comment #14 from L. A. Walsh <suse@tlinx.org> 2009-10-22 04:43:27 PDT --- I hadn't upgraded the system for quite some time, and just got it to finally register so I could theoretically get autoupdates. Then I thought there was an option to update after that, but it's been a while. Took that option and AFAIK, am still running 11.1. It had about 500+MB to download for the updates. running squid3 -- Configure bugmail: http://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=540587 User ma@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c15 --- Comment #15 from Michael Andres <ma@novell.com> 2009-10-22 06:02:37 MDT --- - Comment #9: '..whether it is a yast or squid issue...' This is a potential problem whenever you update a package in a running system. It is not related to squid only. It is not related to dup only. It is not related to openSUSE only. If one of the components required to perfrom the update (rpm, aria, curl, bash, network, ..) breaks during the update, then you are stuck. The solver can check whether the packages dependencies are ok, but NOT if after the package update configfiles, package version and system settings still fit together. If you apply changes to a configfile and the package overwrites it, the service may fail because the options are missing. If the package does not overwrite your configfile, the service may fail because the options are no longer supported, or because some newly introduced option is now missing. Whatever you do it may fail. The more packages involved, the bigger the chance for something to break. And zypper dup performing a real distribution upgrade is a big transaction. - If you encourage people to set DownloadInAdvance when doing zypper dup to migrate from one openSUSE version to another, you should also tell them that they probably need really much diskspace. This kind of dup will probably update almost all installed packages. -- Configure bugmail: http://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=540587 User suse@tlinx.org added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c16 --- Comment #16 from L. A. Walsh <suse@tlinx.org> 2009-10-22 09:48:59 PDT ---
It is not related to squid only. It is not related to dup only. It is not related to openSUSE only.
If one of the components required to perfrom the update (rpm, aria, curl, bash, network, ..) breaks during the update, then you are stuck.
There are some differences in the situations you describe. 1) if one is updating a large list of interdependent packages, and downloading as one is installing (which appeared to be the default action(?)) while executing 'yast'(GUI), then one is guaranteed to have a problem if one kills off the network. 2) If it's an update to a released product, it would violate expectations for an incompatible change to be introduced as a patched or updated product. You could make your argument if one was performing a live-upgrade to the next level of product -- in that case, all RPMS needed to perform the upgrade should likely be downloaded ahead of time, and critical packages saved for 'last' where they would be less likely to disrupt the installation. Usually, if incompatible changes are made to config files between _upgrades_ (going between versions), those packages need to be moved last if they are critical to the process AND if the user has modified one of the config files. If the config files are in the standard state (unmodified), it should be safe to upgrade that package with its upgraded options. If it's not, then that's a bug in that product. This bug's not about all bugs in all products. It's about not killing off your network infrastructure while you are still using it to download updates that are being interspersed with installs AND to "be careful" about updating packages that are being used as 'infrastructure' so that when a daemon (like squid, in _this_ situation) is restarted, the update process is in a known, idle state so a temporarily dropped connection won't cause a hang, bug can be immediately re-initiated after the package has been _updated_ (within the same release). In the case of squid -- if the update or upgrade process detects it is using a proxy on the same machine that's being updated, it might be prudent to issue a warning and ask if this is intentional -- especially if the proxy is going to be replaced. -- Configure bugmail: http://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=540587 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540587#c17 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ke@novell.com |hvogel@novell.com --- Comment #17 from Karl Eichwalder <ke@novell.com> 2009-10-27 08:31:02 MDT --- For the release notes, I created Bug 550417. This is either a yast limitation or a squid issue, or both. -- Configure bugmail: http://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=540587 http://bugzilla.novell.com/show_bug.cgi?id=540587#c Hendrik Vogelsang <hvogel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hvogel@novell.com |rhaidl@novell.com -- Configure bugmail: http://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=540587 http://bugzilla.novell.com/show_bug.cgi?id=540587#c18 Roman Drahtmueller <draht@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |draht@novell.com AssignedTo|rhaidl@novell.com |ma@novell.com --- Comment #18 from Roman Drahtmueller <draht@novell.com> 2009-11-25 16:22:04 UTC --- Squid does not restart itself, it is being restarted. Can we agree that it is out of squid's scope and responsibility to determine if it is allowed to be restarted? After all, it doesn't care if it's used for downloading updates or surfing bugzilla.novell.com. Re-assigning from rhaidl@ to ma@. Thanks, Roman (new squid package maintainer) -- Configure bugmail: http://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=540587 http://bugzilla.novell.com/show_bug.cgi?id=540587#c19 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #19 from Michael Andres <ma@novell.com> 2009-11-26 14:05:35 UTC --- Like most services, squids %postun script triggers the service restart, so libzypp does not have much influence on it. It will happen at the time the package gets installed. And it's up to the maintainer to decide whether this is done. (AFAIK an admin could turn it of in /etc/sysconfig/services. Then you have to manually restart the services.) Download in advance in order to minimize the risk is available with 11.2. For libzypp on 11.1 this is WONTFIX. -- Configure bugmail: http://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=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c20 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |suse@tlinx.org Component|YaST2 |Upgrade Problems Resolution|WONTFIX | AssignedTo|ma@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 11.1 |openSUSE 13.1 Severity|Critical |Normal --- Comment #20 from L. A. Walsh <suse@tlinx.org> 2014-01-15 11:19:59 PST --- Given that this was marked, minimally for 'need to document', But really was "addressed", indirectly(?) by configuring all packages to download before starting. Also, of note -- there is no reason to shut down squid -- ANY more so, than to kill off any program that has files that are "in use". I.e. Right now(in 13.1), if I update something, I can run "zypper ps" AFTER an update has finished, that will tell me which files are currently being used by running procs that are 'deleted' (i.e. likely replaced by the update that just occurred). This means there are a bunch of programs & services that are NOT automatically halted when one of their files is updated. If you update vim -- would you expect all sessions with vim to be killed off (and hopefully restarted?) as part of the upgrade? Why do this w/squid -- i.e. inconsistent behavior that wouldn't likely be expected because the user is likely to have experience You don't want to shut down existing, working services which are working in the middle of a user session -- especially since service upgrades can cause config-file incompatibilities. Possible actions: 1) Verify that the system state is consistent before restarting the service, so if the restart causes the upgrade to "halt", the user will still have a working system. Note: not ideal, as the user may have updates running on multiple systems and be leaving for a 'long break' (overnight or such, as they are expecting the update to take some time), and they would have to repeat the update in order to continue it. Could be addressed by methods used during initial install after reboot to complete further setup after a reboot. 2) Check users upgrade sourced and see if it will be affected by the step -- network (drivers, squid, "ssh if updating via remote login", socks(dante)...), or local device (replacing a driver or restarting a service used to access the device (i.e. update source on a remote network location, or a cd-driver, or a usb-device or a user-space-device driver). This would be *complicated* for little gain and is merely a way of seeing if a restart of a service 'should be safe' -- if it is not, some other action is needed to ensure that. 3) In case of something like squid, verify that the new config WILL work (squid will restart), and that the setup-engine can seamlessly *reconnect* to reopen the needed repos -- would be likely w/http, less likely with https if some accss check is needed. Other fail examples: stateful NFS vs. stateless, reconfigured samba...etc... 4) Just don't restart the service -- leave that to the user just like zypper doesn't kill off processes using files that are upgraded. They can use "zypper ps" to determine what needs to be restarted. --- a **workaround** that is available, is the option to download the sources to stable local sources (useful by default if usr has option set to save/cache downloaded packages locally). ---------- Am re-opening this, since 1, it was closed as resolved+rejected meaning the bug was invalid or nothing is going to be done about it. Minimally, a workaround is provided, so resolved or closed+feature providing workaround would be more appropriate. Note, the workaround doesn't really solve the base problem of doing something during update that invalidates a source you are updating from (networks, likely being the most vulnerable -- and ALSO, **importantly**, one of the most used methods as it allows downloading only needed updates (vs. an ISO which will download a bunch of things a user may not need). As such, the bug might be reassigned to an update team for eventual handling (GSoC?) or such. It's not a high priority for me as I 99.99% of the time don't use a full product upgrade anymore as it's too likely to fail or break my system and leave it (and me) offline for a long period until it is fixed (my suse system is my gateway to the internet, as well as a data server for all of my other non-linux machines (like windows desktops). If server is down -- everything halts. Lowered importance from critical to normal as a workaround is available (predownload). Listed product as suse 13.1 (current version) as this is still an issue, but left platform as 11.1 since that is where it was originally reported. Changed category to 'Update problems', as that is more appropriate than yast. If it is unlikely this will ever be fixed, please close w/correct resolution (which I think would "resolved/feature", as referring to the workaround, though not thinking that is "strictly" used for workarounds (maybe it is, but doubt it). As noted above, this is not a high priority issue for me personally, as since an upgrade fiasco in going to 11.3, I realized I needed to not try "all at once" upgrades unless I didn't care about all of my systems being out of commission for some unknown amount of time (was online w/in a week, but I was still fixing and repairing found problems 4 months later) :-(. FWIW -- I think more work should be put into supporting piecemeal upgrades and intercompat between versions **where possible**... (but that's another whole issue)... -- 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=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.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.
https://bugzilla.novell.com/show_bug.cgi?id=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c21 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |poeml@cmdline.net --- Comment #21 from Arvin Schnell <aschnell@suse.com> 2014-01-16 08:47:16 UTC --- Based on comment #19 reassigning to bugowner of squid. -- 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=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c22 Roman Drahtmueller <draht@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|poeml@cmdline.net |ma@suse.com --- Comment #22 from Roman Drahtmueller <draht@suse.com> 2014-01-16 09:53:41 UTC --- Based on comment#20 (which I find absolutely correct, btw), reassigning to ma. -- 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=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c23 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |313506 AssignedTo|ma@suse.com |draht@suse.com --- Comment #23 from Michael Andres <ma@suse.com> 2014-01-16 11:57:30 CET --- @Roman: Well, first of all it's up to the package to determine if, when and how the service is restarted. You can e.g. move the service restart to out of %post into %posttrans, so it should be executed _after_ the complete package installation is done. If you do so, your bug will depend on bug #313506, because execution of %posttrans must be moved from within rpm into libzypp. This way we can actually guarantee, that those scripts are not executed too early by rpm (currently immediately after the packages %post scripts). This is targeted for 13.2. -- 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=540587 https://bugzilla.novell.com/show_bug.cgi?id=540587#c24 --- Comment #24 from L. A. Walsh <suse@tlinx.org> 2014-01-16 15:33:34 PST --- Re: Based on comment #19 reassigning to bugowner of squid.... I don't feel good about that -- since EACH component that is part of the source stream is vulnerable. New network driver? do you unload and reload net driver? Or bring it down and restart it? What about cifs/nfs drivers -- or a "fuser" based file system relying on a user space daemon. If I was running through dante/socks, same thing. If I am running through a sshfs or just "ssh"... they shouldn't be restarted eitehr (or rsh if that was used)... Saying squid has a problem (and it may), puts the onus on each tool -- maybe the scripts that do "service restarts" should be put at the end of an entire update? AND -- take a note from Windows:: The old versions of files may remain in use until you reboot the system. To see files using deleted versions press <xxx> or use <zypper command>... Reboot now or later? [later] -- 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