/srv/irclogs.ubuntu.com/2018/03/22/#maas.txt

=== frankban|afk is now known as frankban
mupBug #1757991 opened: [2.3.0] metadat URL is [::1] when no port is specified for ipv4 IP in rackd.conf <cpe-onsite> <MAAS:New> <https://launchpad.net/bugs/1757991>08:54
mupBug #1731956 changed: [2.3rc2, UI] Make all the font styles consistent in the summary cards <2.3qa> <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1731956>13:19
=== edmz_ is now known as edmz
=== edmz- is now known as edmz
roaksoaxjhi/win 415:46
roaksoaxerr15:46
=== frankban is now known as frankban|afk
wdennisroaksoax: 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:47
roaksoaxwdennis: is this on what state ?20:50
wdennis"Deployed"20:51
roaksoaxwdennis: check /var/log/maas/rsyslog/<machine-name>/<date>/<messages> and see if there's any error ?20:52
wdennisroaksoax: No errors from what I can see...20:57
roaksoaxwdennis: anything in the console ? it would be strange for it to not at all allow you to log in20:58
roaksoaxwdennis: on ubuntu@20:58
roaksoaxwith your ssh key20:58
wdennisroaksoax: Noting showing on the console, if that's what you meant...21:02
wdennisTried local (cos) login as "ubuntu" w/ passed "ubuntu", not allowing login21:02
wdennisHere's last ~50 lines from /var/log/maas/rsyslog/<machine-name>/<date>/messages: https://bpaste.net/show/8eb6b0dc82d021:03
wdennisWhen I try to login:21:05
wdennisitss-mac-mini:~ itsgroup$ ssh ubuntu@192.168.1.141 Permission denied (publickey).21:05
roaksoaxwdennis: maybe the key is malformed and fails to import it ?21:18
wdennisIt was working before... I rebooted the node, and it no longer worked.21:19
roaksoaxwdennis: ok, so you deployed the machine, ssh, it worked, rebooted, and all of the sudden you were unable to ssh in ?21:23
wdennisThat's correct21:24
roaksoaxwdennis: that seems veeeeeeeeeeery weird21:32
roaksoaxwdennis: what version of MAAs are you using ?21:32
roaksoaxwdennis: and what are you deploying ?21:33
wdennisRunning MAAS 2.3.0 (6434-gd354690-0ubuntu1~16.04.1)21:52
wdennisDeploying U16.0421:52
wdennisroaksoax: Here's a question: can you take a running machine (or a deployed machine that's powered off), and directly "commission" it?21:54
wdennisSeems that I could from the main "Nodes" screen (checkbox-select the node, then choose "Commission" from the "Take action" menu)21:55
wdennisHowever, 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 actions21:56
wdennisThe 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 it21:58
wdennisInstead of the usual "Release" of the node, which runs a disk wipe, then re-commissioning it21:59
wdennisAha, 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."22:01
mupBug #1758193 opened: [2.4] Auto-assigned IP doesn't get written as a hostmap, causing 'deploying' machine to use a IP from dynamic range <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1758193>23:14
mupBug #1748052 changed: [2.4, devel] ] Unable to write to plugin cache /usr/lib/python3/dist-packages/twisted/plugins/dropin.cache: error number 13 <MAAS:Fix Released> <https://launchpad.net/bugs/1748052>23:17
mupBug #1749962 changed: [2.4] Cannot allocate memory when DescribePowerTypes happen <performance> <MAAS:Fix Released> <https://launchpad.net/bugs/1749962>23:17
mupBug #1748055 changed: [2.4, devel] INTERNAL_SERVER_ERROR While commissioning/testing <MAAS:Invalid> <https://launchpad.net/bugs/1748055>23:23
mupBug #1748929 changed: [2.4, CI]  [critical] Failure when cancelling hook <performance> <MAAS:Fix Released> <https://launchpad.net/bugs/1748929>23:29

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!