[openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration
joehuang
joehuang at huawei.com
Tue Feb 23 02:15:27 UTC 2016
Hi, Yipei,
You can use “ps aux |grep python” to see processes started for OpenStack, and make sure services started successfully. And use “netstat -tulpn | grep :9696” to see which process is listening this port. Maybe your Neutron API has not started successfully.
Best Regards
Chaoyi Huang ( Joe Huang )
From: Yipei Niu [mailto:newypei at gmail.com]
Sent: Tuesday, February 23, 2016 10:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: joehuang; Vega Cai
Subject: Re: [tricircle] playing tricircle with devstack under two-region configuration
Hi Joe and Zhiyuan,
When creating network with AZ scheduler hints specified, I execute "curl -X POST http://127.0.0.1:9696/v2.0/networks -H "Content-Type: application/json" -H "X-Auth-Token: $token" -d '{"network": {"name": "net1", "admin_state_up": true, "availability_zone_hints": ["az1"]}}'". The results also indicate that
Failed to connect to 127.0.0.1 port 9696: Connection refused.
Unlike the error mentioned in last mail, I still cannot find any processor is listening on port 9696 after running "rejoin-stack.sh".
Best regards,
Yipei
On Mon, Feb 22, 2016 at 11:45 AM, Vega Cai <luckyvega.g at gmail.com<mailto:luckyvega.g at gmail.com>> wrote:
Hi Yipei,
One reason for that error is that the API service is down. You can run "rejoin-stack.sh" under your DevStack folder to enter the "screen" console of DevStack, to check if services are running well. If you are not familiar with "screen", which is a window manager for Linux, you can do a brief search.
One more thing you can try, change the IP address to 127.0.0.1 and issue the request in the machine hosting the services to see if there is still "Connection refused" error.
BR
Zhiyuan
On 20 February 2016 at 20:49, Yipei Niu <newypei at gmail.com<mailto:newypei at gmail.com>> wrote:
Hi Joe and Zhiyuan,
I encounter an error when executing the following command:
stack at nyp-VirtualBox:~/devstack$ curl -X POST http://192.168.56.101:19999/v1.0/pods -H "Content-Type: application/json" -H "X-Auth-Token: 0ead350329ef4b07ab3b823a9d37b724" -d '{"pod": {"pod_name": "RegionOne"}}'
curl: (7) Failed to connect to 192.168.56.101 port 19999: Connection refused
Before executing the command, I source the file "userrc_early", whose content is as follows:
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_URL=http://192.168.56.101:35357
export OS_USERNAME=admin
export OS_USER_DOMAIN_ID=default
export OS_PASSWORD=nypnyp0316
export OS_PROJECT_NAME=admin
export OS_PROJECT_DOMAIN_ID=default
export OS_REGION_NAME=RegionOne
Furthermore, the results of "openstack endpoint list" are as follows:
stack at nyp-VirtualBox:~/devstack$ openstack endpoint list
+----------------------------------+-----------+--------------+----------------+---------+-----------+------------------------------------------------+
| ID | Region | Service Name | Service Type | Enabled | Interface | URL |
+----------------------------------+-----------+--------------+----------------+---------+-----------+------------------------------------------------+
| 0702ff208f914910bf5c0e1b69ee73cc | RegionOne | nova_legacy | compute_legacy | True | internal | http://192.168.56.101:8774/v2/$(tenant_id)s |
| 07fe31211a234566a257e3388bba0393 | RegionOne | nova_legacy | compute_legacy | True | admin | http://192.168.56.101:8774/v2/$(tenant_id)s |
| 11cea2de9407459480a30b190e005a5c | Pod1 | neutron | network | True | internal | http://192.168.56.101:20001/ |
| 16c0d9f251d84af897dfdd8df60f76dd | Pod2 | nova_legacy | compute_legacy | True | admin | http://192.168.56.102:8774/v2/$(tenant_id)s |
| 184870e1e5df48629e8e1c7a13c050f8 | RegionOne | cinderv2 | volumev2 | True | public | http://192.168.56.101:19997/v2/$(tenant_id)s |
| 1a068f85aa12413582c4f4d256d276af | Pod2 | nova | compute | True | admin | http://192.168.56.102:8774/v2.1/$(tenant_id)s |
| 1b3799428309490bbce57043e87ac815 | RegionOne | cinder | volume | True | internal | http://192.168.56.101:8776/v1/$(tenant_id)s |
| 221d74877fdd4c03b9b9b7d752e30473 | Pod2 | neutron | network | True | internal | http://192.168.56.102:9696/ |
| 413de19152f04fc6b2b1f3a1e43fd8eb | Pod2 | cinderv2 | volumev2 | True | public | http://192.168.56.102:8776/v2/$(tenant_id)s |
| 42e1260ab0854f3f807dcd67b19cf671 | RegionOne | keystone | identity | True | admin | http://192.168.56.101:35357/v2.0 |
| 45e4ccd5e16a423e8cb9f59742acee27 | Pod1 | neutron | network | True | public | http://192.168.56.101:20001/ |
| 464dd469545b4eb49e53aa8dafc114bc | RegionOne | cinder | volume | True | admin | http://192.168.56.101:8776/v1/$(tenant_id)s |
| 47351cda93a54a2a9379b83c0eb445ca | Pod2 | neutron | network | True | admin | http://192.168.56.102:9696/ |
| 56d6f7641ee84ee58611621c4657e45d | Pod2 | nova_legacy | compute_legacy | True | internal | http://192.168.56.102:8774/v2/$(tenant_id)s |
| 57887a9d15164d6cb5b58d9342316cf7 | RegionOne | glance | image | True | internal | http://192.168.56.101:9292 |
| 5f2a4f69682941edbe54a85c45a5fe1b | Pod1 | cinderv2 | volumev2 | True | public | http://192.168.56.101:8776/v2/$(tenant_id)s |
| 6720806fe7e24a7c8335159013dba948 | Pod2 | cinderv2 | volumev2 | True | admin | http://192.168.56.102:8776/v2/$(tenant_id)s |
| 72e2726b55414d25928b4fc9925a06ed | RegionOne | nova_legacy | compute_legacy | True | public | http://192.168.56.101:8774/v2/$(tenant_id)s |
| 75163e97c3014a389ab56184f970908f | Pod2 | neutron | network | True | public | http://192.168.56.102:9696/ |
| 77b67589282e4776916ead802646de11 | Pod1 | nova | compute | True | internal | http://192.168.56.101:8774/v2.1/$(tenant_id)s |
| 789f3456899f4381aef850822c412436 | Pod2 | nova | compute | True | internal | http://192.168.56.102:8774/v2.1/$(tenant_id)s |
| 78da748f6fdc41e8b690acefec8e2838 | Pod1 | cinderv2 | volumev2 | True | internal | http://192.168.56.101:8776/v2/$(tenant_id)s |
| 844402eaacb24f0480aacf7bae9139ee | Pod1 | nova | compute | True | public | http://192.168.56.101:8774/v2.1/$(tenant_id)s |
| 854c00bb353548ad85e691278f74f51f | Pod1 | cinderv2 | volumev2 | True | admin | http://192.168.56.101:8776/v2/$(tenant_id)s |
| 8d1cd835e76b4f8d9ebb4c61526cb0b0 | Pod2 | cinderv2 | volumev2 | True | internal | http://192.168.56.102:8776/v2/$(tenant_id)s |
| 954fc0d2d5ab41cf84df8c00133013bc | RegionOne | tricircle | Cascading | True | public | http://192.168.56.101:19999/v1.0 |
| 981feb7ec05b4e7e854a95e6b6f08130 | RegionOne | cinder | volume | True | public | http://192.168.56.101:8776/v1/$(tenant_id)s |
| 9dd0d79fdd5e4901b77f372a48bb0480 | Pod2 | cinder | volume | True | admin | http://192.168.56.102:8776/v1/$(tenant_id)s |
| 9f082c47441f4155b7789b23e7e9df74 | RegionOne | nova | compute | True | internal | http://192.168.56.101:19998/v2.1/$(tenant_id)s |
| 9f7a8aeb2a7649a2a4ace4fa2b09ec20 | Pod2 | cinder | volume | True | internal | http://192.168.56.102:8776/v1/$(tenant_id)s |
| a1964711d7234735a680cb5f8c8c94fc | RegionOne | nova | compute | True | public | http://192.168.56.101:19998/v2.1/$(tenant_id)s |
| a78ede8acd494ce98b0f74fd740c7ab1 | Pod2 | nova | compute | True | public | http://192.168.56.102:8774/v2.1/$(tenant_id)s |
| ae95ee6b1661486e83fb2ba07a7eeaad | Pod1 | nova | compute | True | admin | http://192.168.56.101:8774/v2.1/$(tenant_id)s |
| af16acfbdd1647b38728d6902e68047f | RegionOne | tricircle | Cascading | True | admin | http://192.168.56.101:19999/v1.0 |
| afde6b08a898458ca0d9c38725b070da | RegionOne | cinderv2 | volumev2 | True | internal | http://192.168.56.101:19997/v2/$(tenant_id)s |
| bae25abb9e1d4ccbabb0b90fffd0b319 | RegionOne | keystone | identity | True | internal | http://192.168.56.101:5000/v2.0 |
| bae6bae8cd804340a9bbb7c2991f90b3 | RegionOne | neutron | network | True | public | http://192.168.56.101:9696/ |
| be103791473d4458b55ba1648628fbd5 | Pod2 | nova_legacy | compute_legacy | True | public | http://192.168.56.102:8774/v2/$(tenant_id)s |
| c444764bde164d6ea6dbdbcf4a66f7cc | Pod2 | cinder | volume | True | public | http://192.168.56.102:8776/v1/$(tenant_id)s |
| c885c5493b834461a0cc2bf2371c002e | RegionOne | neutron | network | True | internal | http://192.168.56.101:9696/ |
| c968a53b50c64d1ebe6d313f9b68543a | RegionOne | glance | image | True | admin | http://192.168.56.101:9292 |
| d2cff2e9381e4232bbd4a37e8512e0e2 | RegionOne | nova | compute | True | admin | http://192.168.56.101:19998/v2.1/$(tenant_id)s |
| e1c7990b7b374cf5aea1c89cda66a2f9 | RegionOne | cinderv2 | volumev2 | True | admin | http://192.168.56.101:19997/v2/$(tenant_id)s |
| e4a6391980024fb4bade7f8af4f1d5e3 | RegionOne | keystone | identity | True | public | http://192.168.56.101:5000/v2.0 |
| ec048e1ce4a04c14a78416a486a2efa2 | Pod1 | neutron | network | True | admin | http://192.168.56.101:20001/ |
| ec4e5d60973d4aaa88a5e48aff3ab10b | RegionOne | glance | image | True | public | http://192.168.56.101:9292 |
| eed887aa33d342cf9bdaa11a2cd8e8fa | RegionOne | neutron | network | True | admin | http://192.168.56.101:9696/ |
| f52daaa17e644c28b5f2a67c1b9321fd | RegionOne | tricircle | Cascading | True | internal | http://192.168.56.101:19999/v1.0 |
+----------------------------------+-----------+--------------+----------------+---------+-----------+------------------------------------------------+
Since current solution to fixing the bug of multi-region setting in devstack needs to be further verified, I am not sure whether the error is caused by the solution or not.
Best regards,
Yipei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160223/0353233c/attachment.html>
More information about the OpenStack-dev
mailing list