Following a recent update to the Compose plug-in, I get the following error (in the attached file) when I try to apply my configuration. Rebooting didn't resolve the problem either. Any pointers on where I should start looking to fix things?
Unable to apply configuration following update to compose plug-in
-
- OMV 7.x
- resolved
- ultimaterez
-
-
chente
Approved the thread. -
This wasn't caused by the plugin. Looks like your salt cache is corrupt or missing. What is the output of: sudo omv-salt stage run prepare
-
debian:
----------
ID: run_state_patch
Function: salt.state
Result: True
Comment: States ran successfully. No changes made to debian.
Started: 15:45:12.860387
Duration: 62.398 ms
Changes:
----------
ID: sync_runners
Function: salt.runner
Name: saltutil.sync_runners
Result: True
Comment: Runner function 'saltutil.sync_runners' executed.
Started: 15:45:12.922841
Duration: 3245.279 ms
Changes:
----------
return:
----------
ID: sync_modules
Function: salt.runner
Name: saltutil.sync_modules
Result: True
Comment: Runner function 'saltutil.sync_modules' executed.
Started: 15:45:16.168228
Duration: 3203.805 ms
Changes:
----------
return:
----------
ID: sync_states
Function: salt.runner
Name: saltutil.sync_states
Result: True
Comment: Runner function 'saltutil.sync_states' executed.
Started: 15:45:19.372144
Duration: 3221.589 ms
Changes:
----------
return:
----------
ID: populate_pillar
Function: salt.runner
Name: omv.populate_pillar
Result: False
Comment: Runner function 'omv.populate_pillar' failed.
Started: 15:45:22.593957
Duration: 3214.978 ms
Changes:
----------
return:
Exception occurred in runner omv.populate_pillar: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/client/mixins.py", line 388, in low
data["return"] = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 149, in __call__
return self.loader.run(run_func, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1234, in run
return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1249, in _run_as
ret = _func_or_method(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/var/cache/salt/master/extmods/runners/omv.py", line 40, in populate_pillar
with open(filename, 'w') as fd:
^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/srv/pillar/omv/default.sls'
----------
ID: run_state_sync
Function: salt.state
Result: True
Comment: States ran successfully. Updating debian.
Started: 15:45:25.809031
Duration: 3251.145 ms
Changes:
debian:
----------
ID: clear_cache
Function: module.run
Result: True
Comment: saltutil.clear_cache: True
Started: 15:45:25.886631
Duration: 18.505 ms
Changes:
----------
saltutil.clear_cache:
True
----------
ID: sync_grains
Function: saltutil.sync_grains
Result: True
Comment: Updated grains.
Started: 15:45:25.905526
Duration: 1087.477 ms
Changes:
----------
grains:
- grains.omv
----------
ID: sync_states
Function: saltutil.sync_states
Result: True
Comment: Updated states.
Started: 15:45:26.993084
Duration: 1032.768 ms
Changes:
----------
states:
- states.omv_dpkg
----------
ID: sync_modules
Function: saltutil.sync_modules
Result: True
Comment: Updated modules.
Started: 15:45:28.025930
Duration: 1033.789 ms
Changes:
----------
modules:
- modules.omv_conf
- modules.omv_utils
Summary for debian
------------
Succeeded: 4 (changed=4)
Failed: 0
------------
Total states run: 4
Total run time: 3.173 s
Summary for debian
------------
Succeeded: 5 (changed=5)
Failed: 1
------------
Total states run: 6
Total run time: 16.199 s
[ERROR ] {'return': 'Exception occurred in runner omv.populate_pillar: Traceback (most recent call last):\n File "/usr/lib/python3/dist-packages/salt/client/mixins.py", line 388, in low\n data["return"] = func(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 149, in __call__\n return self.loader.run(run_func, *args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1234, in run\n return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1249, in _run_as\n ret = _func_or_method(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/var/cache/salt/master/extmods/runners/omv.py", line 40, in populate_pillar\n with open(filename, \'w\') as fd:\n ^^^^^^^^^^^^^^^^^^^\nFileNotFoundError: [Errno 2] No such file or directory: \'/srv/pillar/omv/default.sls\'\n'}
-
-
Seems strange that /srv/pillar doesn't exist. Do you do anything be installing the plugin update?
sudo mkdir -p /srv/pillar/omv
sudo touch /srv/pillar/omv/default.sls
sudo chown -R root:root /srv/pillar/omv
sudo omv-salt stage run prepare
-
To the extent of my memory I didn't do anything prior to updating the plugin. It was about a week or so ago, so I don't recall, but I don't normally do much in that regard beyond clicking the available options to update things.
Here are the the results of the omv-salt stage run prepare:
Code
Display Moredebian: ---------- ID: run_state_patch Function: salt.state Result: True Comment: States ran successfully. No changes made to debian. Started: 16:36:19.946770 Duration: 60.731 ms Changes: ---------- ID: sync_runners Function: salt.runner Name: saltutil.sync_runners Result: True Comment: Runner function 'saltutil.sync_runners' executed. Started: 16:36:20.007555 Duration: 3226.021 ms Changes: ---------- return: ---------- ID: sync_modules Function: salt.runner Name: saltutil.sync_modules Result: True Comment: Runner function 'saltutil.sync_modules' executed. Started: 16:36:23.233692 Duration: 3185.772 ms Changes: ---------- return: ---------- ID: sync_states Function: salt.runner Name: saltutil.sync_states Result: True Comment: Runner function 'saltutil.sync_states' executed. Started: 16:36:26.419549 Duration: 3200.24 ms Changes: ---------- return: ---------- ID: populate_pillar Function: salt.runner Name: omv.populate_pillar Result: True Comment: Runner function 'omv.populate_pillar' executed. Started: 16:36:29.619997 Duration: 3414.696 ms Changes: ---------- return: True ---------- ID: run_state_sync Function: salt.state Result: True Comment: States ran successfully. Updating debian. Started: 16:36:33.034840 Duration: 3205.288 ms Changes: debian: ---------- ID: clear_cache Function: module.run Result: True Comment: saltutil.clear_cache: True Started: 16:36:33.100343 Duration: 10.919 ms Changes: ---------- saltutil.clear_cache: True ---------- ID: sync_grains Function: saltutil.sync_grains Result: True Comment: Updated grains. Started: 16:36:33.111663 Duration: 1087.802 ms Changes: ---------- grains: - grains.omv ---------- ID: sync_states Function: saltutil.sync_states Result: True Comment: Updated states. Started: 16:36:34.199547 Duration: 1020.686 ms Changes: ---------- states: - states.omv_dpkg ---------- ID: sync_modules Function: saltutil.sync_modules Result: True Comment: Updated modules. Started: 16:36:35.220308 Duration: 1019.363 ms Changes: ---------- modules: - modules.omv_conf - modules.omv_utils Summary for debian ------------ Succeeded: 4 (changed=4) Failed: 0 ------------ Total states run: 4 Total run time: 3.139 s Summary for debian ------------ Succeeded: 6 (changed=5) Failed: 0 ------------ Total states run: 6 Total run time: 16.293 s -
That fixed that issues.
What is the output of:
dpkg -l | grep openme
sudo apt-get -f install
-
-
ii openmediavault 7.7.7-1 all openmediavault - The open network attached storage solution
ii openmediavault-apt 7.0.2-1 all openmediavault APT management plugin
ii openmediavault-apttool 7.1.1 all apt tool plugin for OpenMediaVault.
ii openmediavault-compose 7.5.2 all OpenMediaVault compose plugin
ii openmediavault-fail2ban 7.0.1 all OpenMediaVault Fail2ban plugin
ii openmediavault-kernel 7.1.11 all kernel package
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-omvextrasorg 7.0.2 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-sharerootfs 7.0-1 all openmediavault share root filesystem plugin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
-
If you still see the apply button in the omv web interface, click it. Otherwise, what is the output of: sudo omv-salt deploy run compose
-
I did try to click apply, but it gave me an error again. I've attached the error output.
I've also attached the output from the deploy command.
-
-
I think whatever caused /srv/pillar to be removed (possible failing os disk?) is going to cause multiple problems.
I would try: sudo apt-get install --reinstall openmediavault
Hopefully that replaces the missing files.
-
That did the trick! I was able to apply the configuration without issue! I did a reboot to make sure that everything came back up without a hitch and so far so good. I checked and /srv/pillar was still there, so I think that did the trick for me. I really appreciate the help getting back in tip-top shape!
-
ultimaterez
Added the Label resolved
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!