[RFE] Can't specify an error type on LBaaS objects that fail to provision

[Matthew Geldert]

LBaaSv2 objects have a provisioning_status field that can indicate when provisioning has failed, but there is no way to describe to the user what the error was. The ability to specify an error message as a parameter to the BaseManagerMixin.failed_completion() function that can then be returned in "show" calls to the object would save users and administrators a lot of time when debugging issues.

[Carl Baldwin (carl-baldwin)]

Assigning to Brandon to triage because I don't know a lot about lbaas.

[Brandon Logan (brandon-logan)]

This actually something v1 had that v2 does not have and probably would be something useful. In v1 I believe it was called status_description. I'll add the rfe tag because this is an rfe.

[Armando Migliaccio (armando-migliaccio)]

A description field may be useful but the degree of usefulness depends on the level of details provided. I am not sure that short description will save *a lot* of time when debugging, but it can definitely provide clues to where to look.

[Armando Migliaccio (armando-migliaccio)]

This seems nice to have, but I wonder if the LBaaS/Octavia team would like to prioritize this.

[Brandon Logan (brandon-logan)]

We talked a bit yesterday about it in the octavia meeting. Everyone agreed it'd be great to have but I didn't get the sense that it would be a higher priority over the other high priorities. That was just the feeling I got though, and also my opinion that it's not a higher priority.

[Armando Migliaccio (armando-migliaccio)]

Brandon, thanks. Let's keep it on the backburner for now.

[Gregory Thiemonge (gthiemonge)]

Abandoned after re-enabling the Octavia launchpad.