[SRU] ironic-conductor.init.in has wrong entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ironic (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Vivid |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
ironic conductor process is not started by init
[Test Case]
sudo apt-get install ironic-conductor
[Regression Potential]
None
[Original Bug Report]
Description: Ubuntu 14.04.1 LTS
Release: 14.04
ii ironic-api 2015.1~
ii ironic-common 2015.1~
ii ironic-conductor 2015.1~
ii python-ironic 2015.1~
ii python-ironicclient 0.3.1-0ubuntu1~
ironic-conductor 2015.1~
ironic_
ironic-
It looks like this:
#!/bin/sh
### BEGIN INIT INFO
# Provides: ironic-api
# Required-Start: $network $local_fs $remote_fs $syslog
# Required-Stop: $remote_fs
# Should-Start: postgresql mysql keystone ntp rabbitmq-server
# Should-Stop: postgresql mysql keystone ntp rabbitmq-server
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Baremetal API server
# Description: Frontend Baremetal (Ironic) API server
### END INIT INFO
# Author: Thomas Goirand <email address hidden>
DESC="OpenStack Baremetal Service API"
PROJECT_NAME=ironic
NAME=ironic-api
All references to api should be conductor.
summary: |
- conductor has wrong + ironic-conductor.init.in has wrong entries |
Changed in ironic (Ubuntu): | |
assignee: | nobody → Ma Wen Cheng (mars914) |
status: | New → In Progress |
Changed in ironic (Ubuntu): | |
assignee: | Ma Wen Cheng (mars914) → nobody |
Changed in ironic (Ubuntu): | |
assignee: | nobody → Ma Wen Cheng (mars914) |
assignee: | Ma Wen Cheng (mars914) → nobody |
Changed in ironic (Ubuntu): | |
status: | In Progress → New |
Changed in ironic (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → In Progress |
description: | updated |
summary: |
- ironic-conductor.init.in has wrong entries + [SRU] ironic-conductor.init.in has wrong entries |
Changed in ironic (Ubuntu Vivid): | |
status: | Fix Committed → Fix Released |
from my local test, conductor installation has some problems, but not described as this bug.
it is that:
Declaring queue failed with (403: (ACCESS_REFUSED - operation not permitted on the default exchange, (50, 20), None)), retrying