We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I get this error when running following command :
knife openstack server create -f 3 --image e60659e8-ec3b-4074-acde-2a545bf9a76d -S pertest2 -N ct11 --ssh-user ubuntu --bootstrap-network nova_fixed --identity-file ~/Downloads/pertest2.pem -c ~/.chef/knife-test.rb --network-id 2d0edb26-479c-4d07-a391-5876efafc818 -a 10.1.1.225
ERROR: You have either requested an invalid floating IP address or none are available.
If I run above without -a option it works and the VM gets 10.1.1.225 ip assigned.
Any idea why this is happening ?
The text was updated successfully, but these errors were encountered:
are you running nova-networking or neutron?
Sorry, something went wrong.
Neutron
Sent from my iPhone
On Nov 18, 2014, at 6:24 PM, JJ Asghar [email protected] wrote: are you running nova-networking or neutron? — Reply to this email directly or view it on GitHub.
On Nov 18, 2014, at 6:24 PM, JJ Asghar [email protected] wrote:
— Reply to this email directly or view it on GitHub.
You probably didnt have any floating IPs assigned to your account. Please update the gem and see if this is still an issue. If it is please reopen.
No branches or pull requests
I get this error when running following command :
knife openstack server create -f 3 --image e60659e8-ec3b-4074-acde-2a545bf9a76d -S pertest2 -N ct11 --ssh-user ubuntu --bootstrap-network nova_fixed --identity-file ~/Downloads/pertest2.pem -c ~/.chef/knife-test.rb --network-id 2d0edb26-479c-4d07-a391-5876efafc818 -a 10.1.1.225
ERROR: You have either requested an invalid floating IP address or none are available.
If I run above without -a option it works and the VM gets 10.1.1.225 ip assigned.
Any idea why this is happening ?
The text was updated successfully, but these errors were encountered: