Ask Your Question

HARestarter deletes the instance and while creating give Port ID error

asked 2014-06-17 05:47:12 -0500

Jay Mehta gravatar image

updated 2014-06-17 05:49:23 -0500

Hi All,

I am trying to use HARestarter for HeartBeat monitoring of VM.

I have 2 problems: 1. The Alarm is triggered even if the VM is up and running. (Alarm should be triggered only if the VM is down). Why is this behaviour and what should my alarm be like to make it work only if VM goes down? 2. When the alarm is fired, HARestart deletes the existing image and tries creating a new one. But while creation of new one, it throws error on Port ID not found and it stucks there.

I am not sure what needs to be done. Can anyone help on this? I need urgent reply on this.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2014-06-18 00:59:29 -0500

Jay Mehta gravatar image

Can somebody please let me know how to handle HA?

edit flag offensive delete link more

answered 2014-07-02 04:19:36 -0500

erivni gravatar image

I have the same 2 problems. I managed to solve the second one by configuring the port's details inside the Nova::Server itself as follow:

server: type: OS::Nova::Server properties: name: restart_instance flavor: { get_param: flavor } image: { get_param: image } key_name: { get_param: key_name } availability_zone: { get_param: availability_zone } networks: - network: { get_param: network_id } security_groups: - { get_param: security_group_id } user_data: | #!/bin/bash -x touch /root/test echo "Hello, World!" > /root/test

Unfortunatly, I couldn't found a solution to the first problem, my instance is constantly being restarted


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2014-06-17 05:47:12 -0500

Seen: 137 times

Last updated: Jul 02 '14