Ask Your Question
0

After adding new host, can't create instances there

asked 2015-06-17 22:34:32 -0500

sacha-m gravatar image

I installed RDO (Kilo, CentOS 7.1) in three hosts. One Controller, and the other two are running as Hypervisor. So far, so good.
Then, I was running short on computing power, so I add another compute node (CONFIG_COMPUTE_HOSTS=[New_node_IP] on the answer file), and now you can see it on the compute nodes list:

[root@mistral ~(keystone_admin)]# nova hypervisor-list

+----+----------------------------+-------+---------+
| ID | Hypervisor hostname        | State | Status  |
+----+----------------------------+-------+---------+
| 1  | oldserver1.mydomain.local  | up    | enabled |
| 2  | oldserver2.mydomain.local  | up    | enabled |
| 3  | newserver.mydomain.local   | up    | enabled |
+----+----------------------------+-------+---------+

After launching some new instances on Horizon, I figured out none of them were created on "newserver", So I decided to do it on the CLI:

[root@mistral ~(keystone_admin)]# nova boot --image a8818cdd-9737-4294-9e48-06f995c5b873 --flavor m1.small  --key_name "My Keys" --availability-zone nova:newserver.mydomain.local --nic net-id=9e1d4556-c396-4d29-8ddb-2267f6a6385e --poll prueba_a_mano3
+--------------------------------------+-----------------------------------------------+
| Property                             | Value                                         |
+--------------------------------------+-----------------------------------------------+
| OS-DCF:diskConfig                    | MANUAL                                        |
| OS-EXT-AZ:availability_zone          | nova                                          |
| OS-EXT-SRV-ATTR:host                 | -                                             |
| OS-EXT-SRV-ATTR:hypervisor_hostname  | -                                             |
| OS-EXT-SRV-ATTR:instance_name        | instance-00000034                             |
| OS-EXT-STS:power_state               | 0                                             |
| OS-EXT-STS:task_state                | scheduling                                    |
| OS-EXT-STS:vm_state                  | building                                      |
| OS-SRV-USG:launched_at               | -                                             |
| OS-SRV-USG:terminated_at             | -                                             |
| accessIPv4                           |                                               |
| accessIPv6                           |                                               |
| adminPass                            | 8qxAUARPBUgb                                  |
| config_drive                         |                                               |
| created                              | 2015-06-18T03:16:16Z                          |
| flavor                               | m1.small (2)                                  |
| hostId                               |                                               |
| id                                   | 17c2894c-a6f5-4888-8fea-f6494b193df1          |
| image                                | cirros (a8818cdd-9737-4294-9e48-06f995c5b873) |
| key_name                             | My Keys                                       |
| metadata                             | {}                                            |
| name                                 | prueba_a_mano3                                |
| os-extended-volumes:volumes_attached | []                                            |
| progress                             | 0                                             |
| security_groups                      | default                                       |
| status                               | BUILD                                         |
| tenant_id                            | 440d499bc96044b281bac8a4190a087d              |
| updated                              | 2015-06-18T03:16:16Z                          |
| user_id                              | ed62b6401ae64f278a1e7ec9478b6293              |
+--------------------------------------+-----------------------------------------------+

Server building... 0% complete
Error building server
ERROR (InstanceInErrorState): Build of instance 17c2894c-a6f5-4888-8fea-f6494b193df1 was re-scheduled: Image a8818cdd-9737-4294-9e48-06f995c5b873 could not be found.

If I run the same options, but using availability-zone nova:oldserver1.mydomain.local or oldserver2, works perfectly. It seems as "newserver" can't see glances images or something. Any ideas on this?

edit retag flag offensive close merge delete

Comments

1

is there any difference between nova.conf(oldserver1.mydomain.local) and nova.conf(newserver.mydomain.local) related to glance ?

Ranjit gravatar imageRanjit ( 2015-06-18 03:50:24 -0500 )edit

There was one difference: api_servers, which is used to connect with glance. It appeared newserver's IP instead of Controller's. Why? Because I enabled unsupported parameters (CONFIG_UNSUPPORTED) with CONFIG_STORAGE_HOST. I needed cinder, but this option also installs cinder. Now it's working.

sacha-m gravatar imagesacha-m ( 2015-06-18 15:41:30 -0500 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2015-06-18 15:52:40 -0500

sacha-m gravatar image

The problem was I used unsupported parameters on RDO answer file:

CONFIG_UNSUPPORTED=y

And then:

# (Unsupported!) IP address of the server on which to install
# OpenStack services specific to storage servers such as Image or
# Block Storage services.
CONFIG_STORAGE_HOST=[Newserver_IP]

This worked fine, because I needed to have Cinder on "newserver", but I didn't want/need Glance, and as appears there, this CONFIG_STORAGE_HOST option is for both services.
So, thanks to @ranjit´s tip, I found the problem. In "newserver", /etc/nova/nova.conf appeared:

# A list of the glance api servers available to nova. Prefix
# with https:// for ssl-based glance api servers.
# ([hostname|ip]:port) (list value)
#api_servers=<None>
api_servers=[Newserver_IP]:9292

There should appear Controller's IP. So, I changed that, to Controller's IP, restart nova services, and worked fine.
I know this is an unsupported option in this version, but when it will come supported, I'd suggest to separate Image and Block Storage parameters on the answer file.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-06-17 22:34:32 -0500

Seen: 664 times

Last updated: Jun 18 '15