Ask Your Question

Sauskekan's profile - activity

2017-01-25 23:10:08 -0600 received badge  Famous Question (source)
2016-06-25 16:29:20 -0600 received badge  Enthusiast
2016-06-13 01:51:41 -0600 received badge  Popular Question (source)
2016-06-11 18:21:58 -0600 asked a question After Installing Cinder both neutron and nova are not appearing in the controller

Everything was working fine in my kilo OpenStack environment till I installed the cinder service both Neutron and Nova are not appearing in the controller even though both services in their logs are saying "Connected to AMQP server on controller:5672" , is there any bugs known with the Cinder. Below are the output from the controller:

root@controller:/# neutron agent-list +--------------------------------------+--------------------+---------+-------+----------------+---------------------------+ | id | agent_type | host | alive | admin_state_up | binary | +--------------------------------------+--------------------+---------+-------+----------------+---------------------------+ | 2386262f-00b6-4241-9eb9-f5b07e53b340 | Open vSwitch agent | compute | xxx | True | neutron-openvswitch-agent | | 60485583-8158-46a5-a966-0036ada0c2cb | DHCP agent | network | xxx | True | neutron-dhcp-agent | | 8a7b7077-1015-4667-84ac-20575cdd90f6 | Metadata agent | network | xxx | True | neutron-metadata-agent | | b772ff56-94b2-4d54-af72-acc29880bcb6 | L3 agent | network | xxx | True | neutron-l3-agent | | fc02d012-a27d-4190-92f8-0262626eca7f | Open vSwitch agent | network | xxx | True | neutron-openvswitch-agent | +--------------------------------------+--------------------+---------+-------+----------------+---------------------------+ root@controller:/# nova service-list +----+------------------+------------+----------+---------+-------+----------------------------+-----------------+ | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | +----+------------------+------------+----------+---------+-------+----------------------------+-----------------+ | 1 | nova-cert | controller | internal | enabled | up | 2016-06-11T23:20:45.000000 | - | | 2 | nova-consoleauth | controller | internal | enabled | up | 2016-06-11T23:20:44.000000 | - | | 3 | nova-scheduler | controller | internal | enabled | up | 2016-06-11T23:20:45.000000 | - | | 4 | nova-conductor | controller | internal | enabled | up | 2016-06-11T23:20:45.000000 | - | | 5 | nova-compute | compute | nova | enabled | down | 2016-06-11T13:16:28.000000 | - | +----+------------------+------------+----------+---------+-------+----------------------------+-----------------+

2016-06-02 15:00:13 -0600 received badge  Notable Question (source)
2016-06-02 15:00:13 -0600 received badge  Popular Question (source)
2016-04-28 16:15:19 -0600 commented answer My first VM machine is not booting up

The only ERROR that i can see is in the nova-api log:ECONNREFUSED. Trying again in 2 seconds. 2016-04-26 09:29:38.652 1004 ERROR oslo_messaging._drivers.impl_rabbit [-] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.

Would you please help

2016-04-28 16:13:53 -0600 answered a question My first VM machine is not booting up

Thanks for the reply but the only ERROR that can i see in the nova-api log is ECONNREFUSED. Trying again in 2 seconds. 2016-04-26 09:29:38.652 1004 ERROR oslo_messaging._drivers.impl_rabbit [-] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.

despite the port is open and no firewall between the nodes. Would you please help.

2016-04-28 15:26:51 -0600 answered a question My first VM machine is not booting up

I am doing the provider network configuration with Linux bridge, no openv switch, and one more thing to mention that the file Linuxbridge.agent.ini is not exist despite the package is installed.

2016-04-28 14:09:59 -0600 asked a question My first VM machine is not booting up

I did follow the Kilo installation steps as it's written, My environment is very simple i Have one Controller node (Keystone,Glance,Horizon,Neutron) and one compute Node (nova-Compute) ,all the servers are working fine:

[root@controller nova]# neutron agent-list
+--------------------------------------+--------------------+------------+-------+----------------+---------------------------+
| id                                   | agent_type         | host       | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+------------+-------+----------------+---------------------------+
| 29b58e99-0db2-4f21-86d7-dee99b2d5ac7 | Linux bridge agent | controller | :-)   | True           | neutron-linuxbridge-agent |
| 3a519085-fedc-49fd-91ba-5cf4c873423e | Linux bridge agent | compute    | :-)   | True           | neutron-linuxbridge-agent |
| 5996325e-1f99-4381-b374-5604d12d33a4 | Metadata agent     | controller | :-)   | True           | neutron-metadata-agent    |
| dded77cc-c21a-46b3-bc3b-63d0b729d683 | DHCP agent         | controller | :-)   | True           | neutron-dhcp-agent        |
+--------------------------------------+--------------------+------------+-------+----------------+---------------------------+
[root@controller nova]# nova service-list
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host       | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| 1  | nova-consoleauth | controller | internal | enabled | up    | 2016-04-27T12:29:44.000000 | -               |
| 2  | nova-conductor   | controller | internal | enabled | up    | 2016-04-27T12:29:43.000000 | -               |
| 3  | nova-scheduler   | controller | internal | enabled | up    | 2016-04-27T12:29:43.000000 | -               |
| 4  | nova-cert        | controller | internal | enabled | up    | 2016-04-27T12:29:44.000000 | -               |
| 5  | nova-compute     | compute    | nova     | enabled | up    | 2016-04-27T12:29:49.000000 | -               |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
[root@controller nova]# nova image-list
+--------------------------------------+---------------------+--------+--------+
| ID                                   | Name                | Status | Server |
+--------------------------------------+---------------------+--------+--------+
| d791ed49-f300-4d8f-9528-e1c26fb44780 | cirros-0.3.4-x86_64 | ACTIVE |        |
+--------------------------------------+---------------------+--------+--------+

But whenever I run the command to boot the VM it's keeps failing with the below error:

ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-fe8b54f1-96ea-4c35-8e77-62425ace064c)

If run the command without putting the nic option , the command will complete successfully but the machine will remain at the error state. I am using Centos 7.

Can anyone help with this.