llation
https://bugs.launchpad.net/trove/+bug/1658008
3. Tesora EE 1.9
The instance will go to error state because of request timeout error.
On Thu, Mar 09, 2017 at 06:47:18AM -0500, Amrith Kumar wrote:
> Wang Sen, in what environment is this (x86 or non-x86)? I know of at least
> three teams
I have been trying to deploy trove since last December, but my database
instances never escape from BUILD or Error state :(
On Tue, Mar 07, 2017 at 09:15:25PM +1300, Mark Kirkwood wrote:
> I haven't tried to get Trove working with latest versions - but
> experience with previous (Kilo, Liberty,
2017 at 8:59 PM, Amrith Kumar <amrith.ku...@gmail.com>
> wrote:
>
> > Sorry Wang Sen, why do you say Trove is not ready for Neutron"? It has
> > worked with Neutron for some releases now.
> >
> > This does not appear to be at all related to Neutron.
> >
&
Sorry Amrith, I mispelled Newton as neuton ... :(
On Wed, Jan 18, 2017 at 10:59:06PM -0500, Amrith Kumar wrote:
> Sorry Wang Sen, why do you say Trove is not ready for Neutron"? It has
> worked with Neutron for some releases now.
>
> This does not appear to be at all r
Hi all,
I met the resource not found error when I'm creating a database
instance. The instance stays on build status and turns to error status
after timeout.
I know trove is not ready for neuton. Is there a work around for this
issue ? Thanks in advance.
Below is the detailed information.
