I wish :). The -E is needed because we need to pass down the KOLLA_ env variables. Kolla fails if it does not have the KOLLA_COPY_STRATEGY var, for example.
The reason we talk to dbus is probably more to do with pam than anything else (I quickly checked the sudo code and did not see explicit dbus calls, so I am tending to think that we can prolly fix this with either a selinux policy change and/or a pam change inside the containers.
We actually did something similar for rabbit via Ic0789da4645a4ee186d82ad7d943de78d4d5c443
I am wondering if we should try something like that but more global.
I wish :). The -E is needed because we need to pass down the KOLLA_ env variables. Kolla fails if it does not have the KOLLA_COPY_STRATEGY var, for example.
The reason we talk to dbus is probably more to do with pam than anything else (I quickly checked the sudo code and did not see explicit dbus calls, so I am tending to think that we can prolly fix this with either a selinux policy change and/or a pam change inside the containers.
We actually did something similar for rabbit via Ic0789da4645a4e e186d82ad7d943d e78d4d5c443
I am wondering if we should try something like that but more global.