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
Squid & DansGuardian block upgrading to BIG-sized local_vars.yml #512
Comments
(Excerpt from http://lists.laptop.org/pipermail/server-devel/2017-November/008221.html) |
Upgrading post install has always been problematic that is why in the past it was the kitchen sink approach with no option not to install some services while default_vars just lied about being able to do so, just leaving the services disabled. Now with the slimmed down installs in place moving to big should really be a install time option by starting with "big" or "from scratch". There is no issue if you start with the services to be installed from the start, and with a bit of jiggling I can restore the selective post install option, I'm debating if it's worth the effort. |
Apparently fixed. We can re-open if nec. |
Expected behavior and actual behavior.
./iiab-install fails in either of these 2 ways:
TASK [network : Enable DansGuardian] *******************************************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service dansguardian: host"}
or
TASK [network : Enable Squid service] ******************************************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service squid: host"}
Steps to reproduce the problem.
Run "./iiab-install --reinstall" after upgrading a standard install from MEDIUM-sized local_vars.yml to BIG-sized local_vars.yml.
This same problem occurred when upgrading a MIN-sized local_vars.yml to BIG-sized.
Specifications like the version of the IIAB, operating system version, or hardware details.
IIAB 6.5 Preview 2 (and current master) on fully-updated Raspbian Lite 2017-09-07 on RPi3.
The text was updated successfully, but these errors were encountered: