LoadBalancerIDToErrorOnRevertTask is a task to set the LB to ERROR on revert, the final LB's status is PENDING_CREATE, which suggests that
LoadBalancerIDToErrorOnRevertTask's revert didn't be called. In other words, I should be hitting this bug as well that the revert of a LB creation flow may not be complete, leading to the retry mechanism not functioning properly. I was considering the following options:
1, I am not sure if increasing amp_active_wait_sec to avoid using retry mechanism could serve as a workaround
2, I am not sure if using only standby instead of active/standby could serve as a workaround
3, do you think only this fix (https://review.opendev.org/c/openstack/taskflow/+/900746) might be sufficient to address this bug as well, because I saw that you were trying to remove retry and then saying it was necessary above.
Hi @gthiemonge
LoadBalancerIDT oErrorOnRevertT ask is a task to set the LB to ERROR on revert, the final LB's status is PENDING_CREATE, which suggests that oErrorOnRevertT ask's revert didn't be called. In other words, I should be hitting this bug as well that the revert of a LB creation flow may not be complete, leading to the retry mechanism not functioning properly. I was considering the following options:
LoadBalancerIDT
1, I am not sure if increasing amp_active_wait_sec to avoid using retry mechanism could serve as a workaround
2, I am not sure if using only standby instead of active/standby could serve as a workaround
3, do you think only this fix (https:/ /review. opendev. org/c/openstack /taskflow/ +/900746) might be sufficient to address this bug as well, because I saw that you were trying to remove retry and then saying it was necessary above.