just figured out it was a problem with our loadbalancer and inconsistency caused by it between the mysql databases. So sorry for the false alert.
On Tuesday, July 26, 2016 at 7:33:36 PM UTC+2, Enrico Kern wrote: > > also figured out, it is not happening all the time, but may from 5 > provisionings 3 are affected ranging from various clouds, openstack, ec2 > and with different templates. So really unsure what this is. > > On Tuesday, July 26, 2016 at 7:24:04 PM UTC+2, Enrico Kern wrote: >> >> Hi all, >> >> we cannot create new instances with our open source scalr (latest >> version) since yesterday or so i believe. >> >> scalr-upd complains about this: >> >> 2016-07-26 17:18:43,745 - DEBUG - agent.scalrinit.metadata.azure - Does >> not fit (retry in 1 second): File /var/lib/waagent/ovf-env.xml not exists >> >> which might be the cause for this. Seems like the latest scalr-agent >> update on the stable repo broke this? >> >> This directory doesnt exists, it is the same template we used the past x >> months and it worked flawless like 2 days ago. >> >> On scalr itself the machine is stuck in initializing on "Wait for Agent >> HostInit phase to complete" but i can find in the logs that this message >> was delivered by scalr. >> >> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
