| jojden | how to parse output of maas node details | 06:25 |
|---|---|---|
| mup | Bug #1594317 changed: Cannot start lxd-bridge.service when MAAS is managing DNS <dns> <MAAS:Invalid> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1594317> | 06:48 |
| mup | Bug #1594317 opened: Cannot start lxd-bridge.service when MAAS is managing DNS <dns> <MAAS:Invalid> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1594317> | 07:03 |
| mup | Bug #1594317 changed: Cannot start lxd-bridge.service when MAAS is managing DNS <dns> <MAAS:Invalid> <bind9 (Ubuntu):New> <https://launchpad.net/bugs/1594317> | 07:06 |
| jojden | how to parse node details | 08:16 |
| jojden | GET /api/1.0/nodes/{system_id}/ op=details | 08:16 |
| jojden | this gives BSON value | 08:16 |
| jojden | i need to parse this value | 08:17 |
| === CyberJacob is now known as zz_CyberJacob | ||
| === frankban is now known as frankban|afk | ||
| mup | Bug #1549842 changed: [2.0] Failed to update this region's process and endpoints; unleashed:pid=28940 record's may be out of date <MAAS:New> <https://launchpad.net/bugs/1549842> | 16:53 |
| valeech | maas 2.0 beta 3 when I try to update a subnetand move it into a specific space I get the following error: 'NoneType' object has no attribute 'split' | 18:43 |
| jhegge | valeech: There are quite a few little MAAS UI bugs like that in beta 3, if you can upgrade to beta 5 or later, most are gone | 18:52 |
| valeech | jhegge: thanks. I’ll check it out. | 18:52 |
| === zz_CyberJacob is now known as CyberJacob | ||
| valeech | now running maas 2.0 beta 7. When I try to load the GUI, I get this error where the interface should be: Error Occured : 'NoneType' object is not iterable | 19:29 |
| bdx | blake_r_: will you make a new maas-rack rev with a current `charm build` ? | 19:30 |
| bdx | install hook is failing for maas-rack due to pip version < 8.1.1 | 19:31 |
| valeech | ok, the NoneType error only shows up on the Nodes and Networks tabs. The other tabs work fine. | 19:32 |
| sjl | submitting 3 parallel API calls to op=allocate fails the 2nd and 3rd call, but staggering the 3 calls with random delays succeeds. Is there a best practice with API calls to ensure safe calls? | 20:40 |
| mup | Bug #1594975 opened: simultaneous api calls to op=allocate errors <MAAS:New> <https://launchpad.net/bugs/1594975> | 21:42 |
| valeech | Fresh install of maas 2.0 beta 7. Trying to get juju to bootstrap and having issues. I would like to ssh into the node while juju is bootstrapping so I can watch the status. When I try to ssh to the node I get Permission denied (publickey). If I manually deploy the same node, I am able to SSH in no problem. So when maas deploys its not installing the SSH key. I also noticed that it is not deploying the correct version of ubuntu. I have commi | 22:40 |
| valeech | and deploy set to 14.04. When maas auto deploys, it installs 16.04. Again, I can manually deploy and the correct os gets installed and I can SSH. | 22:40 |
| mup | Bug #1594991 opened: [2.0RC2] MAAS logs every power query as a NodeEvent <MAAS:Triaged> <https://launchpad.net/bugs/1594991> | 22:52 |
| === CyberJacob is now known as zz_CyberJacob | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!