Friday, 2021-01-08

*** spatel has joined #senlin00:18
*** spatel has quit IRC00:23
*** sapd1 has quit IRC00:39
*** sapd1 has joined #senlin02:20
*** sapd1 has quit IRC02:30
*** sapd1 has joined #senlin02:43
*** sapd1 has quit IRC03:01
*** sapd1 has joined #senlin03:10
*** sapd1 has quit IRC03:13
*** spatel has joined #senlin03:22
*** hamalq has quit IRC04:01
*** sapd1 has joined #senlin05:47
*** sapd1 has quit IRC06:10
rm_workHave people run into situations where a cluster gets stuck in ERROR on delete and is essentially impossible to remove? I've got a couple in this state, wondering what my next step should be... Assuming digging through the DB should be a last resort but not sure how else to get them to go away06:19
rm_workI'll post full logs in a bit... I don't think they were especially illuminating for me at least though06:20
rm_workWe're running on master branch from... Basically now.06:20
rm_workI think latest pull from upstream master was yesterday06:21
*** sapd1 has joined #senlin06:25
*** spatel has quit IRC06:33
*** sapd1 has quit IRC06:59
*** spatel has joined #senlin07:05
*** spatel has quit IRC07:05
*** sapd1 has joined #senlin10:09
*** sapd1 has quit IRC10:14
*** sapd1 has joined #senlin10:15
*** sapd1 has quit IRC10:20
*** sapd1 has joined #senlin11:07
*** sapd1 has quit IRC11:15
*** sapd1 has joined #senlin11:21
*** sapd1 has quit IRC11:30
*** sapd1 has joined #senlin13:46
*** spatel has joined #senlin14:09
*** spatel has quit IRC15:48
dtruongI would do 'openstack cluster show' and 'openstack cluster action show' on the delete action to see if there is anything in status_reason.17:08
dtruongYou can do a cluster recover to get the cluster to ACTIVE status again and then try the delete again.17:09
*** hamalq has joined #senlin19:10
*** hamalq has quit IRC19:33
*** hamalq has joined #senlin19:33
*** spatel has joined #senlin23:52
*** spatel has quit IRC23:56

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!