Browse Source

Fix loopback service status

Currently when Salt starts setup-loopback-device service
systemd executes losetup command and even if it worked
successfully, systemd marks service as inactive(dead).
And Salt considers service as dead. In order to fix
this behavior, we need to add RemainAfterExit=true to
loopback systemd unit template.

Other changes:
.gitreview added

Related Prod: https://mirantis.jira.com/browse/PROD-11760

Change-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e
pull/110/head
Mykyta Karpin 7 years ago
parent
commit
40edd5837f
2 changed files with 7 additions and 0 deletions
  1. +5
    -0
      .gitreview
  2. +2
    -0
      linux/files/setup-loopback-device.systemd

+ 5
- 0
.gitreview View File

@@ -0,0 +1,5 @@
[gerrit]
host=gerrit.mcp.mirantis.net
port=29418
project=salt-formulas/linux


+ 2
- 0
linux/files/setup-loopback-device.systemd View File

@@ -8,6 +8,8 @@ Wants=systemd-udev-settle.service
[Service]
{# The command is prefixed with '-' to consider it a success if the loopback device is already setup #}
ExecStart=-/sbin/losetup {{ device_name }} {{ file }}
{# In order to Salt can recognize oneshot service as running, we need it to remain active after it exited #}
RemainAfterExit=true
Type=oneshot

[Install]

Loading…
Cancel
Save