Openstack stop working after hosts reboot

Tue Mar 17 19:25:22 UTC 2015

After some struggle (http://askubuntu.com/questions/596404/computers-not-reporting-to-landscape), Landscape is working fine and is managing hosts without problems.

In the other hand, on Openstack Dashboard I'm getting all kind of error messages like "Unable to delete volume snapshot: test snapshot", "Can't find floating IP", etc.

Now I can start instances, but they are not reacheable at all.

My instances have an internal IP (part of the called "Admin_Net", 10.10.0.0/16), and have associated a floating IP (part of the called "ext_net", 10.222.221.0/24).

The Router inside Openstack that connects both networks is called "admin_router" and has IPs 10.10.0.1 (internal) and 10.222.221.2 (external).

Before I move my servers physically, I was able to reach everyithing. Now, I can't.

If I launch an instance, and associate to that instance a floating IP, let's say 10.222.221.10, I can't reach it.

My guess was there is some wire problem, so I went to my Landscape environment's bootstrap, called Balaguera (Physical server, IP 10.222.221.82 on the juju-br0 interface), I double check the cables on the NICs, both wires seemed to be OK, connected to the correct switch and everything.

I'm running out of ideas on what could be the problem.

PS: The good news is now I can attach and detach existin volumes to existing instances. I still can't launch new instances. Actually, What I see when I try to launch a new instance, is the availability zone is "nova" instead of the one are all the others: "region1-1".

Ps2: after writing rhis email, I remember to run the command you, Adam, told me to run:

stockachu at mistral:~$ JUJU_HOME=~/.cloud-install/ juju run --service landscape,landscape-msg 'sudo lsctl restart'

- Error: command timed out

  MachineId: 0/lxc/2

  Stderr: "Warning: Permanently added '10.222.221.140' (ECDSA) to the list of known

    hosts.\r\n"

  Stdout: ""

  UnitId: landscape/0

- MachineId: 0/lxc/3

  Stderr: "Warning: Permanently added '10.222.221.141' (ECDSA) to the list of known

    hosts.\r\nsudo: unable to resolve host juju-machine-0-lxc-3\n"

  Stdout: "== landscape-combo-loader ==\n... Not enabled, skipping.\n== landscape-appserver

    ==\n... Not enabled, skipping.\n== landscape-async-frontend ==\n... Not enabled,

    skipping.\n== landscape-job-handler ==\n... Not enabled, skipping.\n== landscape-msgserver

    ==\n * Checking database schema\n   ...done.\n * Restarting Landscape standalone

    message-server 1\n   ...done.\n * Restarting Landscape standalone message-server

    2\n   ...done.\n== landscape-pingserver ==\n... Not enabled, skipping.\n== landscape-api

    ==\n... Not enabled, skipping.\n== landscape-juju-sync ==\n... Not enabled, skipping.\n==

    landscape-package-upload ==\n... Not enabled, skipping.\n== landscape-package-search

    ==\n... Not enabled, skipping.\n"

  UnitId: landscape-msg/0

And now, If I go to "openstack" section in Landscape, it says "Installing region1 in nube_akainix" and some hook failed: "config-changed" errors (that's on the GUI). The only option I see is to abort the installation, but I don't want to do it. I don't know if there is going to uninstall what was deployed before...

From: Sacha Yunusic 
Sent: lunes, 16 de marzo de 2015 11:51
To: 'ubuntu-openstack-installer at lists.ubuntu.com'
Subject: RE: Openstack stop working after hosts reboot

Adam, 

My answers:

> Another thing to try is reconfiguring neutron networks from within the

> landscape ui. It could be since you switched

> networks that landscape has incorrect networking information

I changed phyisically the servers, not logically. They are in the same netwrork than before. Same IP's , same switches, same everything. The only difference, is now they are in a different building.

Regarding restart services, I'll do it after solving an issue I detect between Landscape and the hosts are being managed by it, as I post here: https://askubuntu.com/questions/596404/computers-not-reporting-to-landscape.

I'll send an email after solving that issue, and update on how this problem goes, because my guess is they are related.

Thanks!

Sacha Yunusic | Gerente Técnico | Pentagon Security & Akainix

Av. Presidente Kennedy 4700 of 1002 - Vitacura | CP (ZIP Code) 7561127 

Central: (56-2) 2246 1050 | Directo: (56-2) 2246 2620 | Cel: (56-99) 883 4752 | www.penta-sec.com <http://www.penta-sec.com/>  & www.akainix.com <http://www.akainix.com/> 

From: Sacha Yunusic 
Sent: viernes, 13 de marzo de 2015 13:04
To: 'ubuntu-openstack-installer at lists.ubuntu.com'
Subject: Openstack stop working after hosts reboot

Hi everyone, 

I'm the new guy here.

About two months ago I installed Openstack using the openstack-installer with autopilot.

There are two juju's environments: "maas" and "8". Maas is the first one, when Landscape is installed. The second one, called "8" is the one that has Openstack and it is launched from the server (container in my case) that Landscape is installed.

The "maas" environment's bootstrap is a Virtual Machine, which is the one that comes with the openstack-installer package. That VM has six containers. One of them, has Landscape (0/lxc/2).

>From there it uses physical hosts, for the "8" environment.

Once everything is running, it's all good. I can launch instances, I can attach volumes, etc.

The problem is when I had to shut down everything, due I had to physically move my servers.

After turn'em on, after some struggles with juju-core versions (more info at https://askubuntu.com/questions/596004/landscape-is-not-running-after-a-reboot-with-juju-core-1-20-x), I made it run. Both environments ("maas" and "8").

I was able to enter to Openstack dashboard and also Landscape, but two weird thing happened:

1.- hosts were not reporting to Landscape

2.- I was not able to launch new instances, nor create new volumes, nor delete them, nor backup volumes, etc. 

I'm ok with reinstalling everything, but I need to recover the data is on those volumes, due it's production data.

Any guess? Please help.

Sacha Yunusic | Gerente Técnico | Pentagon Security & Akainix

Av. Presidente Riesco 5335, Of. 605, Las Condes | CP (ZIP Code) 7561127 

Central: (56-2) 2246 1050 | Directo: (56-2) 2246 2620 | Cel: (56-99) 883 4752 | www.penta-sec.com <http://www.penta-sec.com/>  & www.akainix.com <http://www.akainix.com/> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-openstack-installer/attachments/20150317/37b7cc1e/attachment-0001.html>