I know this code exists and it fails all the expunge tests internally.
Do you know why it exists? Why should expunge be > 600 always? Seems
like we're overriding the global setting that the admin sets and
without log/warning.
On 26 January 2013 07:16, Rohit Yadav <bhais...@apache.org> wrote:
> Because of this code in UserVmManagerImpl;
>
> String workers = configs.get("expunge.workers");
> int wrks = NumbersUtil.parseInt(workers, 10);
>
> String time = configs.get("expunge.interval");
> _expungeInterval = NumbersUtil.parseInt(time, 86400);
> if ( _expungeInterval < 600 ) {
> _expungeInterval = 600;
> }
>
> If a expunge interval is < 600s, it's set to 600. For DevCloud the
> interval is just 60s. Because of this, when running integration smoke
> tests, it fails on the last test which is VM expunging. I've added the
> same logic in integration smoke test:
>
> commit bc40ed85e5c97dddd86ce6421feb50c7c92a54c8
> Author: Rohit Yadav <bhais...@apache.org>
> Date: Fri Jan 25 17:42:04 2013 -0800
>
> test_vm_life_cycle: Fix expunging logic as in mgmt server
> Sets expunge interval to 600 if it's less than that
>
> Status of javelin: all basic integration tests for DevCloud passes,
> all build profiles are working including nonoss, mgmt server runs and
> works for various api calls basic zone dogfooded against DevCloud.
>
> Regards.
