[01:49] <thetrav> is there any way in the maas UI for me to configure the MTU for an interface?
[03:53] <mup> Bug #1589789 opened: is it impossible to add 'A' type record for a host which is not managed by MAAS? <MAAS:New> <https://launchpad.net/bugs/1589789>
[04:26] <mup> Bug #1567249 changed: 'missing_packages' missing and causes traceback <MAAS:Expired> <https://launchpad.net/bugs/1567249>
[04:26] <mup> Bug #1567614 changed: [MAAS 2.0 ] does not add default gw route to nodes. <MAAS:Expired> <https://launchpad.net/bugs/1567614>
[04:46] <thetrav> ok, so couldn't find anything in the UI, found something in the cli around the vlan, which I assume is something of a default
[04:46] <thetrav> managed to update it, however restarting instances in that vlan is not getting them a new MTU
[04:50] <thetrav> so far as the CLI is concerned, my interfaces should have an effective MTU of 2000
[04:50] <thetrav> so far as my nodes are concerned, their interfaces have an MTU of 1500
[07:47] <jojden> I am getting following error, "Specify a storage device to be able to deploy this node."
[07:47] <jojden> how to Specify a storage device
[07:47] <jojden> Specify a storage device to be able to deploy this node.
[07:47] <jojden> Mount the root '/' filesystem to be able to deploy this node.
[09:58] <jojden> hi
[10:21] <brendand> jojden, i'm not sure that's really an error - it might be a ui bug. possibly a little confusing
[10:22] <jojden> brendand
[10:22] <jojden> ok
[10:23] <jojden> but under File system it showing that
[10:23] <jojden> No filesystems defined.
[10:23] <brendand> jojden, has the node been commisioned yet?
[10:23] <jojden> its in commisioning state
[10:26] <jojden> @brendand
[10:27] <jojden> Node commissioning - 'cloudinit' running modules for final	Tue, 07 Jun. 2016 09:45:04
[10:27] <jojden> Node commissioning - 'cloudinit' config-power-state-change ran successfully	Tue, 07 Jun. 2016 09:45:03
[10:27] <brendand> once it's finished that should be gone
[10:28] <jojden> ok
[10:29] <jojden> usally how much time will take for the commissioning ?
[10:29] <brendand> should be quick
[10:31] <jojden> hmmm
[10:31] <jojden> but its taking more time
[10:32] <jojden> so something is wrong with that
[10:32] <jojden> :(
[12:25] <mup> Bug #1589951 opened: why pxe booted node is stucked in commissioning status <MAAS:New> <https://launchpad.net/bugs/1589951>
[12:43] <mup> Bug #1589951 changed: why pxe booted node is stucked in commissioning status <MAAS:New> <https://launchpad.net/bugs/1589951>
[12:46] <mup> Bug #1589951 opened: why pxe booted node is stucked in commissioning status <MAAS:New> <https://launchpad.net/bugs/1589951>
[14:25] <mup> Bug #1590021 opened: [2.0] Cannot create an IP reservation with a hostname <MAAS:New for lamont> <https://launchpad.net/bugs/1590021>
[15:52] <gimmic> man this curtin storage bug is really chappin my ass
[15:55] <gimmic> wonder if I should move over to the 2.0 betas
[15:59] <kiko> gimmic, did you make any progress on finding out what the issue is?
[15:59] <kiko> if not, smoser, do you have some time to look at it with gimmic? if not, someone on your team that knows their stuff?
[16:19] <gimmic> I've got a couple of nodes exhibiting the problem, looking at the logs doesn't tell me much
[16:43] <kiko> gimmic, they fail to deploy randomly when using flat only, right?
[16:49] <smoser> gimmic, did you file a bug ?
[16:54] <LiftedKilt> does maas support ed25519 keys?
[16:55] <kiko> LiftedKilt, for ssh do you mean?
[16:55] <LiftedKilt> kiko: yes
[16:55] <LiftedKilt> when I try to add my key it tells me "Invalid SSH public key."
[16:55] <kiko> i.e. when setting up ssh accounts for the ubuntu/centos users, allow specifying ed25519 public keys?
[16:55] <kiko> I think it does not
[16:55] <kiko> LiftedKilt, could you file a bug?
[16:56] <LiftedKilt> sure
[16:56] <LiftedKilt> kiko: while I have you here - is there a way to have maas change hostnames?
[16:57] <kiko> LiftedKilt, of the deployed nodes? or pre-deployment?
[16:57] <LiftedKilt> either
[16:57] <kiko> pre-deployment sure, just edit the node
[16:57] <LiftedKilt> seriously? haha how did I miss that
[16:57] <LiftedKilt> thanks
[16:58] <kiko> LiftedKilt, post-deployment possibly, but even if so it obviously won't be reflected in the deployed node  (because we don't have a running machine agent nor cloud-init reconfiguration)
[16:59] <LiftedKilt> right - yeah pre-deployment is perfect
[17:02] <mup> Bug #1590081 opened: when setting up ssh accounts for the key injection, allow specifying ed25519 and ecdsa public keys <MAAS:New> <https://launchpad.net/bugs/1590081>
[17:02] <kiko> LiftedKilt, thanks for filing a solid bug report
[17:04] <LiftedKilt> kiko: for sure
[17:39] <smoser> ltrager, https://code.launchpad.net/~smoser/maas-images/trunk.fix-powerpc-mining/+merge/296705 would be nice if you had a chance.
[17:41] <gimmic> kiko: it doesn't seem to be limited to flat only.
[17:43] <kiko> gimmic, okay. so let me restate.
[17:43] <kiko> gimmic, they fail to deploy randomly when using any layout, right?
[17:43] <kiko> your stated success rate was 1/3?
[17:45] <gimmic> or so, yeah. If I knew where in the logs to look to tshoot I would, the layout just isn't very clear (or if there's increased debug options)
[17:50] <kiko> smoser, where should be look at the logs?
[17:50] <kiko> smoser, s/be/he
[19:41] <mup> Bug #1590121 opened: [xenial][maas beta5] [arm64] system tries to enlist when I commission.  <MAAS:Triaged by newell-jensen> <https://launchpad.net/bugs/1590121>
[20:41] <mup> Bug #1590144 opened: core count not updated during commissioning <v-pil> <MAAS:New> <https://launchpad.net/bugs/1590144>