fail to provision workers

[tomdavidson]

I am not able to generate certs with letsencrypt using 0.8.6. I have tried with an existing domain that also had a private zone and then registered a new domain without any other records other then the R53 NS and SOA - same error in both cases.

GENERATING BOSH DIRECTOR CERTIFICATE (34.215.198.136, 10.0.0.6)
2018/03/23 16:48:50 [INFO] acme: Registering account for nobody@example.com
2018/03/23 16:48:51 [INFO][cci.incontact.xyz] acme: Obtaining bundled SAN certificate
2018/03/23 16:48:51 [INFO][cci.incontact.xyz] AuthURL: https://acme-v01.api.letsencrypt.org/acme/authz/GPwqvnpIT8w2hqwikRsZYOHd1-DpixlH5krOpm9BW8M
2018/03/23 16:48:51 [INFO][cci.incontact.xyz] acme: Could not find solver for: http-01
2018/03/23 16:48:51 [INFO][cci.incontact.xyz] acme: Trying to solve DNS-01
map[cci.domain.xyz:Error presenting token: Failed to determine Route 53 hosted zone ID: Could not find the start of authority]

[tomdavidson]

There is a bigger issue at hand. No EC2 resources are provisioned and concourse-up info --region us-west-2 --json cci times out after ~60 sec with exit 1.

[tomdavidson]

I have tried several steps in my script, provisioning the EC2 resources is odd:

fail:

    concourse-up deploy \
        --region $REGION \
        --domain $NAME.$ZONE \
        $NAME

fail:

    concourse-up deploy \
        --region $REGION \
        --domain $NAME.$ZONE \
        --workers $WORKER_COUNT \
        --db-size $DB_SIZE \
       $NAME

fail:

    concourse-up deploy \
        --region $REGION \
        --domain $NAME.$ZONE \
        --workers $WORKER_COUNT \
        --db-size $DB_SIZE \
       $NAME

    concourse-up deploy \
        --region $REGION \
        --domain $NAME.$ZONE \
        --workers $WORKER_COUNT \
        --db-size $DB_SIZE \
       $NAME

pass:

    concourse-up deploy \
        --region $REGION \
         --domain $NAME.$ZONE \
         $NAME

    concourse-up deploy \
         --region $REGION \
         --workers $WORKER_COUNT \
         --db-size $DB_SIZE \
         $NAME

[crsimmons]

@tomdavidson are you still experiencing this issue with the latest version of concourse-up? Feel free to reopen the issue if you are and we will investigate.