Trying to vagrant up on AWS about pcfdev

[omearaj]

BTW, this same Vagrantfile worked running it locally on virtualbox

[sclevine]

Hi @omearaj,

Are you still experiencing this issue with 0.4.0?

[omearaj]

@sclevine - Its been running for about 3 hours and showing the message below. I'm able to target the api and login but pushing a simple spring application fails this:

When I try to start the app I get a staging error.

reating app next in org micropcf-org / space mpcf-space as admin...
OK

Creating route next.54.165.43.XXX.xip.io...
OK

Binding next.54.165.43.XXX.xip.io to next...
OK

Uploading next...
Uploading app files from: target/scale-1.0.0-BUILD-SNAPSHOT.war
Uploading 6.2M, 59 files
Done uploading
OK

timeout connecting to log server, no log will be shown
Starting app next in org micropcf-org / space mpcf-space as admin...
FAILED
Error performing request: Get http://api.54.165.43.XXX.xip.io/v2/apps/07c472f3-ca2c-4e6a-b086-ff708626a891: dial tcp: lookup api.54.165.43.XXX.xip.io: no such host

This is the message from the vagrant up on AWS

==> default: Box 'micropcf/base' could not be found. Attempting to find and install...
default: Box Provider: aws
default: Box Version: 0.24.0
==> default: Loading metadata for box 'micropcf/base'
default: URL: https://atlas.hashicorp.com/micropcf/base
==> default: Adding box 'micropcf/base' (v0.24.0) for provider: aws
default: Downloading: https://atlas.hashicorp.com/micropcf/boxes/base/versions/0.24.0/providers/aws.box
==> default: Successfully added box 'micropcf/base' (v0.24.0) for 'aws'!
==> default: Checking if box 'micropcf/base' is up to date...
==> default: Warning! The AWS provider doesn't support any of the Vagrant
==> default: high-level network configurations (config.vm.network). They
==> default: will be silently ignored.
==> default: Launching an instance with the following settings...
==> default: -- Type: m4.large
==> default: -- AMI: ami-71510f1b
==> default: -- Region: us-east-1
==> default: -- Keypair: vagrant
==> default: -- Block Device Mapping: []
==> default: -- Terminate On Shutdown: false
==> default: -- Monitoring: false
==> default: -- EBS optimized: true
==> default: -- Source Destination check:
==> default: -- Assigning a public IP address in a VPC: false
==> default: -- VPC tenancy specification: default
==> default: Waiting for instance to become "ready"...
==> default: Waiting for SSH to become available...
==> default: Machine is booted and ready for use!
==> default: Running provisioner: shell...
default: Running: inline script
==> default: stdin: is not a tty
==> default: Waiting for services to start...

[davidwadden]

This looks like an issue with xip.io resolution. We have a couple of known issues (reported on our releases page) with AWS (xip.io flakiness and EBS base storage can't handle cf push). We recommend either using VirtualBox or VMware at this point in time, we're still working on making AWS more reliable and more performant.

[omearaj]

Thanks @davidwadden I'll try AWS in a future release. It did work on virtualbox locally.

[vatsan]

I am stuck on the "default: Waiting for services to start..." message as well. I am using VirtualBox on a Mac. Any pointers? It's been stuck for over 2 hours now!

[debu66er]

@vatsan are you connected to Internet? When I try to start MicroPCF connectivity I get stuck where you are now. Just guessing if it is your same case...

[davidwadden]

i'm going to close this issue as we're planning to revisit AWS in the future and it's not being supported in the initial release. we haven't had luck getting the I/O throughput necessary to have CF operate in a stable manner.

@vatsan we can discuss the issues you're seeing on #26
@debu66er can you open a new issue and give us details on what version you're running and your configuration? that Waiting for services to start... message will hang indefinitely if the cluster fails to start properly