Ask Your Question
0

horizon Associate Floating IP to an instance in error state

asked 2015-05-18 01:03:33 -0500

Ritesh Paiboina gravatar image

Hi, I have launched the an instance through horizon and it went to ERROR state, due to No valid host was found : Insufficient Resources : No enough hosts available.

When the instances is not able to launch, the instance statue is changed to ERROR state and the tables actions are visible. In the tables actions, I can see that you can associate or dis-associate a floating IP to the ERROR state instance.

What is the use case of keep those two actions association and disassociation of floating IP to the instance in ERROR state ?

edit retag flag offensive close merge delete
add a comment

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-05-18 02:09:11 -0500

lhinds gravatar image

updated 2015-05-18 02:10:56 -0500

Depends on the error state. Did you take a look at /var/log/nova/* or /var/log/horizo/horion.log.

Even though a machine may have an error state, it might still have a working interface to plumb an ip too.

At a guess, if its a kernel panic or something of a total failure, then you could look to raise it as a bug.

edit flag offensive delete link more

Comments

Hi Luke, As my current error state is because of "Insufficient resources like I don't have RAM and vCPU" Do you mean to say that if an Instance is failed because of some internal errors, at that time we can attach a floating IP and debug/work on it ?

Ritesh Paiboina gravatar imageRitesh Paiboina ( 2015-05-18 02:21:44 -0500 )edit

IMHO , as an error instance cannot be re-launched, it is not worth to assign a IP. Though other current action such edit instance , lock / unlock might be helpful.

Ritesh Paiboina gravatar imageRitesh Paiboina ( 2015-05-18 02:25:00 -0500 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2015-05-18 01:03:33 -0500

Seen: 300 times

Last updated: May 18 '15

Related questions

Router not routing between internal and external network in openstack

floating ip management

Exception tuples

dashboard error 500 on install

how to associate floating point IP with VM

Can not associate the floating ip to instance

Juno unable to retrieve instance list

Horizon : error 500

Can't Resolve nova-api Error

Horizon: Networks with nova-network