cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remi Bergsma <RBerg...@schubergphilis.com>
Subject Re: Heads-up: Serious investigator issue in 4.4
Date Wed, 09 Sep 2015 05:07:38 GMT
Yes, I'm sure.

Have a look at table async_job_join_map

What foreign keys are there? I deleted fk_async_job_join_map__join_job_id, as per 4.5 upgrade
script.

Regards, Remi


On 09 Sep 2015, at 01:44, Pierre-Luc Dion <pdion@cloudops.com<mailto:pdion@cloudops.com>>
wrote:

Hello Remi,

Are you sure the async job issue is not fixed in 4.4.4? Because for us
upgrading to it did solve that problem so far.

Thanks for sharing latest info,

Cheers

PL
On Sep 4, 2015 4:34 PM, "Remi Bergsma" <RBergsma@schubergphilis.com<mailto:RBergsma@schubergphilis.com>>
wrote:

Hi all,


This brought me some serious headaches this week. HA in 4.4.4 (and any
4.4.x version would have this) doesn't do investigations properly due to
the Hyper-V investigator returning false instead of null. So, it confirms
any VM as down whereas it may be running. Yes, this becomes a mess indeed
;-) In 4.5 and master this was already fixed.


Links:

https://issues.apache.org/jira/browse/CLOUDSTACK-8811

https://github.com/apache/cloudstack/pull/761


Another issue on 4.4 is with the cleaning of async jobs. That fails due to
a foreign key constraint (also solved in 4.5 already) causing it to block
other jobs:

https://issues.apache.org/jira/browse/CLOUDSTACK-8810


Might write a blog about it once I got some sleep ;-)


We're running 4.4 HEAD now.


I'd recommend anyone using 4.4.x to either compile packages from the 4.4
branch (with the fixes included) or, even better, upgrade to 4.5.2.


Regards,

Remi

PS: I wasn’t able to do any PR review this week. Too busy fire fighting,
worked day & night. Hope to return to normal operations next week.


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message