cablelabs / snaps-openstack

OpenStack installer for SNAPS
Apache License 2.0
9 stars 10 forks source link

Error on install at "Running Neutron bootstrap container" #76

Open hasuf opened 6 years ago

hasuf commented 6 years ago

Running sudo python iaas_launch.py -l TRACE -f conf/openstack/kolla/deployment.yaml -drs 2>&1 |while read line; do printf "$(date -u '+%F %T%z')\t$line\n"; done | tee /var/tmp/iaas_launch-`date +%Y%m%d-%H%M%S`.log

Errors out at

"fatal: [10.30.17.11 -> 10.30.17.11]: FAILED! => {"changed": true,                                                                                                                            
"failed": true,                                                                                                                                                                               
"msg": "Container exited with non-zero return code"}",                                                                                                                                        
"", 

On my controller, I see:

root@CONTROLLER01_COMPUTE012469:~# docker ps -al
CONTAINER ID        IMAGE                                                       COMMAND             CREATED             STATUS                     PORTS               NAMES
f70a5a5edf55        10.30.17.11:4000/kolla/ubuntu-source-neutron-server:5.0.2   "kolla_start"       6 minutes ago       Exited (1) 6 minutes ago                       bootstrap_neutron

and

root@CONTROLLER01_COMPUTE012469:~# docker logs f70a5a5edf55
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Copying /var/lib/kolla/config_files/neutron.conf to /etc/neutron/neutron.conf
INFO:__main__:Setting permission for /etc/neutron/neutron.conf
INFO:__main__:Copying /var/lib/kolla/config_files/fwaas_driver.ini to /etc/neutron/fwaas_driver.ini
INFO:__main__:Setting permission for /etc/neutron/fwaas_driver.ini
INFO:__main__:Copying /var/lib/kolla/config_files/neutron_lbaas.conf to /etc/neutron/neutron_lbaas.conf
INFO:__main__:Setting permission for /etc/neutron/neutron_lbaas.conf
INFO:__main__:Copying /var/lib/kolla/config_files/neutron_vpnaas.conf to /etc/neutron/neutron_vpnaas.conf
INFO:__main__:Setting permission for /etc/neutron/neutron_vpnaas.conf
INFO:__main__:Copying /var/lib/kolla/config_files/ml2_conf.ini to /etc/neutron/plugins/ml2/ml2_conf.ini
INFO:__main__:Setting permission for /etc/neutron/plugins/ml2/ml2_conf.ini
INFO:__main__:Writing out command to execute

Traceback (most recent call last):
  File "/var/lib/kolla/venv/bin/neutron-db-manage", line 10, in <module>
    sys.exit(main())
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 687, in main
    return_val |= bool(CONF.command.func(config, CONF.command.name))
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 206, in do_upgrade
    run_sanity_checks(config, revision)
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/db/migration/cli.py", line 671, in run_sanity_checks
    script_dir.run_env()
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/alembic/script/base.py", line 425, in run_env
    util.load_python_file(self.dir, 'env.py')
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/alembic/util/pyfiles.py", line 93, in load_python_file
    module = load_module_py(module_id, path)
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/alembic/util/compat.py", line 75, in load_module_py
    mod = imp.load_source(module_id, path, fp)
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/db/migration/alembic_migrations/env.py", line 24, in <module>
    from neutron.db.migration.models import head  # noqa
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/db/migration/models/head.py", line 29, in <module>
    from neutron.db import agentschedulers_db  # noqa
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/db/agentschedulers_db.py", line 30, in <module>
    from neutron.agent.common import utils as agent_utils
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/agent/common/utils.py", line 23, in <module>
    from neutron.conf.agent import common as config
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/conf/agent/common.py", line 23, in <module>
    from neutron.common import config
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/common/config.py", line 31, in <module>
    from neutron.conf import common as common_config
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/conf/common.py", line 96, in <module>
    help=_("Hostname to be used by the Neutron server, "
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 1484, in __init__
    **kwargs)
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 959, in __init__
    self._check_default()
  File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_config/cfg.py", line 980, in _check_default
    'opt': self.type})
oslo_config.cfg.DefaultValueError: Error processing default value CONTROLLER01_COMPUTE012469 for Opt type of HostAddress.

My host info looks correct on the controller:

CONTROLLER01_COMPUTE012469
root@CONTROLLER01_COMPUTE012469:~# cat /etc/hosts
127.0.1.1       unassigned-hostname.unassigned-domain   unassigned-hostname snaps-node-01

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
192.168.122.25 kernel-vhost
192.168.122.35 spdk-vhost

10.30.17.11 CONTROLLER01_COMPUTE012469
10.30.17.12 COMPUTE022818
127.0.0.1 localhost
hasuf commented 6 years ago

Adding log file: iaas_launch-20180126-145212.log

Adding deployment.yaml (renamed here with .txt suffix so I could attach the yaml file) deployment.yaml.txt

chiraggupta06 commented 6 years ago

Hi, Seems like the issue is with mariadb container. Try deploying openstack with different keepalived_virtual_router_id(can be anything from 0-255) and virtual ip provided in deployment.yaml. The tags are present in deployment.yaml as keepalived_virtual_router_id: , internal_vip_address:, external_vip_address:

Br, chirag gupta

hasuf commented 6 years ago

Hi, I changed the values

...
     keepalived_virtual_router_id: "100"                                                                                                                              
...                                                                                                           
     internal_vip_address: "10.30.17.5"                                                                                                                               
...                                                                                                                           
     external_vip_address: "10.30.19.6"                                                                                                                               
...

but got the same error:

"fatal: [10.30.17.11 -> 10.30.17.11]: FAILED! => {"changed": true,                                                                                                    
"failed": true,                                                                                                                                                       
"msg": "Container exited with non-zero return code"}",                                                                                                                
"",       

iaas_launch-20180129-133929.log

chiraggupta06 commented 6 years ago

Hi, Can you please check that mariadb container status after cleanup you can use command docker ps -a for this and provide mariadb,neutron container logs via command "docker logs mariadbcontainerID" . Also provide logs present inside mariadb container at /var/log/kolla/mariadb/ you can access container via command: "docker exec -it containerID bash"