Ask Your Question

harish23r's profile - activity

2017-11-22 12:38:01 -0600 received badge  Taxonomist
2017-09-21 05:23:17 -0600 received badge  Famous Question (source)
2017-09-21 05:23:17 -0600 received badge  Notable Question (source)
2017-09-21 05:23:17 -0600 received badge  Popular Question (source)
2017-05-10 02:03:52 -0600 received badge  Popular Question (source)
2017-05-10 02:03:52 -0600 received badge  Notable Question (source)
2017-02-27 21:35:12 -0600 received badge  Famous Question (source)
2017-02-26 00:45:38 -0600 asked a question VirtutalBox Network Configuration for Openstack Kolla AIO Deployment?

Hi. I'm using virtual box to run a Kolla All-in-one deployment. The deployment fails for some reason and I suspect a problem in network configuration. Here are my details.

Host OS: Ubuntu 16.04
VirtualBox Host Network Config
NAT Network:
Default settings
CIDR 10.0.2.0/24
DHCP Enabled
Host-Only Adapter
IP: 10.11.11.1 Mask: 255.255.255.0
DHCP Enabled:
Server: 10.11.11.2
Mask:255.255.255.0 DHCP Lease Range 10.11.11.3 to 10.11.11.100


Guest OS: Ubuntu 16.04
Interface enp0s3 (NAT) (Enabled at Settings -> Network)
Assigned IP: 10.0.2.15
Interface enp0s8 (Host-Only) (Enabled at VM settings -> Network)
Static IP: 10.11.11.3 Gateway: 10.11.11.1(Host OS)

I am able to ping the Host OS, and access internet from the guest OS. But I get problems while deployment Any Corrections to do? Please do suggest corrections or a new correct network configuration for deploying Kolla in Virtual Box.

2017-02-26 00:33:58 -0600 commented answer Kolla AIO deploy fail: Hostname has to resolve IP address ?

And what should I change here? How to point address on the interface?

2017-02-26 00:33:28 -0600 commented answer Kolla AIO deploy fail: Hostname has to resolve IP address ?

I don't seem to get your answer. Linux by deafult maps 127.0.0.1 to localhost. ?

2017-02-25 13:25:15 -0600 received badge  Editor (source)
2017-02-25 13:23:40 -0600 asked a question Kolla AIO deploy fail: Hostname has to resolve IP address ?

I'm trying to deploy Kolla in AIO.
I build images using the command: kolla-build -p default -b ubuntu -t binary
I am deploying it in my local system. I'm using ubuntu 16.04, built images. I'm not using a local registry.

kolla-ansible precheck runs fine

kolla-ansible deploy gives me an error while starting rabbitmq
My host name is DESKTOP
The output of hosts file
cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 DESKTOP

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

The error is as follows
TASK: [rabbitmq | fail msg="Hostname has to resolve to IP address of api_interface"] * failed: [localhost] => (item={u'cmd': [u'getent', u'ahostsv4', u'DESKTOP'], u'end': u'2017-02-26 00:45:10.399323', u'stderr': u'', u'stdout': u'127.0.1.1 STREAM DESKTOP\n127.0.1.1 DGRAM \n127.0.1.1 RAW ', u'changed': False, u'rc': 0, 'item': 'localhost', u'warnings': [], u'delta': u'0:00:00.001585', 'invocation': {'module_name': u'command', 'module_complex_args': {}, 'module_args': u'getent ahostsv4 DESKTOP'}, 'stdout_lines': [u'127.0.1.1 STREAM DESKTOP', u'127.0.1.1 DGRAM ', u'127.0.1.1 RAW '], u'start': u'2017-02-26 00:45:10.397738'}) => {"failed": true, "item": {"changed": false, "cmd": ["getent", "ahostsv4", "DESKTOP"], "delta": "0:00:00.001585", "end": "2017-02-26 00:45:10.399323", "invocation": {"module_args": "getent ahostsv4 DESKTOP", "module_complex_args": {}, "module_name": "command"}, "item": "localhost", "rc": 0, "start": "2017-02-26 00:45:10.397738", "stderr": "", "stdout": "127.0.1.1 STREAM DESKTOP\n127.0.1.1 DGRAM \n127.0.1.1 RAW ", "stdout_lines": ["127.0.1.1 STREAM DESKTOP", "127.0.1.1 DGRAM ", "127.0.1.1 RAW "], "warnings": []}} msg: Hostname has to resolve to IP address of api_interface

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************** to retry, use: --limit @/home/ravichandran/site.retry

localhost : ok=84 changed=11 unreachable=0 failed=1

Please help.

2017-02-24 08:03:10 -0600 commented question single node kolla deployment failed while starting heka container: internal server error?

I have done the extra configurations as said in the guide, earlier. and Only then this error. But there won't be a problem if I don't use a local registry right? Mutlinode deployment isn't really a necessity.

2017-02-24 02:54:08 -0600 commented question single node kolla deployment failed while starting heka container: internal server error?

While using Kolla-build, I build only specific images and pushed it to the registry, only horizon, glance, nova, neutron, keystone. Will that be a problem?

2017-02-24 02:46:41 -0600 commented answer single node kolla deployment failed while starting heka container: internal server error?

WARNING: Host file not found: inventory-file WARNING: provided hosts list is empty, only localhost is available PLAY RECAP ***********************

2017-02-24 02:46:17 -0600 commented answer single node kolla deployment failed while starting heka container: internal server error?

Is theera any other option I need to check? Output for kolla-ansible pull -i inventory_file is below: Pulling Docker images : ansible-playbook -i inventory-file -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e action=pull /usr/local/share/kolla/ansible/site.yml

2017-02-24 02:44:52 -0600 commented question single node kolla deployment failed while starting heka container: internal server error?

I have configured the DOCKER_OPTS="--insecure-registry ID_ADDRESS:4000" option in my /etc/default/docker file in my Ubuntu 16.04. Still the issue persists . @Eduardo Gonzalez

2017-02-24 02:44:38 -0600 commented answer single node kolla deployment failed while starting heka container: internal server error?

I have configured the DOCKER_OPTS="--insecure-registry ID_ADDRESS:4000" option in my /etc/default/docker file in my Ubuntu 16.04. Still the issue persists .

2017-02-24 02:41:46 -0600 received badge  Notable Question (source)
2017-02-23 02:17:55 -0600 commented question single node kolla deployment failed while starting heka container: internal server error?

I do not have a kolla.conf file in the system. But the docker has started on start up.

2017-02-22 17:18:14 -0600 received badge  Popular Question (source)
2017-02-16 09:27:34 -0600 asked a question single node kolla deployment failed while starting heka container: internal server error?

I'm trying to deploy a single node installation of kolla, which I will later be extending to 2 hosts. All the steps work until the "kolla-ansible deploy" command. Tried with Docker version 1.12 as well as version 1.13.
I've build all the container images using kolla-build command and pushed the images in the local docker registry running at port 4000. I configured by giving the correct values globals.yml file for the repository.

When I give kolla-ansible deploy, the deployment stops while starting heka container with the following error:
TASK: [common | starting heka container] *********** failed: [localhost] => {"changed": true, "failed": true} msg: APIError(HTTPError(u'500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.25/containers/create?name=heka',),)

FATAL: all hosts have failed -- aborting

localhost : 0k=28 changed=0 unreachable=0 failed=1

I'm not sure if this is a config mistake with openstack kolla or with docker. I gave docker_insecure_registry to true in the globals.yml file. Is there some configuration I'm missing? Any place where I can check with detailed steps for deploying kolla?

Please help me, this is required for my capstone project.!

EDIT: While using Kolla-build, I build only specific images and pushed it to the registry, only horizon, glance, nova, neutron, keystone. Will that be a problem?

2017-02-16 06:11:28 -0600 received badge  Organizer (source)