Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 0.9.4
-
Fix Version/s: None
-
Component/s: Knife
-
Labels:None
Description
During the 'bootstrap' phase of "knife [CLOUD TYPE] server create", it attempts to use the validation certificate, but it does so without verifying the file exists before launching the instance in [CLOUD TYPE]. The user then has to clean up the instance manually after fixing the certificate.
% knife ec2 server create "role[webserver]" -i -G www,default -x ubuntu -S jtimberman -f c1.medium Instance ID: i-a9d827c3 Flavor: c1.medium Image: ami-2d4aa444 Availability Zone: us-east-1b Security Groups: www, default SSH Key: jtimberman Waiting for server.......................... Public DNS Name: ec2-174-129-82-13.compute-1.amazonaws.com Public IP Address: 174.129.82.13 Private DNS Name: domU-12-31-38-00-C5-A1.compute-1.internal Private IP Address: 10.252.202.79 Bootstrapping Chef on 174.129.82.13 /Library/Ruby/Gems/1.8/gems/chef-0.9.5/lib/chef/knife/bootstrap.rb:81:in `read': No such file or directory - /Users/jtimberman/Development/joshtest/.chef/joshtest-validation.pem (Errno::ENOENT) from /Library/Ruby/Gems/1.8/gems/chef-0.9.5/lib/chef/knife/bootstrap.rb:81:in `run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.5/lib/chef/knife/ec2_server_create.rb:130:in `run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.5/lib/chef/application/knife.rb:115:in `run' from /Library/Ruby/Gems/1.8/gems/chef-0.9.5/bin/knife:25 from /usr/bin/knife:19:in `load' from /usr/bin/knife:19
(where CLOUD TYPE is rackspace, ec2 or terremark)
Activity
- All
- Comments
- History
- Activity
- Transitions Summary
bulk updating fix versions to next release