Skip to main content

Re: [Openstack] [TACKER] VIM STATUS PENDING IN OPENSTACK ROCKY

Hi, from the logs I think is something missing in mistral executor images from tacker.

What distribution and install type are you using, latest kolla and kolla ansible from git?

Regards

On Thu, Aug 30, 2018, 5:09 PM pablo brunetti <pablobrunetti@hotmail.com> wrote:

Hi,


I installed OpenStack Rocky Multinode with Kolla-Ansible. In the Tacker module, I am having trouble creating the VIM, the status is pending and the VNFFG does not work because of this. I've activated all the modules that Tacker needs (Barbican, Mistral, Networking-SFC, Ceilometer, Heat).


Has anyone had this problem yet?


VIM0
70e75906-d9d5-42b1-9835-65bab0c23671      False http://192.168.0.64:5000/v3     RegionOne      admin        admin     PENDING        openstack


LOGS:

TACKER-SERVER


2018-08-30 11:45:10.611 27 INFO tacker.wsgi [req-7c57c13c-e480-462f-9b1a-5a239c671e8f d096a0e324274a8abf8c326f6ac9e9a5 8a11667d9ac8477eb5ac50f4020add81 - - -] 192.168.0.64 - - [30/Aug/2018 11:45:10] "GET /v1.0/vnfds.json?template_source=onboarded HTTP/1.1" 200 211 0.010963
2018-08-30 11:45:12.827 41 INFO tacker.wsgi [req-8daf5c47-de62-4a1e-ab5d-a2abb062965b d096a0e324274a8abf8c326f6ac9e9a5 8a11667d9ac8477eb5ac50f4020add81 - - -] 192.168.0.64 - - [30/Aug/2018 11:45:12] "GET /v1.0/vims.json HTTP/1.1" 200 899 0.118279

MISTRAL-ENGINE

2018-08-30 11:45:01.852 8 INFO workflow_trace [req-90f08fff-96a7-4d2a-9c57-1c2f9f9f408c d096a0e324274a8abf8c326f6ac9e9a5 8a11667d9ac8477eb5ac50f4020add81 - default default] Task 'monitor_ping_vimPingVIMTASK' (caebddf1-7c1c-414f-9e9d-4f8de15349e0) [RUNNING -> SUCCESS, msg=None] (execution_id=2780e3eb-2862-4d5f-9990-343fceeecd3d)
2018-08-30 11:45:02.719 8 INFO workflow_trace [req-9f001438-bb30-4f35-b448-1fa4a57e23c8 - - - - -] Workflow 'vim_id_70e75906-d9d5-42b1-9835-65bab0c23671' [RUNNING -> SUCCESS, msg=None] (execution_id=2780e3eb-2862-4d5f-9990-343fceeecd3d)

MISTRAL-SERVER

2018-08-30 11:44:37.898 24 WARNING oslo_db.sqlalchemy.utils [req-06cf535b-b8a5-475c-b758-c8496d0ae48e d096a0e324274a8abf8c326f6ac9e9a5 8a11667d9ac8477eb5ac50f4020add81 - default default] Unique keys not in sort_keys. The sorting order may be unstable.

MISTRAL-EXECUTOR

2018-08-30 11:45:01.268 8 INFO mistral.executors.executor_server [req-90f08fff-96a7-4d2a-9c57-1c2f9f9f408c d096a0e324274a8abf8c326f6ac9e9a5 8a11667d9ac8477eb5ac50f4020add81 - default default] Received RPC request 'run_action'[action_ex_id=b9f18b10-b4ae-49a4-bd94-4233a2a625c7, action_cls_str=tacker.nfvo.workflows.vim_monitor.vim_ping_action.PingVimAction, action_cls_attrs={}, params={count: 1, targetip: 192.168.0.64, vim_id: 70e75906-d9d5-42b1-9835-65bab0c23671, interval: 1, tim..., timeout=None]
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action [req-90f08fff-96a7-4d2a-9c57-1c2f9f9f408c d096a0e324274a8abf8c326f6ac9e9a5 8a11667d9ac8477eb5ac50f4020add81 - default default] failed to run mistral action for vim 70e75906-d9d5-42b1-9835-65bab0c23671: OSError: [Errno 2] No such file or directory
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action Traceback (most recent call last):
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/tacker/nfvo/workflows/vim_monitor/vim_ping_action.py", line 88, in run
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     status = self._ping()
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/tacker/nfvo/workflows/vim_monitor/vim_ping_action.py", line 60, in _ping
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     debuglog=False)
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/tacker/agent/linux/utils.py", line 66, in execute
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     addl_env=addl_env, debuglog=debuglog)
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/tacker/agent/linux/utils.py", line 55, in create_process
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     env=env)
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/tacker/common/utils.py", line 128, in subprocess_popen
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     close_fds=True, env=env)
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/eventlet/green/subprocess.py", line 55, in __init__
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     subprocess_orig.Popen.__init__(self, args, 0, *argss, **kwds)
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/usr/lib/python2.7/subprocess.py", line 394, in __init__
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     errread, errwrite)
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action   File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action     raise child_exception
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action OSError: [Errno 2] No such file or directory
2018-08-30 11:45:01.832 8 ERROR tacker.nfvo.workflows.vim_monitor.vim_ping_action




Thanks.




_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Comments

Post a Comment

Popular posts from this blog

[Openstack] [Nova] Instance creation problem

Hi. I'm setting up a Openstack system on the servers of my laboratory. While I try to create an instance, a problem has occurred! Instance creation was failed and it seems that libvirt failed to attaching the vif to the instance. When I create a virtual machine by using virsh tool (libvirt) manually, there was no problem. I add the logs as follows: 1. controller node "/var/log/nova/nova-conductor.log" 2018-11-28 21:18:13.033 2657 ERROR nova.scheduler.utils [req-291fdb2d-fa94-461c-9f5f-68d340791c77 3367829d9c004653bdc9102443bd4736 47270e4fb58045dc88b6f0f736286ffc - default default] [instance: 9c2d08f3-0680-4709-a64d-ae1729a11304] Error from last host: node1 (node node1): [u'Traceback (most recent call last):\n', u'  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1840, in _do_build_and_run_instance\n    filter_properties, request_spec)\n', u'  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line
Post a Comment
Read more

Re: [Openstack] OpenStack Queens Manual Installation

Hello Kevin, In installation of the Keystone OpenStack Queens the port 35357 is deprecated and should be replaced by port 5000 . ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357 Review the entire Neutron installation, replacing port 35357 with 5000. I suggest deleting the database and popular again. I made a notification on bugs.launchpad, but was flagged as invalid, stating that the problem has already been fixed. https://bugs.launchpad.net/neutron/+bug/1773585 Best Regards. De: Kevin Kwon <poby1972@gmail.com> Enviado: sábado, 16 de junho de 2018 11:30 Para: openstack@lists.openstack.org Assunto: [Openstack] OpenStack Queens Manual Installation   Dear All! Hi.. Would you please help to install the Openstack on Ubunto 16.04.4 Server manually. I have installed the Keystone, Glance and Nova with One Controller Node and One Compute node with Installatio
Post a Comment
Read more

Re: [Openstack] Not able to use openstack swift using the s3 api plugin...

Hello Shyam, I did not have so much experience with s3curl but it looks like the problem is caused by client but it seems like the s3token middleware, which is to get authentication with keystone. So let us check "What authentication are you using", then check "your exisiting configuration". That seems a way to go. And more, if you could change the reference from https://docs.openstack.org/mitaka/config-reference/object-storage/configure-s3.html , please consider if you would refer the newest docs at the master of swift3 repository, https://github.com/openstack/swift3 . That is because OpenStack mitaka was approximately 2 years ago and some of the docs looks weird to me. (e.g. recommend swauth by default in the pipeline config) If you could follow up the Swift upstream, the good news is that swift3 got merged as "s3api" to the Swift upstream repository in recent, https://github.com/openstack/swift/commit/636b922f3b2882f7dd6c656983d7862b274dcf98 . So you ma
Post a Comment
Read more