kuryr deploy fails

Bug #1634700 reported by bjolo
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

ENV: kolla stable/newton; ubuntu source

kuryr deploy fails. container stuck in restarting.

docker logs kuryr
http://paste.openstack.org/show/586295

bjolo (bjorn-lofdahl)
description: updated
Changed in kolla:
milestone: none → ocata-1
status: New → Confirmed
importance: Undecided → High
Changed in kolla:
milestone: ocata-1 → ocata-2
Revision history for this message
Mauricio Lima (mliima) (mauricio-lima) wrote :
Download full text (5.2 KiB)

root@control:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7f45fb51fe53 control:4000/kolla/ubuntu-source-horizon:3.0.0 "kolla_start" 37 minutes ago Up 37 minutes horizon
6a4839c2be4b control:4000/kolla/ubuntu-source-neutron-metadata-agent:3.0.0 "kolla_start" 37 minutes ago Up 37 minutes neutron_metadata_agent
78a904a17a14 control:4000/kolla/ubuntu-source-neutron-l3-agent:3.0.0 "kolla_start" 37 minutes ago Up 37 minutes neutron_l3_agent
e3dde33b1d49 control:4000/kolla/ubuntu-source-neutron-dhcp-agent:3.0.0 "kolla_start" 37 minutes ago Up 37 minutes neutron_dhcp_agent
468f6dea1306 control:4000/kolla/ubuntu-source-neutron-openvswitch-agent:3.0.0 "kolla_start" 37 minutes ago Up 37 minutes neutron_openvswitch_agent
15d9006dc701 control:4000/kolla/ubuntu-source-neutron-server:3.0.0 "kolla_start" 37 minutes ago Up 37 minutes neutron_server
873930d5def5 control:4000/kolla/ubuntu-source-openvswitch-vswitchd:3.0.0 "kolla_start" 38 minutes ago Up 38 minutes openvswitch_vswitchd
f897d818cc24 control:4000/kolla/ubuntu-source-openvswitch-db-server:3.0.0 "kolla_start" 38 minutes ago Up 38 minutes openvswitch_db
868e41769ee9 control:4000/kolla/ubuntu-source-kuryr-libnetwork:3.0.0 "kolla_start" 39 minutes ago Up 37 minutes kuryr
1cc7242bf4ba control:4000/kolla/ubuntu-source-nova-ssh:3.0.0 "kolla_start" 39 minutes ago Up 39 minutes nova_ssh
bdbe860ea70c control:4000/kolla/ubuntu-source-nova-compute:3.0.0 "kolla_start" 39 minutes ago Up 39 minutes nova_compute
0ea8d61863af control:4000/kolla/ubuntu-source-nova-libvirt:3.0.0 "kolla_start" 40 minutes ago Up 39 minutes nova_libvirt
58f0a1fec868 control:4000/kolla/ubuntu-source-nova-conductor:3.0.0 "kolla_start" 40 minutes ago Up 40 minutes nova_conductor
5ceb8014bf89 control:4000/kolla/ubuntu-source-nova-scheduler:3.0.0 "kolla_start" 40 minutes ago Up 40 minutes nova_scheduler
eee0d1c612cb control:4000/kolla/ubuntu-source-nova-novncproxy:3.0.0 "kolla_start" 40 minutes ago Up 40 minutes nova_novncproxy
1e96f732a52a control:4000/kolla/ubuntu-source-nova-consoleauth:3.0.0 "kolla_start" ...

Read more...

Changed in kolla:
status: Confirmed → Invalid
Revision history for this message
Mauricio Lima (mliima) (mauricio-lima) wrote :
Revision history for this message
Mauricio Lima (mliima) (mauricio-lima) wrote :

kolla stable/newton; ubuntu source

bjolo, can you try to reproduce?

Revision history for this message
Matt McEuen (mm9745) wrote :

This affects me on stable/newton, ubuntu source. I get the same error in my kuryr docker logs:
Running command: 'kuryr-server --config-file /etc/kuryr/kuryr.conf'
/usr/local/bin/kolla_start: line 24: exec: kuryr-server: not found

Is there any additional info I can provide to help debug this?

Changed in kolla:
status: Invalid → Confirmed
Revision history for this message
janonymous (janonymous) wrote :

Hi Matt,

I can see the info logs, can you also paste the debug logs also..
I have some doubt regarding executable path but could not confirm atm without proper investigation:
If kolla uses upstart and calls this:

https://github.com/openstack/kuryr-libnetwork/blob/master/init/kuryr.conf#L13 (/usr/bin/kuryr-server) --> should be (/usr/local/bin/kuryr-server) [or kuryr-server directly if it is added to env]

Then path at which the distro is installing binary and path from which it is fetched are different.

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.