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

reboot hosts handler occurs without changes #57

Open
xunholy opened this issue Aug 12, 2020 · 4 comments
Open

reboot hosts handler occurs without changes #57

xunholy opened this issue Aug 12, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@xunholy
Copy link
Member

xunholy commented Aug 12, 2020

Details

The hosts should only need to be reboot for significant changes that require them to be restarted.

Currently, without any changes they'll still trigger into a host reboot which isn't intended.

@xunholy xunholy added the bug Something isn't working label Aug 12, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@xunholy
Copy link
Member Author

xunholy commented Aug 14, 2020

After doing several trials what seems to be the offending notify that triggers the host reboot handler is the following task:

- name: install log2ram
  command: /bin/sh ./install.sh
  args:
    chdir: '/opt/log2ram'
  register: log2ram
  changed_when: '"Reboot to activate log2ram" in log2ram.stdout'
  notify: reboot hosts

@xunholy
Copy link
Member Author

xunholy commented Aug 26, 2020

Tested consecutive installs for log2ram to determine if it was idempotent, however, each install will still require a restart or at least prompt the user that a restart is required.

pi@k8s-master-01:/opt/log2ram$ sudo /bin/sh ./install.sh
#####         Reboot to activate log2ram         #####
##### edit /etc/log2ram.conf to configure options ####
pi@k8s-master-01:/opt/log2ram$ sudo /bin/sh ./install.sh
#####         Reboot to activate log2ram         #####
##### edit /etc/log2ram.conf to configure options ####

@xunholy
Copy link
Member Author

xunholy commented Aug 26, 2020

This might potentially be solved if we installed with the recommended official method rather than running the shell script as described here: https://github.com/azlux/log2ram#with-apt-recommended

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

No branches or pull requests

1 participant