On Wed, Mar 08, 2017 at 06:41:58PM -0000, Pas wrote:
> Feel free to close this, I mainly reported this so maybe others will
> find the workaround useful.
I think this bug should remain open until we either fix the race or we
replace the daemon start with the private one as planned. Since the bug
is currently still present and valid, and is fundamentally a different
underlying issue from the other one. For example, if we struggled to fix
the policy-rc.d issue for whatever reason, we might still be introduce a
"wait for mysqld to be ready or time out" call before running
mysql_upgrade, fixing this bug but not the other.
On Wed, Mar 08, 2017 at 06:41:58PM -0000, Pas wrote:
> Feel free to close this, I mainly reported this so maybe others will
> find the workaround useful.
I think this bug should remain open until we either fix the race or we
replace the daemon start with the private one as planned. Since the bug
is currently still present and valid, and is fundamentally a different
underlying issue from the other one. For example, if we struggled to fix
the policy-rc.d issue for whatever reason, we might still be introduce a
"wait for mysqld to be ready or time out" call before running
mysql_upgrade, fixing this bug but not the other.