Comment 6 for bug 1599779

Just bootstrapping. Machine is quiescent in terms of doing anything real
with Juju. Adding a container takes a long time given the CPU usage. As do
various other Juju operations (status, show-machines, etc).

On 12 July 2016 at 13:46, James Tunnicliffe <email address hidden>
wrote:

> Are you simply bootstrapping to GCE? Any other machines / containers /
> services?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1599779
>
> Title:
> Very high CPU usage from 'creating cloud image metadata storage'
> emitted in debug log every second
>
> Status in juju-core:
> New
>
> Bug description:
> Bootstrapping on Google I see the following output from the debug-log
> repeated many many times resulting in high CPU usage against jujud and
> mongod. This does not happen in beta10, so something since then.
>
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
> creating cloud image metadata storage
> started state for model-3bdf9f1a-f7e9-4486-840c-d82d3846e3a6 successfully
> starting standard state workers
>
> This repeated block of output is happening every few seconds; see the
> attached machine-0.log.
>
> I tried to bisect this a little:
>
> $ git bisect good
> There are only 'skip'ped commits left to test.
> The first bad commit could be any of:
> f44f3ccfc8f2aad18273ac2f4b5ee83afc7414d4
> 1db368791b4341a0482c57747935bb44642ff067
> 6a4a21838f35969a93c7fa8e4c5035186f833705
> 0a5bd61f6c85d9caf9ead484fc88d6dc525c4635
> 9ce1f5a9ec85b9750c9911b5a7cc42f2cc19fc4b
> 2e49459b30930bbceacdd09b4e5473b4f81d654b
> 535c3f0ac268d4b9c2d84126b57cef7df0f63b33
> a392876040e8323c9fca9f53a0586cfcf0d4750e
> We cannot bisect more!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1599779/+subscriptions
>

--
Andrew McDermott <email address hidden>
Juju Core Sapphire team <http://juju.ubuntu.com>