Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
non-integer constraints not handled correctly for add-machines API #45
Comments
battlemidget
self-assigned this
Feb 7, 2017
battlemidget
added
the
bug
label
Feb 7, 2017
|
This is the culprit:
The constraints aren't being parsed propery for juju to handle. working through this now |
mikemccracken
changed the title from
Big Data spells not waiting for deploys to complete
to
non-integer constraints not handled correctly for add-machines API
Feb 7, 2017
mikemccracken
assigned
mikemccracken
and unassigned
battlemidget
Feb 7, 2017
mikemccracken
referenced this issue
in conjure-up/conjure-up
Feb 7, 2017
Closed
non-integer constraints not handled correctly for add-machines API #654
|
moved to conjure-up/conjure-up#654 |
mikemccracken
closed this
Feb 7, 2017
|
Thanks for the quick work on this. Do you know when this will be in the beta channel as docs have
and this is pretty prevalent? |
|
I've got a couple more tests to run and then I'll push to beta today |
|
The current beta works it just doesn't process the constraints |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
arosales commentedFeb 7, 2017
•
Edited 1 time
-
mikemccracken
Feb 7, 2017
It seems with the new 00_deploy-done code the spell is not waiting for the deploy to complete. In recent testing as soon as I select to deploy application the spell almost immediately goes to the final ganglia test which errors in the following stack trace:
The deployment usually takes about 10 minutes in AWS. The spell is only waiting < 1 minute before going to the final ganglia step. Thus, I don't think we are waiting for the applications to be become active.
-thanks,
Antonio