=== frankban|afk is now known as frankban [08:54] Bug #1757991 opened: [2.3.0] metadat URL is [::1] when no port is specified for ipv4 IP in rackd.conf [13:19] Bug #1731956 changed: [2.3rc2, UI] Make all the font styles consistent in the summary cards <2.3qa> === edmz_ is now known as edmz === edmz- is now known as edmz [15:46] jhi/win 4 [15:46] err === frankban is now known as frankban|afk [20:47] roaksoax: The nodes run cloud-init every time they boot, correct? I'm not able to get into a node with the SSH key that's set on the user who owns the node... Even tried power off/power on, still no go. Any local console login available? [20:50] wdennis: is this on what state ? [20:51] "Deployed" [20:52] wdennis: check /var/log/maas/rsyslog/// and see if there's any error ? [20:57] roaksoax: No errors from what I can see... [20:58] wdennis: anything in the console ? it would be strange for it to not at all allow you to log in [20:58] wdennis: on ubuntu@ [20:58] with your ssh key [21:02] roaksoax: Noting showing on the console, if that's what you meant... [21:02] Tried local (cos) login as "ubuntu" w/ passed "ubuntu", not allowing login [21:03] Here's last ~50 lines from /var/log/maas/rsyslog///messages: https://bpaste.net/show/8eb6b0dc82d0 [21:05] When I try to login: [21:05] itss-mac-mini:~ itsgroup$ ssh ubuntu@192.168.1.141 Permission denied (publickey). [21:18] wdennis: maybe the key is malformed and fails to import it ? [21:19] It was working before... I rebooted the node, and it no longer worked. [21:23] wdennis: ok, so you deployed the machine, ssh, it worked, rebooted, and all of the sudden you were unable to ssh in ? [21:24] That's correct [21:32] wdennis: that seems veeeeeeeeeeery weird [21:32] wdennis: what version of MAAs are you using ? [21:33] wdennis: and what are you deploying ? [21:52] Running MAAS 2.3.0 (6434-gd354690-0ubuntu1~16.04.1) [21:52] Deploying U16.04 [21:54] roaksoax: Here's a question: can you take a running machine (or a deployed machine that's powered off), and directly "commission" it? [21:55] Seems that I could from the main "Nodes" screen (checkbox-select the node, then choose "Commission" from the "Take action" menu) [21:56] However, when I'm in the specific node screen (by clicking on the node name from the Nodes screen), I do not see "Commission" in the list of available actions [21:58] The reason I ask is, this is a test setup I'm running, and I could just "reset" the node by commissioning it, then re-deploy it [21:59] Instead of the usual "Release" of the node, which runs a disk wipe, then re-commissioning it [22:01] Aha, the answer seems to be "no, you can't"... Tried to Commission it from the Nodes screen, and got "1 node cannot be commissioned. To proceed, update your selection." [23:14] Bug #1758193 opened: [2.4] Auto-assigned IP doesn't get written as a hostmap, causing 'deploying' machine to use a IP from dynamic range [23:17] Bug #1748052 changed: [2.4, devel] ] Unable to write to plugin cache /usr/lib/python3/dist-packages/twisted/plugins/dropin.cache: error number 13 [23:17] Bug #1749962 changed: [2.4] Cannot allocate memory when DescribePowerTypes happen [23:23] Bug #1748055 changed: [2.4, devel] INTERNAL_SERVER_ERROR While commissioning/testing [23:29] Bug #1748929 changed: [2.4, CI] [critical] Failure when cancelling hook