| roaksoax | /win/win 6 | 01:11 |
|---|---|---|
| === mup_ is now known as mup | ||
| baldpope | if I want to delete and then provision from scratch an existing node, do I release it through the webui or ? | 02:35 |
| === blahdeblah is now known as blahdeblah-lunch | ||
| baldpope | appears to be to release and then commision? | 02:39 |
| baldpope | is it possible to have video output of the boot image changed back to 80x25 - would make working with serial consoles a lot easier | 02:42 |
| === blahdeblah-lunch is now known as blahdeblah | ||
| baldpope | ok, nearly 1am - misc. problems trying to deploy openstack via maas | 05:45 |
| baldpope | anyone interested in helping out trying to get openstack pushed ? | 05:46 |
| jwitko | hey guys when querying the maas API with python 2.7 I get an error surrounding a pickle object `ValueError: unsupported pickle protocol: 3` | 06:04 |
| jwitko | can anyone tell me where the picke dump is being done so that I might test adding the protocol=2 parameter ? | 06:05 |
| === frankban|afk is now known as frankban | ||
| mup | Bug #1623468 opened: NVME disks are not showing up in MaaS when commissioning nodes using any newer kernel than "hwe-t" <MAAS:New> <https://launchpad.net/bugs/1623468> | 12:24 |
| mup | Bug #1623468 changed: NVME disks are not showing up in MaaS when commissioning nodes using any newer kernel than "hwe-t" <MAAS:New> <https://launchpad.net/bugs/1623468> | 13:03 |
| rock | roaksoax: Hi. Libvirt error : connection closed issue resolved. we faced the similar bug as https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/994476. Now created 4 maas nodes with PXE boot enable option 1) add chassis https://imagebin.ca/v/2v3Cvi0gPkCG 2) enlisting nodes https://imagebin.ca/v/2v3CKF6k90lB. After enlisting the power state not changing form on to OFF. Log info: http://paste.openstack.org/show/576163/ | 13:32 |
| rock | roaksoax: SO then I deleted enlisted nodes. Again I clicked on "Add Chassis" entered details. This nodes enlisted in MAAS UI with power state OFF. | 13:41 |
| roaksoax | rock: that is fine | 13:41 |
| roaksoax | rock: that is expected | 13:41 |
| roaksoax | rock: the machines will be in "New" state and powered off | 13:41 |
| roaksoax | rock: now you need to "Commission" them | 13:41 |
| rock | roaksoax: Yes. I am doing now. | 13:42 |
| rock | roaksoax: nodes state after 15 min of commissioning start https://imagebin.ca/v/2v3JgORVid5I. Two nodes came to ready state but disks not detected. power is in "on" mode. Two nodes are still commissioning . I am stucking here. IThe state of nodes not changing. | 13:55 |
| rock | roaksoax: maas log : http://paste.openstack.org/show/576181/ | 13:57 |
| roaksoax | rock: what type of disks your VM's have? | 14:03 |
| roaksoax | virtio ? | 14:03 |
| rock | roaksoax: default disk, One SATA disk[second disk] | 14:08 |
| rock | roaksoax: I mean One virtual disk [Disk1], second SATA disk [Disk2] | 14:10 |
| rock | roaksoax: Genarally, what type of disks we need to take and what storage format we need to choose for KVM VMs | 14:13 |
| rock | roaksoax: Two nodes commissioning failed with Node marking failed : timeout issue. maas log info: http://paste.openstack.org/show/576191/ | 14:20 |
| rock | roaksoax: https://imagebin.ca/v/2v3V5ZDsIGAi. | 14:30 |
| roaksoax | rock: there may be a bug discovering those | 14:52 |
| roaksoax | rock: try setting the VM disk to IDE ? | 14:52 |
| jwitko | hey guys when querying the maas API with python 2.7 I get an error surrounding a pickle object `ValueError: unsupported pickle protocol: 3` | 14:54 |
| jwitko | can anyone tell me where the picke dump is being done so that I might test adding the protocol=2 parameter ? | 14:54 |
| baldpope | trying to deploy openstack auto deploy with openstack-install and selecting auto deploy | 14:55 |
| rock | roaksoax: OK. Thank you. I will try with IDE. And In which cases we will get ERROR: Marking node failed: Node operation 'Commissioning' timed out after 0:20:00. | 14:57 |
| rock | roaksoax: I selected IDE disks for KVM VMs. Still two nodes not detecting disks.And two nodes are failing commission with ERROR: Marking node failed: Node operation 'Commissioning' timed out after 0:20:00. How can I resolve this. Have you faced similar issues?. | 15:25 |
| rock | roaksoax: In MAAS UI, clicked on "Add Machine". And then added individual machines. Here also commissioning failed: RROR: Marking node failed: Node operation 'Commissioning' timed out after 0:20:00. For three individually added nodes it was showing the same issues. | 15:33 |
| baldpope | rock, one thing that caught me yesterday (new maas user myself) was to make sure I was selecting the 'internal' ip of the maas server | 15:40 |
| baldpope | in my case - two nics, one dedicated for provisioning (eth1) and the other is the lan (eth0) | 15:41 |
| baldpope | when I setup maas, I mistakenly gave the web interface the eth0 IP | 15:41 |
| baldpope | fixed a couple of issues once I used the correct internal ip | 15:41 |
| baldpope | may only be an issue if you have 2 nics and the networks are firewalled between the two | 15:41 |
| rock | baldpope: Hi. are you doing maas setup on KVM machines? | 15:44 |
| baldpope | no, bare metal | 15:44 |
| baldpope | or trying to | 15:44 |
| baldpope | deploying an openstack cluster in house | 15:44 |
| rock | baldpope: Ok. Actually, I am trying maas setup on KVM machines. I want to have [MAAS+OpenStack base bundle] setup to test our bundle. | 15:46 |
| baldpope | sounds like we're doing much the same thing | 15:46 |
| baldpope | i'm just on BM | 15:46 |
| rock | baldpope: Oh. great. Previously, I setup Ubuntu Openstack Autopilot Setup On Bare Metal. Due to lack of enough servers I am going to have [MAAS+OpenStack base] setup On KVM machines. | 15:48 |
| baldpope | very cool rock - might have to pick your brain then | 15:50 |
| baldpope | been running into problems attempting to run the openstack installer | 15:50 |
| rock | baldpope: SO which problems are you facing. JUJU bootstrap error (or) LAndscape deployment error. | 15:51 |
| baldpope | juju | 15:51 |
| rock | baldpope: How much time it was taking to bootstrap. | 15:53 |
| baldpope | a good 20 minutes - maybe longer | 15:53 |
| baldpope | annoying as fuck | 15:53 |
| jwitko | Is it possible to use python 2.7 with MaaS 2.0 API ? it does not seem to be possible unless I'm missing something ? | 15:58 |
| roaksoax | jwitko: 2.0 no, 2.0 doens't support py2.7 | 15:58 |
| roaksoax | rock: was maas able to power on the machines ? | 15:58 |
| jwitko | ty | 15:59 |
| jwitko | that is a real bummer. is that publicized anywhere on the docs? | 15:59 |
| rock | roaksoax: Yes. | 16:02 |
| rock | baldpope: OH. I got the same juju bootstrap error. I rerun the Openstack installer. Third time I got succeded. | 16:04 |
| rock | roaksoax: When we start commissioning MAAS able to power on the machines. | 16:07 |
| jwitko | roaksoax, can you run maas 1.9 on ubuntu 16.04 ? | 16:09 |
| roaksoax | jwitko: no, only 2.0 | 16:21 |
| roaksoax | jwitko: 1.9 doesn't support python3 | 16:21 |
| roaksoax | 2.0 doesn't support python2 | 16:21 |
| kiko | roaksoax, isn't there an independent client library they could use that does support python2? | 16:21 |
| kiko | or is the issue that any library will not have been updated for MAAS2? | 16:21 |
| roaksoax | kiko: the 1.9 client library won't work with 2.0. Working with the 2.0 API requires python3 | 16:25 |
| jkov | What is the best way to install the debs that result from package-dev make target? | 16:28 |
| kiko | roaksoax, well, working with the 2.0 API could be implemented in brainfuck or bash tbh :-) it's more that the API we ship is python3 :-) | 16:30 |
| kiko | I mean it IS just REST :-) | 16:30 |
| mup | Bug #1519828 changed: [2.1] Support for static routes <canonical-bootstack> <MAAS:Fix Released> <MAAS 1.9:Won't Fix> <MAAS 2.0:Won't Fix> <https://launchpad.net/bugs/1519828> | 16:34 |
| mup | Bug #1519828 opened: [2.1] Support for static routes <canonical-bootstack> <MAAS:Fix Released> <MAAS 1.9:Won't Fix> <MAAS 2.0:Won't Fix> <https://launchpad.net/bugs/1519828> | 16:43 |
| baldpope | rock, kiko is it possible the juju error is because the image pushed (during commissioning) has a key already defined? not sure what to look for in some of these errors | 16:45 |
| mup | Bug #1519828 changed: [2.1] Support for static routes <canonical-bootstack> <MAAS:Fix Released> <MAAS 1.9:Won't Fix> <MAAS 2.0:Won't Fix> <https://launchpad.net/bugs/1519828> | 16:46 |
| === Kiall_ is now known as Kiall | ||
| === frankban is now known as frankban|afk | ||
| mup | Bug #1623598 opened: [2.1, vanilla] Settings page do not have separators for the config sections <MAAS:New> <https://launchpad.net/bugs/1623598> | 17:22 |
| mup | Bug #1623599 opened: [2.1, vanilla] Settings page do not have separators for the config sections <ui> <ux> <vanilla> <MAAS:New> <https://launchpad.net/bugs/1623599> | 17:22 |
| Kiall | Hey, so - I'm trying to create some custom images - debian based, LVM backed, but anything I upload fails to deploy.. Anyone know of some docs for handling custom images? (Beyond what's in the maas docs themselves), or open source tools I can check the code in for building the images? | 17:24 |
| kiko | Kiall, there are no docs beyond the MAAS docs, and we are spread really thin post-2.0 | 17:27 |
| kiko | Kiall, if you're interested we'd be happy to sell you a professional services engagement to help you build an image customization pipeline | 17:28 |
| kiko | but we're being a bit victims of our own success right now :) | 17:28 |
| Kiall | Hah, always with the upsell ;) | 17:28 |
| Kiall | I'll keep digging, thanks :) | 17:28 |
| kiko | Kiall, think of all the hungry programmers | 17:29 |
| * Kiall works on OpenSource for a living too, and is also quite hungy ;) | 17:29 | |
| baldpope | Kiall, where you at? can I buy you a donut? | 17:58 |
| Kiall | lol - Ireland ;) | 17:58 |
| baldpope | suprised there's not a ${cryptocoinoftheday} bot running - allow people to tip each othere here | 17:58 |
| baldpope | Kiall, buy you a stout? | 17:59 |
| Kiall | Maybe next time ;) | 18:05 |
| === degville- is now known as degville | ||
| mup | Bug #1623634 opened: [2.1] Trying to cancel an image import from the new Images page results on it not being cancelled on the backend. <angular-images> <MAAS:Confirmed> <https://launchpad.net/bugs/1623634> | 19:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!