[17:36] <bdx> hello
[17:36] <bdx> I need to remove a stuck controller
[17:36] <bdx> I think I need to do it from the db directly as I cant seem to do it from the gui
[17:36] <bdx> or cli
[17:37] <bdx> I'm wondering what table I should be deleting the controller entry from?
[17:45] <roaksoax> bdx: is this the master controller ?
[17:45] <bdx> no
[17:46] <bdx> its a non existing controller
[17:46] <bdx> that wont leave
[17:46] <bdx> leaving my maas borked for some time now
[17:46] <bdx> I need to move forward today
[17:46] <bdx> I feel I need to just remove the entry from the nodes table
[17:47] <roaksoax> bdx: why won't it just remove ?
[17:48] <bdx> its this https://bugs.launchpad.net/maas/2.4/+bug/1774538
[17:51] <bdx> I've tried this https://paste.ubuntu.com/p/kvT75jKWVm/
[17:51] <bdx> but it just doesnt seem to make sense
[17:52] <bdx> postgresql seems to be telling there is an entry that exists that doesnt exist
[17:59] <roaksoax> bdx: update the 'pool' to 'None' for that uuid and try deleting it
[17:59] <roaksoax> ?
[18:02] <bdx> roaksoax: the 'pool_id' field in the 'maasserver_node' table?
[18:03] <roaksoax> bdx: uhmm i guess so since you are looking at the db
[18:04] <bdx> roaksoax: where did you mean?
[18:09] <bdx> roaksoax: https://paste.ubuntu.com/p/B6hhKHn5RX/
[18:13] <roaksoax> bdx: so what I saw the fix wasw doing was:
[18:13] <roaksoax> +    Node = apps.get_model('maasserver', 'Node')
[18:13] <roaksoax> +    Node.objects.exclude(node_type=NODE_TYPE.MACHINE).update(pool=None)
[18:13] <bdx> yeah I saw that too
[18:15] <bdx> deleting the controller from the gui
[18:15] <bdx> I get a different result then I previously did
[18:15] <bdx> now that the pool_id = NULL
[18:16] <bdx> it doesnt error anymore
[18:16] <bdx> but now it just sits https://imgur.com/a/7HZacVx
[18:16] <bdx> lol
[18:16] <bdx> worse then an eerror
[18:16] <bdx> oh shoot
[18:16] <bdx> I spoke too soon
[18:16] <roaksoax> bdx: may be trying to power off
[18:16] <bdx> its removed
[18:17] <roaksoax> bdx: cool
[18:17] <bdx> yes
[18:17] <bdx> thats great
[18:17] <bdx> roaksoax: thanks for taking time
[18:17] <bdx> appreciated
[18:17] <roaksoax> no prob, glad to help
[18:29] <roneth99> How to force MAAS to deploy an image no matter an existing image on the disk?
[18:30] <roneth99> It appeared that MAAS skipped deploying because it sees there is already an existing OS on the disk.
[18:30] <roaksoax> roneth99: ??? MAAS doesn't skip deploying if there's a pre-installation. MAAS even tells the partitioner to wipe the superblock of all disks
[18:30] <bdx> geh, seems I have a few dangling issues
[18:30] <bdx> https://imgur.com/a/nNL36fM
[18:30] <bdx> seems now the proxy and chrony wont start
[18:31] <bdx> roaksoax: starting to feel like I should switch back to the deb now, possibly these things are snap related?
[18:32] <roaksoax> bdx: it would be matter of finding out why they dont start, but that said, should work unless something is conflicting e.g. other services inside the actual machine are owning those ports /
[18:32] <roaksoax> ?
[18:35] <roneth99> roaksoax: Monitoring the console, I can see the "Ubuntu" image got laid out... Run its things.. and eventually kicking off Cloud-Init, then finally reboot the system. But the system came back with old OS....
[18:35] <bdx> https://paste.ubuntu.com/p/2n8TGczTv7/
[18:36] <bdx> no maas apt packages are installed https://paste.ubuntu.com/p/8TPhMs3hJT/
[18:36] <bdx> il pick at this for a while and see what I can come up with
[18:36] <roneth99> roaksoax: By the way, what did you mean by "pre-installation"... Where can I check that if that exists.
[18:39] <roaksoax> bdx: check the logs on those services
[18:40] <roaksoax> roneth99: the only thing i could think of why something like that would happen is that another disk has the installation and the system is booting into that other disk
[18:40] <roaksoax> roneth99: but that would be weird, it would be helpful to have logs to better understand what's going on
[18:40] <bdx> my  chrony.log is spammed with
[18:40] <bdx> 2018-08-06T18:40:00Z chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 -DEBUG)
[18:40] <bdx> 2018-08-06T18:40:00Z Fatal error : Another chronyd may already be running (pid=1291), check /run/chronyd.pid
[18:40] <bdx> ok
[18:40] <bdx> so that makes sense
[18:40] <bdx> what you said
[18:43] <bdx> ahhh looks like I had dangling squid and chrony from the deb install
[18:43] <bdx> that makes sense
[18:43] <bdx> ok
[18:43] <bdx> thanks again!
[18:51] <roneth99> roaksoax: I am erasing the disk and will attempt another try.... If I see the same issue again, what logs would be usefule for you? maas.log, rackd.log, regiond.log ?
[22:06] <xygn4l> roaksoax: plans to retire IPMI and provide redfish for Dell? not comfortable using protocol with an open cve since 2003.  security teams REALLY hate it.
[22:37] <roaksoax> xygn4l: as of today, we have no plans, unless of course it comes through customers