| mup | Bug #1587201 opened: MAAS 2.0 fails to format all bcache partitions <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1587201> | 01:21 |
|---|---|---|
| mup | Bug #1587201 changed: MAAS 2.0 fails to format all bcache partitions <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1587201> | 01:27 |
| === Guest68352 is now known as spammy | ||
| === frankban|afk is now known as frankban | ||
| capslockwizard | I've been looking around the manual of maas but I can't seem to find any documentation on the images that maas uses | 09:08 |
| capslockwizard | What I can infer is that is gzip file | 09:09 |
| capslockwizard | How can I go about building my own custom MAAS image (Ubuntu and not CentOS) | 09:09 |
| capslockwizard | ? | 09:09 |
| jojden | how to update interface using maas api | 10:10 |
| jojden | I am getting following error with this code | 10:10 |
| jojden | self.client.put(u"nodes/%s/interfaces/%s/" % (node_id, interfaces_id)) | 10:10 |
| jojden | HTTP ERROR: Cannot update interface interface because the node is not Ready. | 10:11 |
| jojden | any idea | 10:14 |
| jojden | It means we can change only for the node with ready state ? | 10:14 |
| joelio | Hey, I've done a fresh install of 16.04 and just installed MaaS in some real hardware (I tested with vms first). I can't for the life of me get the network interfaces or the controller itself listed in a given subnet | 10:51 |
| joelio | it didn't autodiscover what range it was in either | 10:51 |
| joelio | not I can't add DHCP resolution as it needs a controller to define that and I can't set the contoller as it's not appearing in the list of available controllers | 10:51 |
| D4RKS1D3 | Hi, I am trying to add a machine via juju, but i received this message "ERROR juju.provisioner provisioner_task.go:655 cannot start instance for machine "40": cannot run instances gomaasapi: got error back from server: 409 CONFLICT (No available node matches constraints: name=imaginative-attention.datacentre tags=datacentre)" | 11:50 |
| D4RKS1D3 | Someone know what happens? | 11:51 |
| joelio | this just doesn't work.. no rack controller can be applied to a network | 12:08 |
| joelio | so can't provision, shame a s this looked like a good tool | 12:09 |
| joelio | I've gone through all the docs related to rack controller too | 12:09 |
| joelio | it just doesn't work - wonder if it's a bug? | 12:09 |
| joelio | yea, just doesnt work - even on a fresh install | 12:26 |
| joelio | Node must be connected to a network. | 12:26 |
| joelio | in the Controller summary | 12:26 |
| joelio | I've applied subnets/spaces etc | 12:26 |
| joelio | but there seems to be a bug now | 12:26 |
| joelio | it's annoying that the docs don't reference 16.04 properly too - there seems to be a mish-mash of 1.9 and 2.x info | 12:27 |
| joelio | as for example, it's showing ethX, not Consistent Device Naming | 12:27 |
| joelio | perhaps I'm in a bug | 12:29 |
| joelio | as it's beta3 listed in the package upstream in 16.04 | 12:29 |
| joelio | yet the latest and greatest according to the changelog is beta5 | 12:29 |
| joelio | there's no PPA for 16.04 either | 12:29 |
| joelio | ahh, found the next ppa | 12:31 |
| joelio | yea, still the same issue | 13:57 |
| === Guest63702 is now known as terje | ||
| === Guest61314 is now known as CyberJacob | ||
| === CyberJacob is now known as Guest68658 | ||
| === Guest68658 is now known as CyberJacob | ||
| joelio | I guess this is a dead channel then too? | 14:58 |
| joelio | guess MaaS not the product for us then.. :) | 14:59 |
| lovea | Just upgraded from MAAS 1.8 to 2.0 and my PXE boot is bust. The upgrade has placed my external eth0 (unmanaged) and internal (maas managed) eth1 in the same fabric. I have created a separate fabric for the maas managed subnet but can't seem to move the subnet into it. How do I either move (update) a subnet into a different fabric or move an interface into another fabric? | 15:38 |
| lovea | To add to that the upgrade effectively placed both subnets on the same untagged VLAN. | 15:45 |
| mup | Bug # opened: 1587539, 1587542, 1587543, 1587544 | 15:54 |
| mup | Bug #1587548 opened: In p.rpc.clusterservice.Cluster.refresh, no attempt is made to deal with concurrency <tech-debt> <MAAS:New> <https://launchpad.net/bugs/1587548> | 16:06 |
| mup | Bug #1587549 opened: In p.rpc.clusterservice.Cluster.refresh, nothing waits for or handles errors from p.refresh.refresh <tech-debt> <MAAS:Triaged> <https://launchpad.net/bugs/1587549> | 16:06 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1587605 opened: [2.0b5] Allowed to commission newly enlisted nodes without power type set <MAAS:New> <https://launchpad.net/bugs/1587605> | 18:33 |
| sjl | must maas be installed on a bare-metal server? | 19:26 |
| kiko | sjl, no, it can run in a VM | 19:40 |
| kiko | in fact many people do | 19:40 |
| sjl | thanks kiko. | 20:19 |
| sjl | anyone get this to work? 'sudo apt-get install maas-image-builder' I get Unable to locate package error | 20:19 |
| kiko | sjl, that package I think may be available from a PPA | 20:24 |
| sjl | oh ok, was trying to follow the docs on how to install maas-image-builder:http://maas.ubuntu.com/docs/os-support.html?highlight=builder#maas-image-builder | 20:25 |
| kiko | sjl, http://askubuntu.com/questions/744966/how-do-you-install-the-maas-image-builder-on-14-04-lts maybe? | 20:28 |
| sjl | kiko, looked promising but fails on the `make` step with "Error: There is a version conflict" | 20:35 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!