Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updog check-update return code #748

Closed
tjkirch opened this issue Feb 18, 2020 · 3 comments · Fixed by #772
Closed

updog check-update return code #748

tjkirch opened this issue Feb 18, 2020 · 3 comments · Fixed by #772
Assignees
Labels
type/bug Something isn't working

Comments

@tjkirch
Copy link
Contributor

tjkirch commented Feb 18, 2020

updog.service runs updog check-update which returns 1 if there are no new updates. That's a healthy state for the system, so the service shouldn't be marked as failed (and the system as degraded) when there are no updates.

We need a way for the systemd service not to fail when there are no updates. We should either:

  • Always make it return 0 when there are no updates
  • Make it return 0 unless a --fail-if-no-updates flag is given
  • Make it return 0 if a --allow-no-updates flag is given
@tjkirch tjkirch added type/bug Something isn't working good first issue labels Feb 18, 2020
@tjkirch
Copy link
Contributor Author

tjkirch commented Feb 18, 2020

Or, @sam-aws suggests that we could just remove the service for now, since it's just informational.

@sam-aws
Copy link
Contributor

sam-aws commented Feb 18, 2020

Always make it return 0 when there are no updates

NAK, this was the whole drama with dogswatch

Make it return 0 unless a --fail-if-no-updates flag is given
Make it return 0 if a --allow-no-updates flag is given

This feels like adding too much complexity to the operation, but I can see some utility in at least checking if the TUF repo is available. Then again the --all option would do that too.

The updog service was added way early on as more of a placeholder than anything else; I'd lean towards removing it and replacing it with something that advertises boot/update success (eg. something that calls #674). That could even be covered by the existing mark-successful-boot.service.

@iliana
Copy link
Contributor

iliana commented Feb 22, 2020

+1 to removing updog.service

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants