kolla-deploy-AIO fail

Bug #1595128 reported by jianqingjiang on 2016-06-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Undecided
Unassigned

Bug Description

my /etc/kolla/kolla-build.conf is
[DEFAULT]
base = centos
install_type = soruce
namespace = lokolla
push = false

and I run ./tool/build.py -p default to deploy

here is the log:

TASK [common : include] ********************************************************
included: /root/kolla/ansible/roles/common/tasks/start.yml for localhost

TASK [common : Starting heka container] ****************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unknown error message: Tag 2.0.2 not found in repository docker.io/kollaglue/centos-source-heka"}
        to retry, use: --limit @/root/kolla/ansible/site.retry

PLAY RECAP *********************************************************************
localhost : ok=12 changed=0 unreachable=0 failed=1

Command failed ansible-playbook -i /root/kolla/ansible/inventory/all-in-one -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e action=deploy /root/kolla/ansible/site.yml

so I run docker images:
[root@kolla kolla]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
lokolla/centos-source-nova-libvirt 2.0.2 af48e5d8c222 29 hours ago 1.353 GB
lokolla/centos-source-nova-compute 2.0.2 d4ba7670b773 29 hours ago 933 MB
lokolla/centos-source-nova-ssh 2.0.2 5c16abe20e13 29 hours ago 849.2 MB
more...

I run "docker images" is ok, but when I deploy, the error log shows that kolla is using a outside docker registry...
and the quickstart says that it's ok not to deploy a local registry in my all-in-one env.

Swapnil Kulkarni (coolsvap) wrote :

Please attach or add the content of /etc/systemd/system/docker.service.d/kolla.conf and /etc/sysconfig/docker

Swapnil Kulkarni (coolsvap) wrote :

 also share the output of docker ps -a

Changed in kolla:
status: New → Incomplete
jianqingjiang (18367826256-3) wrote :

[root@kolla kolla]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

docker ps -a shows nothing

jianqingjiang (18367826256-3) wrote :

@Swapnil Kulkarni (coolsvap)
/etc/systemd/system/docker.service.d/kolla.conf and /etc/sysconfig/docker is new files, how do I edit them?
ps:My env is CentOS7

jianqingjiang (18367826256-3) wrote :

And I installed docker regsitry... but why kolla is complaining this path "192.168.52.219:4000/kollaglue/centos-source-heka:2.0.2".coz AIO install doesn't need a registry

TASK [common : Starting heka container] ****************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "The requested image does not exist: 192.168.52.219:4000/kollaglue/centos-source-heka:2.0.2"}
        to retry, use: --limit @/root/kolla/ansible/site.retry

PLAY RECAP *********************************************************************
localhost : ok=12 changed=0 unreachable=0 failed=1

jianqingjiang (18367826256-3) wrote :

I run command "docker images" show
localhost:4000/kollaglue/centos-source-heka latest 4b123bfd6c1d 2 days ago 371.1 MB

But kolla still complaining...
TASK [common : Starting heka container] ****************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "The requested image does not exist: localhost:4000/kollaglue/centos-source-heka:lastst"}
        to retry, use: --limit @/root/kolla/ansible/site.retry

PLAY RECAP *********************************************************************
localhost : ok=12 changed=0 unreachable=0 failed=1

Rahul Sharma (rahulsharmaait) wrote :

You have a typo: the image is built with tag "lastst" and not "latest". I guess you modified the openstack-release tag in etc/kolla/defaults.yml.

Rahul Sharma (rahulsharmaait) wrote :

Log says: "The requested image does not exist: localhost:4000/kollaglue/centos-source-heka:lastst"

So it is looking for image name with tag lastst. That is wrong probably due to misconfiguration in globals.yml file.

Launchpad Janitor (janitor) wrote :

[Expired for kolla because there has been no activity for 60 days.]

Changed in kolla:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers