conjure-up: no xenial images found about spells

[johnsca]

The error is from Juju and indicates that it couldn't find the instance image to use when creating the controller. Testing it myself now, I was unable to replicate the issue. Considering Juju 2.5 was just recently released, I suspect this was a transient issue with the timing of getting the images out to the image repository. Can you please try this again and see if it has resolved itself? Thanks.

[tburow]

Yea I’ve tried multiple times with the same error.

If I choose jaas for hosted deployment I get past that but it’s constantly failing on the compleation step for kubectl

Same results with core also.

[johnsca]

I'm not really sure what the issue is, since I'm able to bootstrap with Juju 2.5.0 on AWS us-east-1 without issue. I've opened a Juju Discourse thread asking for assistance from the Juju folks.

[mitechie]

Check that if you're using a really old aws account that you have a valid default VPC please.

[tburow]

hmm that brings up a different point, how do I specify a specific vpc and no public IPs? but that's tertiary to the fact I cant seem to get this to work out of the box in basic form.

Two errors that seem to have a common theme are

• failure to find the ami image (running local NOT hosted JaaS)
• failure to execute post kubectl steps (running JaaS)
  (other threads with these errors and seemingly random fixes)

If I run a deploy in The Jaas web console, things seem to work fine. but running from conjure-up on cli it fails in both deployment scenerios with different errors.

this is out of the box, no custom configs

[tburow]

im going to close this issue as unresolved. I'm going to move on to another tool and dont want to take more of folks time. ty for your suggestions