Systemd configs in docker containers contain errors and deprecated options

Bug #1642232 reported by Rodion Tikunov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
In Progress
Medium
Rodion Tikunov

Bug Description

Systemd configs in docker containers contain errors and deprecated options. It would be good to fix them.

Steps to reproduce:
docker logs fuel-core-8.0-rabbitmq
[/etc/systemd/system/start-container.service:4] Unknown lvalue 'ConditionFileExecutable' in section 'Unit'
[/etc/systemd/system/rabbitmq-server.service:10] Executable path is not absolute, ignoring: chown -R rabbitmq:rabbitmq /var/lib/rabbitmq

docker logs fuel-core-8.0-nginx
Failed to read PID from file /run/nginx.pid: Invalid argument
start-container.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Unit start-container.service entered failed state.
start-container.service failed.

docker logs fuel-core-8.0-mcollective
PID file /var/run/mcollective.pid not readable (yet?) after start.

docker logs fuel-core-8.0-ostf
[/usr/lib/systemd/system/ostf.service:2] Unknown lvalue 'Name' in section 'Unit'
[/etc/systemd/system/start-container.service:4] Unknown lvalue 'ConditionFileExecutable' in section 'Unit'
start-container.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Unit start-container.service entered failed state.
start-container.service failed.

docker logs fuel-core-8.0-astute
[/usr/lib/systemd/system/astute.service:2] Unknown lvalue 'Name' in section 'Unit'
[/etc/systemd/system/start-container.service:4] Unknown lvalue 'ConditionFileExecutable' in section 'Unit'
start-container.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Unit start-container.service entered failed state.
start-container.service failed.

docker logs fuel-core-8.0-rsync
PID file /var/run/xinetd.pid not readable (yet?) after start.

docker logs fuel-core-8.0-keystone
[/etc/systemd/system/start-container.service:4] Unknown lvalue 'ConditionFileExecutable' in section 'Unit'

docker logs fuel-core-8.0-postgres
[/etc/systemd/system/start-container.service:4] Unknown lvalue 'ConditionFileExecutable' in section 'Unit'

Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :
Changed in fuel:
assignee: MOS Linux (mos-linux) → Rodion Tikunov (rtikunov)
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Related fix proposed to tools/sustaining (master)

Related fix proposed to branch: master
Change author: Anton Chevychalov <email address hidden>
Review: https://review.fuel-infra.org/29482

Changed in fuel:
status: New → In Progress
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Related fix merged to tools/sustaining (master)

Reviewed: https://review.fuel-infra.org/29482
Submitter: Anton Chevychalov <email address hidden>
Branch: master

Commit: 7ad176e1d6f81fc6ef06de064076bc5564ff3197
Author: Anton Chevychalov <email address hidden>
Date: Wed Jan 18 11:00:11 2017

Fix 8.0 update procedure

There is a bug around lvm, systemd and xfs. So we need
to change update procedure.
Now it reboots master node after update.

Related-Bug: #1642232

Change-Id: Ie59e339d6876264fe463a47061089281acbcdc78

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Related fix proposed to mos/mos-docs (stable/8.0)

Related fix proposed to branch: stable/8.0
Change author: Anton Chevychalov <email address hidden>
Review: https://review.fuel-infra.org/33149

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Related fix merged to mos/mos-docs (stable/8.0)

Reviewed: https://review.fuel-infra.org/33149
Submitter: Olena Logvinova <email address hidden>
Branch: stable/8.0

Commit: 7afe4081a1276b83f82e50ab71e21a69523bd0e3
Author: Anton Chevychalov <email address hidden>
Date: Tue Apr 25 14:16:42 2017

Fix 8.0 update procedure

There is a bug around lvm, systemd and xfs. So we need
to change update procedure.

Related-Bug: #1642232

Change-Id: I99e20a768f2e9afe31d5a72875373b42ea5dc569

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.