Services should not be started until metadata exists

Bug #1334313 reported by Dan Prince on 2014-06-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Dan Prince

Bug Description

All of the OpenStack services appear to be started/restarted multiple times before proper config metadata exists. See the nova-compute log file for example:

-- Logs begin at Wed 2014-06-25 13:42:22 UTC, end at Wed 2014-06-25 13:51:37 UTC. --
Jun 25 13:42:59 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Starting nova-compute Service...
Jun 25 13:42:59 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Started nova-compute Service.
Jun 25 13:43:13 overcloud-novacompute0-pbi3gpdge523 nova-compute[1284]: 2014-06-25 13:43:13.184 1284 ERROR nova.virt.driver [-] Compute driver option required, but not specified
Jun 25 13:43:13 overcloud-novacompute0-pbi3gpdge523 systemd[1]: nova-compute.service: main process exited, code=exited, status=1/FAILURE
Jun 25 13:43:13 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Unit nova-compute.service entered failed state.
Jun 25 13:43:19 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Starting nova-compute Service...
Jun 25 13:43:19 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Started nova-compute Service.
Jun 25 13:43:21 overcloud-novacompute0-pbi3gpdge523 nova-compute[1903]: 2014-06-25 13:43:21.449 1903 ERROR nova.virt.driver [-] Compute driver option required, but not specified
Jun 25 13:43:21 overcloud-novacompute0-pbi3gpdge523 systemd[1]: nova-compute.service: main process exited, code=exited, status=1/FAILURE
Jun 25 13:43:21 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Unit nova-compute.service entered failed state.
Jun 25 13:47:04 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Starting nova-compute Service...
Jun 25 13:47:04 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Started nova-compute Service.
Jun 25 13:47:06 overcloud-novacompute0-pbi3gpdge523 nova-compute[2481]: 2014-06-25 13:47:06.662 2481 INFO oslo.messaging._drivers.impl_rabbit [req-be149bf4-77b1-4bd1-ac37-7ff96b7bf3ae ] Connected to AMQP server on 192.0.2.3:5672

---

Ditto for Neutron:

-- Logs begin at Wed 2014-06-25 13:42:22 UTC, end at Wed 2014-06-25 13:51:37 UTC. --
Jun 25 13:42:57 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Starting neutron-openvswitch-agent Service...
Jun 25 13:42:57 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Started neutron-openvswitch-agent Service.
Jun 25 13:43:12 overcloud-novacompute0-pbi3gpdge523 neutron-openvswitch-agent[1238]: 2014-06-25 13:43:12.521 1238 CRITICAL neutron [-] Unexpected boolean value ''
Jun 25 13:43:12 overcloud-novacompute0-pbi3gpdge523 systemd[1]: neutron-openvswitch-agent.service: main process exited, code=exited, status=1/FAILURE
Jun 25 13:43:12 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Unit neutron-openvswitch-agent.service entered failed state.
Jun 25 13:43:18 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Starting neutron-openvswitch-agent Service...
Jun 25 13:43:18 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Started neutron-openvswitch-agent Service.
Jun 25 13:43:20 overcloud-novacompute0-pbi3gpdge523 neutron-openvswitch-agent[1853]: 2014-06-25 13:43:20.471 1853 CRITICAL neutron [-] Unexpected boolean value ''
Jun 25 13:43:20 overcloud-novacompute0-pbi3gpdge523 systemd[1]: neutron-openvswitch-agent.service: main process exited, code=exited, status=1/FAILURE
Jun 25 13:43:20 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Unit neutron-openvswitch-agent.service entered failed state.
Jun 25 13:47:03 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Starting neutron-openvswitch-agent Service...
Jun 25 13:47:03 overcloud-novacompute0-pbi3gpdge523 systemd[1]: Started neutron-openvswitch-agent Service.
Jun 25 13:47:05 overcloud-novacompute0-pbi3gpdge523 sudo[2525]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=10 -- set-fail-mode br-int secure

----

I'm not sure yet if this is an os-collect-config issue, Heat related or something else... but this shouldn't be happening. Having services get started before proper config files exist could cause bad "default" things to happen in some cases.

Dan Prince (dan-prince) on 2014-06-25
Changed in tripleo:
importance: Undecided → High
status: New → Triaged
Dan Prince (dan-prince) on 2014-06-25
Changed in tripleo:
assignee: nobody → Dan Prince (dan-prince)
Dan Prince (dan-prince) on 2014-06-25
Changed in tripleo:
assignee: Dan Prince (dan-prince) → nobody
Dan Prince (dan-prince) on 2014-06-25
Changed in tripleo:
assignee: nobody → Dan Prince (dan-prince)

This bug was reported against an old version of TripleO, and may no longer be valid.

Since it was reported before the start of the liberty cycle (and our oldest stable
branch is stable/liberty), I'm marking this incomplete.

Please reopen this (change the status from incomplete) if the bug is still valid
on a current supported (stable/liberty, stable/mitaka or trunk) version of TripleO,
thanks!

Changed in tripleo:
status: Triaged → Incomplete
Ben Nemec (bnemec) wrote :

Pretty sure this is not happening anymore. Feel free to reopen if it is.

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

Other bug subscribers