Ask Your Question

vblando's profile - activity

2019-09-21 13:12:27 -0500 asked a question [kolla] horizon menus not working

Release: Stein

Versions

[root@controller1 ~]# pip show kolla-ansible
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Name: kolla-ansible
Version: 8.0.0
Summary: Ansible Deployment of Kolla containers
Home-page: https://docs.openstack.org/kolla-ansible/latest/
Author: OpenStack
Author-email: openstack-discuss@lists.openstack.org
License: Apache License, Version 2.0
Location: /usr/lib/python2.7/site-packages
Requires: cryptography, setuptools, jmespath, oslo.utils, Jinja2, PyYAML, netaddr, docker, six, oslo.config, pbr
Required-by:
[root@controller1 ~]#
[root@controller1 ~]# pip --version
pip 19.2.1 from /usr/lib/python2.7/site-packages/pip (python 2.7)
[root@controller1 ~]#
[root@controller1 ~]# ansible --version
ansible 2.8.3
  config file = None
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Jun 20 2019, 20:27:34) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
[root@controller1 ~]#
[root@controller1 ~]# docker --version
Docker version 19.03.1, build 74b1e89
[root@controller1 ~]#

I have experienced this for quite some time now when suddenly menus on horizon are not working, I have no custom configs and no modifications whatsoever. The only solution that I have found is to redeploy horizon by stopping and deleting the container image and redeploy, but then again it will stop working again and I have to redeploy again.

Here's what it says on the logs when I try to click on a menu (ex. LAUNCH INSTANCE).

[Sun Sep 22 01:57:03.740925 2019] [:error] [pid 58]   <script type='text/javascript' id='/static/framework/widgets/wizard/wizard.html'>
[Sun Sep 22 01:57:03.740930 2019] [:error] [pid 58]
[Sun Sep 22 01:57:03.740934 2019] [:error] [pid 58]
[Sun Sep 22 01:57:03.740941 2019] [:error] [pid 58] angular
[Sun Sep 22 01:57:03.740945 2019] [:error] [pid 58]  .module('horizon.app')
[Sun Sep 22 01:57:03.740950 2019] [:error] [pid 58]  .run(['$templateCache', function($templateCache) {
[Sun Sep 22 01:57:03.740954 2019] [:error] [pid 58]    $templateCache.put(
[Sun Sep 22 01:57:03.740959 2019] [:error] [pid 58]      "/static/framework/widgets/wizard/wizard.html",
[Sun Sep 22 01:57:03.740967 2019] [:error] [pid 58]      "<div class=\\"ng-wizard\\" ng-form=\\"wizardForm\\">\\n  <div class=\\"modal-header\\">\\n    <button type=\\"button\\" class=\\"close\\" ng-click=\\"cancel()\\" aria-hidden=\\"true\\" aria-label=\\"Close\\">\\n      <span aria-hidden=\\"true\\" class=\\"fa fa-close\\"></span>\\n    </button>\\n    <span class=\\"h4 modal-title\\" ng-bind=\\"::workflow.title\\"></span>\\n  </div>\\n\\n  <div class=\\"modal-body\\">\\n\\n  <div class=\\"alert alert-danger error-message\\" ng-show=\\"viewModel.hasError\\" ng-bind=\\"viewModel.errorMessage\\"></div>\\n\\n    <div class=\\"row\\">\\n      <div class=\\"col-xs-12 col-sm-3 ...
(more)
2019-09-18 14:17:57 -0500 received badge  Famous Question (source)
2019-08-30 03:26:53 -0500 received badge  Notable Question (source)
2019-08-30 03:26:53 -0500 received badge  Popular Question (source)
2019-08-25 13:36:01 -0500 commented question Why is it that CirrOS instances connect, but others don't?

Maybe it's not the image or instance, maybe it's your network, how did you set it up? What type, self service or provider network?, Is it flat, vxlan/vlan, gre?

2019-08-21 11:50:51 -0500 answered a question TASK [keystone : Creating the Keystone service and endpoint] failure

I was able to deploy on a fresh installation, nothing was changed so I don't know where the issue lies. It's running smoothly for a couple of weeks now.

2019-08-13 14:16:56 -0500 received badge  Famous Question (source)
2019-08-08 09:20:26 -0500 received badge  Popular Question (source)
2019-08-08 09:20:26 -0500 received badge  Notable Question (source)
2019-08-06 23:48:02 -0500 commented question TASK [keystone : Creating the Keystone service and endpoint] failure

the 3 keystone containers (keystone-fernet, keystone-ssh, keystone) are running fine though, no error on their logs

2019-08-06 23:38:03 -0500 commented question TASK [keystone : Creating the Keystone service and endpoint] failure

I reinstalled the OS of the controller and tried to deploy again, same issue, I have sufficient memory

this is what I go on the logs http://paste.openstack.org/show/755596/

2019-08-06 04:05:32 -0500 asked a question TASK [keystone : Creating the Keystone service and endpoint] failure

OS: CentOS 7 Ansible version: 2.8.3 Kolla-Ansible version: 8.0.0

globals.yml

kolla_base_distro: "centos"
kolla_install_type: "source"
openstack_release: "stein"

I already tried redeploying on a fresh installed nodes but this error keeps on happening.

deploy error

TASK [keystone : Creating the Keystone service and endpoint] ****************************************************************************************************************************************
failed: [controller1] (item={u'interface': u'admin', u'url': u'http://172.30.20.250:35357'}) => {"ansible_loop_var": "item", "changed": true, "item": {"interface": "admin", "url": "http://172.30.20.250:35357"}, "msg": "'Traceback (most recent call last):\\n  File \"/tmp/ansible_YVCYGA/ansible_module_kolla_keystone_service.py\", line 58, in main\\n    for _service in cloud.keystone_client.services.list():\\n  File \"/opt/ansible/lib/python2.7/site-packages/shade/_legacy_clients.py\", line 95, in keystone_client\\n    self._identity_client\\n  File \"/opt/ansible/lib/python2.7/site-packages/shade/openstackcloud.py\", line 616, in _identity_client\\n    \\'identity\\', min_version=2, max_version=\\'3.latest\\')\\n  File \"/opt/ansible/lib/python2.7/site-packages/shade/openstackcloud.py\", line 506, in _get_versioned_client\\n    if adapter.get_endpoint():\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/adapter.py\", line 271, in get_endpoint\\n    return self.session.get_endpoint(auth or self.auth, **kwargs)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/session.py\", line 1158, in get_endpoint\\n    return auth.get_endpoint(self, **kwargs)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/identity/base.py\", line 380, in get_endpoint\\n    allow_version_hack=allow_version_hack, **kwargs)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/identity/base.py\", line 271, in get_endpoint_data\\n    service_catalog = self.get_access(session).service_catalog\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/identity/base.py\", line 134, in get_access\\n    self.auth_ref = self.get_auth_ref(session)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/identity/generic/base.py\", line 208, in get_auth_ref\\n    return self._plugin.get_auth_ref(session, **kwargs)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/identity/v3/base.py\", line 178, in get_auth_ref\\n    authenticated=False, log=False, **rkwargs)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/session.py\", line 1064, in post\\n    return self.request(url, \\'POST\\', **kwargs)\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/session.py\", line 903, in request\\n    raise exceptions.from_response(resp, method, url)\\nInternalServerError: Internal Server Error (HTTP 500)\\n'"}
failed: [controller1] (item={u'interface': u'internal', u'url': u'http://172.30.20.250:5000'}) => {"ansible_loop_var": "item", "changed": true, "item": {"interface": "internal", "url": "http://172.30.20.250:5000"}, "msg": "'Traceback (most recent call last):\\n  File \"/tmp/ansible_icI3pI/ansible_module_kolla_keystone_service.py\", line 58, in main\\n    for _service in cloud.keystone_client.services.list():\\n  File \"/opt/ansible/lib/python2.7/site-packages/shade/_legacy_clients.py\", line 95, in keystone_client\\n    self._identity_client\\n  File \"/opt/ansible/lib/python2.7/site-packages/shade/openstackcloud.py\", line 616, in _identity_client\\n    \\'identity\\', min_version=2, max_version=\\'3.latest\\')\\n  File \"/opt/ansible/lib/python2.7/site-packages/shade/openstackcloud.py\", line 506, in _get_versioned_client\\n    if adapter.get_endpoint():\\n  File \"/opt/ansible/lib/python2.7/site-packages/keystoneauth1/adapter.py\", line 271, in get_endpoint\\n    return self.session.get_endpoint ...
(more)
2019-08-05 12:19:05 -0500 received badge  Taxonomist
2019-07-26 20:36:44 -0500 received badge  Famous Question (source)
2019-07-01 05:41:20 -0500 answered a question Unable to Pull Kuryr Docker image

This is fixed already. Need to deploy via "source" instead of "binary".

2019-06-30 22:27:11 -0500 asked a question Unable to Pull Kuryr Docker image

# pip show kolla-ansible

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Name: kolla-ansible
Version: 7.1.1
Summary: Ansible Deployment of Kolla containers
Home-page: https://docs.openstack.org/kolla-ansible/latest/
Author: OpenStack
Author-email: openstack-dev@lists.openstack.org
License: Apache License, Version 2.0
Location: /usr/lib/python2.7/site-packages
Requires: cryptography, setuptools, jmespath, oslo.utils, Jinja2, PyYAML, netaddr, docker, six, oslo.config, pbr
Required-by:

global.yml

---
openstack_release: "rocky"
enable_etcd: "yes"
enable_kuryr: "yes"
enable_zun: "yes"
...

Deploying kuryr failed because it can't fetch the image

TASK [kuryr : Pulling kuryr image] ******************************************************************************************************************************************************************
fatal: [compute1]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_SLO9VV/__main__.py\", line 910, in main\\n result = bool(getattr(dw, module.params.get(\\'action\\'))())\\n File \"/tmp/ansible_kolla_docker_payload_SLO9VV/__main__.py\", line 532, in pull_image\\n repository=image, tag=tag, stream=True\\n File \"/usr/lib/python2.7/site-packages/docker/api/image.py\", line 414, in pull\\n self._raise_for_status(response)\\n File \"/usr/lib/python2.7/site-packages/docker/api/client.py\", line 263, in _raise_for_status\\n raise create_api_error_from_http_exception(e)\\n File \"/usr/lib/python2.7/site-packages/docker/errors.py\", line 31, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation)\\nImageNotFound: 404 Client Error: Not Found (\"repository kolla/centos-binary-kuryr-libnetwork not found: does not exist or no pull access\")\\n'"}
2019-05-21 04:02:30 -0500 received badge  Famous Question (source)
2019-05-20 10:33:25 -0500 received badge  Notable Question (source)
2019-05-14 06:59:28 -0500 received badge  Popular Question (source)
2019-05-14 06:59:28 -0500 received badge  Notable Question (source)
2019-04-28 21:51:02 -0500 commented question Error to access dashboard

that's an unusual error, what does the logs says?

2019-04-18 03:27:48 -0500 received badge  Popular Question (source)
2019-04-17 11:22:52 -0500 commented answer [kolla] all bridge interfaces are down

complete ping tests 1. VM to VM using the private IP = success 2. VM to VM using the floating IP = success 3. VM to VM router = success 4. Controller/Compute to VM = failed

2019-04-15 04:02:48 -0500 commented question [kolla] all bridge interfaces are down

it can't ping out from the q-router http://paste.openstack.org/raw/dsUKWt...

2019-04-15 03:23:24 -0500 commented question [kolla] all bridge interfaces are down
2019-04-14 22:43:12 -0500 answered a question [kolla] all bridge interfaces are down

Additional Update 1. The instance can ping it's gateway (the controller) but beyond that, there's nothing. C:\fakepath\2019-04-15 11_42_08-Window.png

2019-04-14 06:01:32 -0500 commented answer [kolla] all bridge interfaces are down

launched cirros but it cannot ping out

2019-04-14 02:16:54 -0500 commented question The VMs cannot access the Internet after installing the OpenStack via Kolla-ansible

we have the same problem and I'm still trying to find out why

2019-04-14 02:16:10 -0500 commented answer Interfaces created by kolla in DOWN/UNKNOWN state

i actually did this but it did not solve the problem, here's the link of my question https://ask.openstack.org/en/question...

2019-04-13 23:52:31 -0500 asked a question [kolla] all bridge interfaces are down

Kolla-ansible 7.1.0 on CentOS 7, Rocky release

1st NIC = bond0, with public IP

2nd NIC = enp1s0f1, no IP

globals.yml
network_interface: "bond0"
neutron_external_interface: "enp1s0f1"
kolla_internal_vip_address: "<public_IP"
enable_haproxy: "no"

[root@openstack-controller1 kolla]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp1s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 50:6b:4b:09:15:14 brd ff:ff:ff:ff:ff:ff
3: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP qlen 1000
    link/ether 50:6b:4b:09:15:15 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::526b:4bff:fe09:1515/64 scope link
       valid_lft forever preferred_lft forever
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 50:6b:4b:09:15:14 brd ff:ff:ff:ff:ff:ff
    inet <public_IP>/31 brd 255.255.255.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet 10.64.26.131/31 brd 255.255.255.255 scope global bond0:0
       valid_lft forever preferred_lft forever
    inet6 2604:1380:3000:2d00::3/127 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::526b:4bff:fe09:1514/64 scope link
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
    link/ether 02:42:7f:81:3e:e0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
6: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 02:fd:7d:e3:23:3b brd ff:ff:ff:ff:ff:ff
7: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 50:6b:4b:09:15:15 brd ff:ff:ff:ff:ff:ff
8: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 4a:0b:79:a2:5a:43 brd ff:ff:ff:ff:ff:ff
9: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether a2:fb:30:b8:e5:4d brd ff:ff:ff:ff:ff:ff
13: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN qlen 1000
    link/ether 6a:82:0f:b1:d8:d4 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6882:fff:feb1:d8d4/64 scope link
       valid_lft forever preferred_lft forever
[root@openstack-controller1 kolla]#
2019-03-20 02:19:02 -0500 received badge  Famous Question (source)
2019-03-20 01:54:33 -0500 commented answer high availability for controller and compute in openstack

to add, there's a Masakari Service for Instance HA, I haven't tested it yet though https://www.openstack.org/software/re...

2019-03-20 01:49:48 -0500 answered a question Can anyone please help me how to install openstack queens in ubuntu 16.04?

you can also try using kolla-ansible for deploying an all-in-one environment. https://docs.openstack.org/kolla-ansi...

2019-03-20 01:48:12 -0500 answered a question kolla-ansible all-in-one to multinode?

Just update the inventory to include the other nodes and it will configure it as multinode

2019-03-20 01:42:39 -0500 asked a question [kolla] Disabling haproxy does not work

Environment: Ubuntu Version: Queens

I have a 2 node deployment and I disabled haproxy in globals.yml but for some reason it does not doing what it's supposed to do.

An error on the deployment run reveals that MariaDB is trying to connect to a VIP

TASK [mariadb : Waiting for MariaDB service to be ready through VIP] ********************************************************************************************************************************
FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (6 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (5 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (4 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (3 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (2 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready through VIP (1 retries left).
fatal: [192.168.0.115]: FAILED! => {"attempts": 6, "changed": false, "cmd": ["docker", "exec", "mariadb", "mysql", "-h", "192.168.0.199", "-P", "3306", "-u", "haproxy", "-e", "show databases;"], "delta": "0:00:03.093026", "end": "2019-03-20 02:11:02.423933", "msg": "non-zero return code", "rc": 1, "start": "2019-03-20 02:10:59.330907", "stderr": "ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.0.199' (113 \"No route to host\")", "stderr_lines": ["ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.0.199' (113 \"No route to host\")"], "stdout": "", "stdout_lines": []}

enabling haproxy fixes it.

2019-03-03 20:47:43 -0500 received badge  Notable Question (source)
2019-03-03 10:05:56 -0500 commented question Zun not starting up

I was thinking that it might be related to this https://bugs.launchpad.net/kolla-ansi... as my controller is also a compute, I am redoing my environment to separate them.

2019-03-01 01:38:35 -0500 commented question Zun not starting up

I already saw the error on kolla logs and a possible cause is that i haven't setup docker on the node properly that's why zun is complaining

2019-02-28 22:31:52 -0500 received badge  Popular Question (source)
2019-02-28 01:34:38 -0500 asked a question Zun not starting up

using kolla-ansible to deploy my environment, I added zun and kuryr and noticed that I got errors when trying to work on containers via horizon. Then I found out that the zun_compute container is restarting and wont boot up. Kuryr is fine though.

[root@kolla1 kolla]# docker ps |grep zun
0785e894c238        kolla/centos-source-zun-compute:rocky                 "dumb-init --single-c"   15 hours ago        Restarting (1) 19 minutes ago                       zun_compute
27ea20e663f5        kolla/centos-source-zun-wsproxy:rocky                 "dumb-init --single-c"   34 hours ago        Up 34 hours                                         zun_wsproxy
3c82f29b23a3        kolla/centos-source-zun-api:rocky                     "dumb-init --single-c"   34 hours ago        Up 34 hours                                         zun_api
[root@kolla1 kolla]#
[root@kolla1 kolla]# docker ps |grep kur
e0fe62d4e052        kolla/centos-source-kuryr-libnetwork:rocky            "dumb-init --single-c"   34 hours ago        Up 34 hours                                         kuryr
[root@kolla1 kolla]#

Tried restarting the containers but zun_compute still wont run. Logs also is not help as I don't see any relevant error messages.

2019-02-27 07:30:34 -0500 received badge  Teacher (source)
2019-02-26 21:39:13 -0500 answered a question Why we choose OpenStack cloud platform to build a private cloud ?

Firstly, it's open source, that's a big plus to me, then It's fully customizable, it's stable and reliable enough to be deployed on production, though there are some bugs here and there but it's minimal and most of the time resolvable, You can ask help from the OpenStack community here and/or in the Mailing List, the community is huge. I've deployed and used it in production since 2014.

2019-02-26 21:28:17 -0500 answered a question How can I add new HDD to openstack system.

More details please.

  1. Is your node already using LVM?
  2. What errors are you seeing?
2019-02-24 19:47:57 -0500 received badge  Notable Question (source)
2019-02-21 21:19:02 -0500 received badge  Popular Question (source)
2019-02-18 07:41:02 -0500 asked a question kolla-ansible precheck error

Can't figure out the problem, it stopped at this TASK, the node is newly installed with Minimal CentOS 7, the only service running is SSH.

TASK [glance : Checking free port for Glance Registry] ******************************************************************************************************************************************
fatal: [10.150.7.102]: FAILED! => {"msg": "The conditional check 'inventory_hostname in groups[glance_services['glance-registry']['group']]' failed. The error was: error while evaluating conditional (inventory_hostname in groups[glance_services['glance-registry']['group']]): Unable to look up a name or access an attribute in template string ({% if inventory_hostname in groups[glance_services['glance-registry']['group']] %} True {% else %} False {% endif %}).\nMake sure your variable name does not contain invalid characters like '-': argument of type 'StrictUndefined' is not iterable\n\nThe error appears to have been in '/usr/share/kolla-ansible/ansible/roles/glance/tasks/precheck.yml': line 18, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Checking free port for Glance Registry\n  ^ here\n"}
        to retry, use: --limit @/usr/share/kolla-ansible/ansible/site.retry

PLAY RECAP **************************************************************************************************************************************************************************************
10.150.7.102               : ok=68   changed=0    unreachable=0    failed=1
10.150.7.103               : ok=15   changed=0    unreachable=0    failed=0
localhost                  : ok=10   changed=0    unreachable=0    failed=0
2019-02-12 07:55:02 -0500 received badge  Famous Question (source)
2018-02-16 20:01:16 -0500 received badge  Notable Question (source)
2018-02-16 20:01:16 -0500 received badge  Famous Question (source)