Bug #1277
The systemd services files have various issues
Status: | Closed | Start date: | 05/15/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Jaime Melis | % Done: | 0% | |
Category: | Packaging | |||
Target version: | Release 3.6 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 3.4 |
Description
ozone.service and sunstone.service:
- Process ownership settings are not correct, remove [Exec]
one_scheduler.service:
- After requirement should be remote-fs.target and not remote_fs.target
- Process ownership settings are not correct, remove [Exec]
one.service
- After requirement should be remote-fs.target and not remote_fs.target
- Process ownership settings are not correct, remove [Exec]
- Additional conditions are needed
Associated revisions
Bug #1277: fix services files ~ In all cases using the [Exec] section is incorrect, the user and group settings are not applied as expected. ~ The name for the remote fs, i.e. nfs target is remote-fs.target and not remote_fs.target, the broken service file cuases improper service order startup and thus triggers non obvious failures. (one_scheduler.service and one.service) ~ one.service is missing conditions thus it would be possible to start the service in an inconsistent state.
Bug #1277: fix services files ~ In all cases using the [Exec] section is incorrect, the user and group settings are not applied as expected. ~ The name for the remote fs, i.e. nfs target is remote-fs.target and not remote_fs.target, the broken service file cuases improper service order startup and thus triggers non obvious failures. (one_scheduler.service and one.service) ~ one.service is missing conditions thus it would be possible to start the service in an inconsistent state.
(cherry picked from commit fdcf102cbcc92d46ec20f2d6da4d4456a1c97858)
History
#1 Updated by Ruben S. Montero about 9 years ago
- Category set to Packaging
- Status changed from New to Assigned
- Assignee set to Jaime Melis
- Target version set to Release 3.6
#2 Updated by Jaime Melis about 9 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed
Patch applied. Thank you for your contributions, Robert!