On Thu, Jul 24, 2014 at 1:01 AM, Nikhil Manchanda
wrote:
>
> Tim Simpson writes:
>
> > To summarize, this is a conversation about the following LaunchPad
> > bug: https://launchpad.net/bugs/1325512
> > and Gerrit review: https://review.openstack.org/#/c/97194/6
> >
> > You are saying the function
Tim Simpson writes:
> To summarize, this is a conversation about the following LaunchPad
> bug: https://launchpad.net/bugs/1325512
> and Gerrit review: https://review.openstack.org/#/c/97194/6
>
> You are saying the function "_service_is_active" in addition to
> polling the datastore service stat
FAILED state) so the logs surfaced this as a DNS error. This change should
> help us avoid such issues.
>
> Thanks,
>
> Tim
>
>
> --
> *From:* Denis Makogon [dmako...@mirantis.com]
> *Sent:* Wednesday, July 23, 2014 7:30 AM
> *To:* OpenStack Development Mailing Li
m]
Sent: Wednesday, July 23, 2014 7:30 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Trove] Guest prepare call polling mechanism issue
Hello, Stackers.
I’d like to discuss guestagent prepare call polling mechanism issue (see [1]).
Let me first describe why this is actually an
Hello, Stackers.
I’d like to discuss guestagent prepare call polling mechanism issue (see
[1]).
Let me first describe why this is actually an issue and why it should be
fixed. For those of you who is familiar with Trove knows that Trove can
provision instances through Nova API and Heat API (see
Hello Stackers.
I’d like to discuss raised issue related to Trove-guestagent prepare call
polling mechanism issue (see [1]).
Let me first describe why this is actually an issue and why it should be
fixed. For those of you who is familiar with Trove knows that Trove can
provision instances throug
