Open Stack

Can I change Docker registry to use my local one in advance? If possible, do I need to synchronize registry in advance?
Is there any guidance?




-----Original Message-----
From: openstack-discuss-bounces+sz_cuitao=163.com at lists.openstack.org <openstack-discuss-bounces+sz_cuitao=163.com at lists.openstack.org> On Behalf Of Tommy Sway
Sent: Wednesday, August 25, 2021 2:05 AM
To: 'Sean Mooney' <smooney at redhat.com>; 'Radosław Piliszek' <radoslaw.piliszek at gmail.com>
Cc: 'openstack-discuss' <openstack-discuss at lists.openstack.org>
Subject: RE: What is this error, does it effect the install?

This error maybe because the internet download speed is too slow, can I change the docker registry source to resolve it ?



fatal: [network02]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n  File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line 268, in _raise_for_status\\n    response.raise_for_status()\\n  File \"/usr/lib/python3.6/site-packages/requests/models.py\", line 940, in raise_for_status\\n    raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=wallaby&fromImage=kolla%2Fcentos-binary-neutron-openvswitch-agent\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n  File \"/tmp/ansible_kolla_docker_payload_nob6zdmd/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1199, in main\\n  File \"/tmp/ansible_kolla_docker_payload_nob6zdmd/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 850, in recreate_or_restart_container\\n  File \"/tmp/ansible_kolla_docker_payload_nob6zdmd/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 868, in start_container\\n  File \"/tmp/ansible_kolla_docker_payload_nob6zdmd/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 650, in pull_image\\n  File \"/usr/local/lib/python3.6/site-packages/docker/api/image.py\", line 430, in pull\\n    self._raise_for_status(response)\\n  File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line 270, in _raise_for_status\\n    raise create_api_error_from_http_exception(e)\\n  File \"/usr/local/lib/python3.6/site-packages/docker/errors.py\", line 31, in create_api_error_from_http_exception\\n    raise cls(e, response=response, explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=wallaby&fromImage=kolla%2Fcentos-binary-neutron-openvswitch-agent: Internal Server Error (\"Get \"https://registry-1.docker.io/v2/\": context deadline exceeded\")\\n'"}











-----Original Message-----
From: Sean Mooney <smooney at redhat.com>
Sent: Wednesday, August 25, 2021 1:45 AM
To: Tommy Sway <sz_cuitao at 163.com>; 'Radosław Piliszek' <radoslaw.piliszek at gmail.com>
Cc: 'openstack-discuss' <openstack-discuss at lists.openstack.org>
Subject: Re: What is this error, does it effect the install?

On Wed, 2021-08-25 at 01:24 +0800, Tommy Sway wrote:
> Could you please tell me again that when kolla tool is used for formal deployment, if there are failed steps or nodes are damaged in the middle, is it ok for me to reinstall a new node, add it in and run the deployment command again?
> I've heard that Ansible-based deployments are generally idempotent, so that shouldn't be a problem.
> Isn't it?
it kind of depends on what faild and where.
you willl ahve to rebootstrap the node if you reinstall it.

most of the time if somethign fails with kolla you can just fix the problem in your config or whatever caused it and re run deploy.
you generally shoudl not need to reinstall the os. running kolla-ansible destory will generally clean up the env fully if it comes to that.


if you do remove the node and try to re add it its generally better not to reuse hostnames.
you can but then you might need to do service specific cleanups in some cases.

in this partical case it was jsut complaing that localhost does not have docker.
localhost (presumable your laptop/desktop) does not need docker unless you intende to buidl the kolla images your self inwhich case the fix is just install docker and if you run prechecks again it should pass.

> Thank you very much!
> 
> 
> 
> -----Original Message-----
> From: Radosław Piliszek <radoslaw.piliszek at gmail.com>
> Sent: Tuesday, August 24, 2021 10:33 PM
> To: Tommy Sway <sz_cuitao at 163.com>
> Cc: openstack-discuss <openstack-discuss at lists.openstack.org>
> Subject: Re: What is this error, does it effect the install?
> 
> On Tue, Aug 24, 2021 at 4:23 PM Tommy Sway <sz_cuitao at 163.com> wrote:
> > 
> > I try to install Openstack using kolla, but it’s a error when I check the system before installation :
> > 
> > 
> > 
> > # kolla-ansible -i ./multinode prechecks
> > 
> > 
> > 
> > 
> > 
> > PLAY RECAP
> > ********************************************************************
> > **
> > *****************************************
> > 
> > compute01                  : ok=28   changed=0    unreachable=0    failed=0    skipped=24   rescued=0    ignored=0
> > 
> > control01                  : ok=65   changed=0    unreachable=0    failed=0    skipped=59   rescued=0    ignored=0
> > 
> > control02                  : ok=62   changed=0    unreachable=0    failed=0    skipped=53   rescued=0    ignored=0
> > 
> > control03                  : ok=62   changed=0    unreachable=0    failed=0    skipped=53   rescued=0    ignored=0
> > 
> > localhost                  : ok=6    changed=0    unreachable=0    failed=1    skipped=2    rescued=0    ignored=0
> > 
> > monitoring01               : ok=18   changed=0    unreachable=0    failed=0    skipped=15   rescued=0    ignored=0
> > 
> > network01                  : ok=47   changed=0    unreachable=0    failed=0    skipped=109  rescued=0    ignored=0
> > 
> > network02                  : ok=47   changed=0    unreachable=0    failed=0    skipped=105  rescued=0    ignored=0
> > 
> > storage01                  : ok=18   changed=0    unreachable=0    failed=0    skipped=15   rescued=0    ignored=0
> > 
> > 
> > 
> > 
> > 
> > The error is :
> > 
> > 
> > 
> > The full traceback is:
> > 
> > Traceback (most recent call last):
> > 
> >   File
> > "/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-26360093203
> > 73 31/AnsiballZ_kolla_container_facts.py", line 102, in <module>
> > 
> >     _ansiballz_main()
> > 
> >   File
> > "/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-26360093203
> > 73 31/AnsiballZ_kolla_container_facts.py", line 94, in 
> > _ansiballz_main
> > 
> >     invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
> > 
> >   File
> > "/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-26360093203
> > 73 31/AnsiballZ_kolla_container_facts.py", line 40, in invoke_module
> > 
> >     
> > runpy.run_module(mod_name='ansible.modules.kolla_container_facts',
> > init_globals=None, run_name='__main__', alter_sys=True)
> > 
> >   File "/usr/lib64/python3.6/runpy.py", line 205, in run_module
> > 
> >     return _run_module_code(code, init_globals, run_name, mod_spec)
> > 
> >   File "/usr/lib64/python3.6/runpy.py", line 96, in _run_module_code
> > 
> >     mod_name, mod_spec, pkg_name, script_name)
> > 
> >   File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
> > 
> >     exec(code, run_globals)
> > 
> >   File
> > "/tmp/ansible_kolla_container_facts_payload_v95779u3/ansible_kolla_c
> > on
> > tainer_facts_payload.zip/ansible/modules/kolla_container_facts.py",
> > line 18, in <module>
> > 
> > ModuleNotFoundError: No module named 'docker'
> > 
> > fatal: [localhost]: FAILED! => {
> > 
> >     "changed": false,
> > 
> >     "module_stderr": "Traceback (most recent call last):\n  File \"/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/AnsiballZ_kolla_container_facts.py\", line 102, in <module>\n    _ansiballz_main()\n  File \"/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/AnsiballZ_kolla_container_facts.py\", line 94, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/AnsiballZ_kolla_container_facts.py\", line 40, in invoke_module\n    runpy.run_module(mod_name='ansible.modules.kolla_container_facts', init_globals=None, run_name='__main__', alter_sys=True)\n  File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n    return _run_module_code(code, init_globals, run_name, mod_spec)\n  File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n    mod_name, mod_spec, pkg_name, script_name)\n  File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n    exec(code, run_globals)\n  File \"/tmp/ansible_kolla_container_facts_payload_v95779u3/ansible_kolla_container_facts_payload.zip/ansible/modules/kolla_container_facts.py\", line 18, in <module>\nModuleNotFoundError: No module named 'docker'\n",
> > 
> >     "module_stdout": "",
> > 
> >     "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
> > 
> >     "rc": 1
> > 
> > }
> > 
> > 
> > 
> > 
> > 
> > I installed the docker package on the deploy localhost and run again, but it still raise the same error.
> > 
> > 
> > 
> > What is it ? And does it effect the install ?
> > 
> > 
> 
> It's a minor bug in that the tooling should not be trying to check docker on localhost.
> It should be fine to progress ignoring this particular issue.
> 
> -yoctozepto
> 
> 
>