| guilhermesp | hey there! ive seen a behavior for a long time now which some clusters fails to be deleted when it cannot find a stack associated to it. This is a bit problematic because it requeires a db manipulation to be able to remove the cluster | 13:55 |
|---|---|---|
| guilhermesp | is anyone aware of this? | 13:55 |
| guilhermesp | https://www.irccloud.com/pastebin/y3J7DEus/ | 14:05 |
| guilhermesp | this is basically what happens. It looks like an issue with magnum finding lbs for the cluster? | 14:05 |
| guilhermesp | i think this shoould be taken care here ? https://github.com/openstack/magnum/blob/6951ac4fc6b6178637fac7bd5d05096adb5c6bdc/magnum/common/octavia.py#L102-L105 | 14:08 |
| guilhermesp | the thing is: we are running wallaby and i can see that code in there, but it looks like is not enough to avoid the issue | 14:18 |
| guilhermesp | maybe this is happening because on the clsuter definition we still have the stack_id instead of None? | 14:21 |
| guilhermesp | https://www.irccloud.com/pastebin/oqdFpkwc/ | 14:21 |
| guilhermesp | my workaround for this for now is setting the ghost stack_id on the cluster to NULL on DB | 14:38 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!