+++ This bug was initially created as a clone of Bug #1443654 +++ [ see original bug ] --- Additional comment from Nir Soffer on 2017-06-13 23:09:49 CEST --- (In reply to Michal Skrivanek from comment #20) > (In reply to Michael Burman from comment #18) > > There are a lot of errors on vdsm log during network outage, i have no idea > > if that expected. > > Well, those should be followed up by storage to clean up the messages. > Adding Nir to check that If you think the errors are a storage issue, open a bug so someone from storage can take a look.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
(In reply to Michal Skrivanek from comment #0) > +++ This bug was initially created as a clone of Bug #1443654 +++ > > [ see original bug ] > > --- Additional comment from Nir Soffer on 2017-06-13 23:09:49 CEST --- > > (In reply to Michal Skrivanek from comment #20) > > (In reply to Michael Burman from comment #18) > > > There are a lot of errors on vdsm log during network outage, i have no idea > > > if that expected. > > > > Well, those should be followed up by storage to clean up the messages. > > Adding Nir to check that > > If you think the errors are a storage issue, open a bug so someone from > storage > can take a look. Logs please?
sorry I didn't mention that explicitly other than in the original augmented bug description - all logs and further context is in the original bug 1443654
(In reply to Michal Skrivanek from comment #3) > sorry I didn't mention that explicitly other than in the original augmented > bug description - all logs and further context is in the original bug 1443654 I'm trying to understand what messages you're trying to get rid of. Care to point me in the right direction?
https://bugzilla.redhat.com/show_bug.cgi?id=1443654#c19 grep for Tracebacks, most for them storage's, related to the disconnect. Everything is in the original bug, it's just that Nir asked for a separate bug, so there is this one:-)
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it. If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
Closing old bug. Please reopen if still relevant/you want to work on it.