You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How familiar are you with the the source code relevant to this issue?:
{Replace this with a number from 1 to 10. 1 being not familiar, and 10 being very familiar}
7
Expected behaviour:
{A detailed description of what you expect to see}
pihole update code for 5 release checks for SELinux and exits if it is enabled, however there is also a shell variable PIHOLE_SELINUX. If this is set pihole -up continues with SELinux either enabled or enabled and in enforcing mode. I understand there are issues with pihole as is with SELinux and have taken measures to let it function with SELinux enforcing to a degree I can live with.
IMHO this variable should be either mentioned by the installer in update mode or documented. I just stumbled upon it in your source code.
Actual behaviour:
pihole -up on 4->5 updates pihole and the webinterface but not FTL, and thus breaks itself.
{A detailed description and/or screenshots of what you do see}
In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}
How familiar are you with the the source code relevant to this issue?:
{Replace this with a number from 1 to 10. 1 being not familiar, and 10 being very familiar}
7
Expected behaviour:
{A detailed description of what you expect to see}
pihole update code for 5 release checks for SELinux and exits if it is enabled, however there is also a shell variable PIHOLE_SELINUX. If this is set pihole -up continues with SELinux either enabled or enabled and in enforcing mode. I understand there are issues with pihole as is with SELinux and have taken measures to let it function with SELinux enforcing to a degree I can live with.
IMHO this variable should be either mentioned by the installer in update mode or documented. I just stumbled upon it in your source code.
Actual behaviour:
pihole -up on 4->5 updates pihole and the webinterface but not FTL, and thus breaks itself.
{A detailed description and/or screenshots of what you do see}
Steps to reproduce:
pihole -up on any system with SELinux enabled.
{Detailed steps of how we can reproduce this}
export PIHOLE_SELINUX=true
pihole -up
Succes
pihole -up
Failure
Debug token provided by uploading
pihole -d
log:{Alphanumeric token}
Troubleshooting undertaken, and/or other relevant information:
{Steps of what you have done to fix this}
The text was updated successfully, but these errors were encountered: