when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i “have not provided a valid image (AMI) value.” but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
I see there are two versions of fog installed. Probably the knife-ec2
plugin uses the old plugin. One thing to try is to remove the 1.6.0 fog
library and try again.
when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i "have not provided a valid image (AMI) value." but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
AMIs only exist in one datacenter. If you're using somebody else's you'll
need to find a different AMI id for each datacenter. If you've made your
own you'll need to figure out how to move them. I think AWS has tools for
it but can't recall for sure.
I see there are two versions of fog installed. Probably the knife-ec2
plugin uses the old plugin. One thing to try is to remove the 1.6.0 fog
library and try again.
when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i "have not provided a valid image (AMI) value." but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
thanks for the responses so far. but i still need help:
the us-west-2 issue is fixed in both fog 1.6.0 and 1.8.0:
[zahadum fog-1.8.0]$ cd ../fog-1.6.0/
[zahadum fog-1.6.0]$ grep us-west-2 changelog.txt
us-west-2 default ami. thanks Edward Muller
add us-west-2 region. thanks geemus
each specific AMI ID i try in east and west is an AMI i built specifically
in that region. so there's no need to move any AMIs. "knife ec2 server
create" works for me when launching in east, but not west.
any other ideas?
On Fri, 11 Jan 2013, Leo Dirac (SR) wrote:
AMIs only exist in one datacenter. If you're using somebody else's you'll
need to find a different AMI id for each datacenter. If you've made your
own you'll need to figure out how to move them. I think AWS has tools for
it but can't recall for sure.
I see there are two versions of fog installed. Probably the knife-ec2
plugin uses the old plugin. One thing to try is to remove the 1.6.0 fog
library and try again.
when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i "have not provided a valid image (AMI) value." but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
thanks for the responses so far. but i still need help:
the us-west-2 issue is fixed in both fog 1.6.0 and 1.8.0:
[zahadum fog-1.8.0]$ cd ../fog-1.6.0/
[zahadum fog-1.6.0]$ grep us-west-2 changelog.txt
us-west-2 default ami. thanks Edward Muller
add us-west-2 region. thanks geemus
each specific AMI ID i try in east and west is an AMI i built specifically
in that region. so there's no need to move any AMIs. "knife ec2 server
create" works for me when launching in east, but not west.
any other ideas?
On Fri, 11 Jan 2013, Leo Dirac (SR) wrote:
AMIs only exist in one datacenter. If you're using somebody else's you'll
need to find a different AMI id for each datacenter. If you've made your
own you'll need to figure out how to move them. I think AWS has tools for
it but can't recall for sure.
I see there are two versions of fog installed. Probably the knife-ec2
plugin uses the old plugin. One thing to try is to remove the 1.6.0 fog
library and try again.
when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i "have not provided a valid image (AMI) value." but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
has anyone else on the list successfully created a node with knife ec2
in us-west-2? i'm wondering if it's just me, if i need to crack open
the the code to figure out how to further debug this.
running the below-mentioned knife ec2 command with -VV only gives me:
DEBUG: Using configuration from /home/kallen/.chef/knife.rb
ERROR: You have not provided a valid image (AMI) value. Please note the short
option for this value recently changed from '-i' to '-I'.
thanks for the responses so far. but i still need help:
the us-west-2 issue is fixed in both fog 1.6.0 and 1.8.0:
[zahadum fog-1.8.0]$ cd ../fog-1.6.0/
[zahadum fog-1.6.0]$ grep us-west-2 changelog.txt
us-west-2 default ami. thanks Edward Muller
add us-west-2 region. thanks geemus
each specific AMI ID i try in east and west is an AMI i built specifically
in that region. so there's no need to move any AMIs. "knife ec2 server
create" works for me when launching in east, but not west.
any other ideas?
On Fri, 11 Jan 2013, Leo Dirac (SR) wrote:
AMIs only exist in one datacenter. If you're using somebody else's you'll
need to find a different AMI id for each datacenter. If you've made your
own you'll need to figure out how to move them. I think AWS has tools for
it but can't recall for sure.
I see there are two versions of fog installed. Probably the knife-ec2
plugin uses the old plugin. One thing to try is to remove the 1.6.0 fog
library and try again.
when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i "have not provided a valid image (AMI) value." but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
has anyone else on the list successfully created a node with knife ec2
in us-west-2? i'm wondering if it's just me, if i need to crack open
the the code to figure out how to further debug this.
running the below-mentioned knife ec2 command with -VV only gives me:
DEBUG: Using configuration from /home/kallen/.chef/knife.rb
ERROR: You have not provided a valid image (AMI) value. Please note the short
option for this value recently changed from '-i' to '-I'.
thanks for the responses so far. but i still need help:
the us-west-2 issue is fixed in both fog 1.6.0 and 1.8.0:
[zahadum fog-1.8.0]$ cd ../fog-1.6.0/
[zahadum fog-1.6.0]$ grep us-west-2 changelog.txt
us-west-2 default ami. thanks Edward Muller
add us-west-2 region. thanks geemus
each specific AMI ID i try in east and west is an AMI i built specifically
in that region. so there's no need to move any AMIs. "knife ec2 server
create" works for me when launching in east, but not west.
any other ideas?
On Fri, 11 Jan 2013, Leo Dirac (SR) wrote:
AMIs only exist in one datacenter. If you're using somebody else's you'll
need to find a different AMI id for each datacenter. If you've made your
own you'll need to figure out how to move them. I think AWS has tools for
it but can't recall for sure.
I see there are two versions of fog installed. Probably the knife-ec2
plugin uses the old plugin. One thing to try is to remove the 1.6.0 fog
library and try again.
when i try to use knife ec2 to create a node in ec2 us-west-2, i get an
error saying i "have not provided a valid image (AMI) value." but, i in
fact did supply a valid ID with the correct syntax. however, i run the
same kind of command for us-east-1, and it works.
hmm. that AMI, 12.04 LTS 64bit instance-store, also fails for me in
us-west-2. but in us-east-1, ami-d726abbe, 12.04 LTS, works.
i don't understand ...
west:
[zahadum ~]$ knife ec2 server create -N host01.gruentea.com -E prod_foo -S prod-foo-keypair -Z us-west-2b -f m1.large -I ami-ca2ca4fa -g sg-xyz --user-data /path/chef-repo/nodes/node-host01.gruentea.com.json --distro okta-ubuntu-launch -VV
DEBUG: Using configuration from /home/kallen/.chef/knife.rb
ERROR: You have not provided a valid image (AMI) value. Please note
the short option for this value recently changed from '-i' to '-I'.
has anyone else on the list successfully created a node with knife ec2
in us-west-2? i'm wondering if it's just me, if i need to crack open
the the code to figure out how to further debug this.
running the below-mentioned knife ec2 command with -VV only gives me:
DEBUG: Using configuration from /home/kallen/.chef/knife.rb
ERROR: You have not provided a valid image (AMI) value. Please note the short
option for this value recently changed from '-i' to '-I'.
hmm. that AMI, 12.04 LTS 64bit instance-store, also fails for me in
us-west-2. but in us-east-1, ami-d726abbe, 12.04 LTS, works.
i don't understand ...
west:
[zahadum ~]$ knife ec2 server create -N host01.gruentea.com -E prod_foo
-S prod-foo-keypair -Z us-west-2b -f m1.large -I ami-ca2ca4fa -g sg-xyz
--user-data /path/chef-repo/nodes/node-host01.gruentea.com.json --distro
okta-ubuntu-launch -VV
DEBUG: Using configuration from /home/kallen/.chef/knife.rb
ERROR: You have not provided a valid image (AMI) value. Please note
the short option for this value recently changed from '-i' to '-I'.
has anyone else on the list successfully created a node with knife ec2
in us-west-2? i'm wondering if it's just me, if i need to crack open
the the code to figure out how to further debug this.
running the below-mentioned knife ec2 command with -VV only gives me:
DEBUG: Using configuration from /home/kallen/.chef/knife.rb
ERROR: You have not provided a valid image (AMI) value. Please note
the short
option for this value recently changed from '-i' to '-I'.