It happens once in 4 -- 6 deployment attempts, I don't think that qualifies as "rather rare"
> which is very hard to fix
Just because the bug is "hard to fix" doesn't mean it's invalid.
> it is irrational to spend time on it
It's irrational to spend time arguing that bugs should not be fixed.
> In case a user experiences it, our verdict is "the issue should be manually resolved by operations people".
In reality these issues get resolved as "bye-bye Fuel, we'll pay our $$$ to Amazon/Red Hat/Canonical".
And until you guys take the quality of the product seriously, it's going to happen that way ever and ever again.
Dmitry,
> That is a rather rare case
It happens once in 4 -- 6 deployment attempts, I don't think that qualifies as "rather rare"
> which is very hard to fix
Just because the bug is "hard to fix" doesn't mean it's invalid.
> it is irrational to spend time on it
It's irrational to spend time arguing that bugs should not be fixed.
> In case a user experiences it, our verdict is "the issue should be manually resolved by operations people".
In reality these issues get resolved as "bye-bye Fuel, we'll pay our $$$ to Amazon/Red Hat/Canonical".
And until you guys take the quality of the product seriously, it's going to happen that way ever and ever again.