action #105960
Updated by jbaier_cz almost 3 years ago
## Observation
```
Feb 04 10:55:19 openqa systemd[1]: Starting Certificate Update Runner for Dehydrated...
Feb 04 10:55:19 openqa dehydrated[6052]: # INFO: Using main config file /etc/dehydrated/config
Feb 04 10:55:19 openqa dehydrated[6052]: # INFO: Using additional config file /etc/dehydrated/config.d/suse-ca.sh
Feb 04 10:55:19 openqa dehydrated[6052]: # INFO: Running /usr/bin/dehydrated as dehydrated/dehydrated
Feb 04 10:55:19 openqa sudo[6052]: root : PWD=/ ; USER=dehydrated ; GROUP=dehydrated ; COMMAND=/usr/bin/dehydrated --cron
Feb 04 10:55:20 openqa dehydrated[6427]: {}
Feb 04 10:55:20 openqa systemd[1]: dehydrated.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 10:55:20 openqa systemd[1]: dehydrated.service: Failed with result 'exit-code'.
Feb 04 10:55:20 openqa systemd[1]: Failed to start Certificate Update Runner for Dehydrated.
```
## Acceptance criteria
- **AC1**: OSD is automatically dehydrated on a regular schedule
## Suggestions
- Add a simple systemd timer
- Use service.running as a prerequisite state in salt c.f. https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/certificates/dehydrated.sls#L36
- See if a new account is needed
- Consider `request_failure()` hook inside https://github.com/dehydrated-io/dehydrated/blob/master/docs/examples/hook.sh
## Out of scope
- qem dashboard (different ticket)