It is hard to say. technically, all you know is that the read-back didn't operate. If a command failed directly following that (ex. an elastic ip didn't attach), it could explain why. We assume this is timing related, and something that eventually resolves (perhaps in order of seconds or less).
I know I'm not saying much, just that I don't know if there would be a problem, just that if there were a problem, you could tell AWS that preceding it, the affected instances failed a readback. If you are concerned about the sudden flare-up, you could ask about it. Ex. this is a readback after runInstances. Before, you'd be able to, now you don't. ask them if there's some behavioral change we should know about? Hope the rambling helps :) -A On Tue, Oct 28, 2014 at 12:00 AM, Yaron Rosenbaum <yaron.rosenb...@gmail.com> wrote: > Hi > > Thank you. > > I’m hitting this every single time. > What’s the practical implications of this? > > (Y) > > On Oct 27, 2014, at 4:06 PM, Adrian Cole <adrian.f.c...@gmail.com> wrote: > > You've hit quite the edge case! Basically, there were instances returned > from the create call that were not returned from the describe call. Eventual > consistency, in other words. > > https://github.com/jclouds/jclouds/blob/master/apis/ec2/src/main/java/org/jclouds/ec2/compute/strategy/EC2CreateNodesInGroupThenAddToSet.java#L163 > > On Mon, Oct 27, 2014 at 6:00 AM, Yaron Rosenbaum <yaron.rosenb...@gmail.com> > wrote: >> >> jclouds.compute - << not api visible instances([{region=us-east-1, >> name=sir-02ggqbxp}]) >> >> >> >> (Y) >> > >
