| === CyberJacob is now known as zz_CyberJacob | |
| [00:24] <ennoble> Is there a way to tell MaaS to install on a specific storage device (or at least storage device type) on the server? | |
| === _rparenato is now known as rparenato | |
| === jtv1 is now known as jtv | |
| === zz_CyberJacob is now known as CyberJacob | |
| === CyberJacob is now known as zz_CyberJacob | |
| [10:40] <mup> Bug #1496339 opened: Problem installing fixture '.../src/maasserver/fixtures/dev_fixture.yaml <dev-environment> <MAAS:Triaged> <https://launchpad.net/bugs/1496339> | |
| === allenap changed the topic of #maas to: MAAS: Ubuntu's bare-metal provisioning tool | Docs: http://maas.ubuntu.com/ | Mailing list: https://launchpad.net/~maas-devel | |
| [10:46] <mup> Bug #1496339 changed: Problem installing fixture '.../src/maasserver/fixtures/dev_fixture.yaml <dev-environment> <MAAS:Triaged> <https://launchpad.net/bugs/1496339> | |
| [10:49] <mup> Bug #1496339 opened: Problem installing fixture '.../src/maasserver/fixtures/dev_fixture.yaml <dev-environment> <MAAS:Triaged> <https://launchpad.net/bugs/1496339> | |
| [11:02] <binoy> how to post in maas api | |
| [11:03] <binoy> using maas-client | |
| [11:08] <binoy> hi | |
| [11:40] <mup> Bug #1496360 opened: POST request using python-maas-client <MAAS:New> <https://launchpad.net/bugs/1496360> | |
| [11:44] <mup> Bug #1496360 changed: POST request using python-maas-client <MAAS:New> <https://launchpad.net/bugs/1496360> | |
| [11:47] <mup> Bug #1496360 opened: POST request using python-maas-client <MAAS:New> <https://launchpad.net/bugs/1496360> | |
| [11:53] <mup> Bug #1496360 changed: POST request using python-maas-client <MAAS:Invalid> <https://launchpad.net/bugs/1496360> | |
| [11:58] <binoy> https://bugs.launchpad.net/maas/+bug/1496360 | |
| [12:02] <mup> Bug #1496360 opened: POST request using python-maas-client <MAAS:New> <https://launchpad.net/bugs/1496360> | |
| [12:09] <binoy_> https://bugs.launchpad.net/maas/+bug/1496360 | |
| [12:11] <mup> Bug #1496360 changed: POST request using python-maas-client <MAAS:New> <https://launchpad.net/bugs/1496360> | |
| [12:14] <mup> Bug #1496360 opened: POST request using python-maas-client <MAAS:Invalid> <https://launchpad.net/bugs/1496360> | |
| [13:23] <David_Orange> Hello MAASters | |
| [13:24] <kiko> hello there! | |
| [13:24] <kiko> David_Orange, can I help? | |
| [13:25] <David_Orange> kiko: I go an issue with my MAAS. I Got 2 interfaces and the DHCP is on the second one | |
| [13:25] <David_Orange> The data source sent to my node is pointing to the ip of the fist interface, where can I change that ? | |
| [13:25] <kiko> David_Orange, can you explain a bit more -- 2 interfaces on a node or on the maas cluster controllers? | |
| [13:26] <David_Orange> kiko: sorry, My master have 2 interfaces, one for admin and the 2 second on for the provisioning of other nodes | |
| [13:27] <David_Orange> and when the node start the commisionning it receive a bad address: | |
| [13:27] <kiko> David_Orange, by master I assuming you mean the cluster controller? :) | |
| [13:27] <David_Orange> MAAS: {consumer_key: DnebRm9DqCDDDYPVJC, metadata_url: 'http://192.168.0.53/MAAS/metadata/', | |
| [13:27] <kiko> David_Orange, what version of MAAS, incidentally? | |
| [13:27] <David_Orange> yes | |
| [13:28] <David_Orange> the last one, I check | |
| [13:28] <kiko> please check with dpkg -l | grep maas | |
| [13:28] <David_Orange> 1.7.6 | |
| [13:28] <kiko> thanks | |
| [13:28] <David_Orange> 1.7.6+bzr3376-0ubuntu2~15.04.1 | |
| [13:28] <kiko> thanks | |
| [13:29] <kiko> okay. so you have a cluster controller with two interfaces. what have you configured in the clusters page? | |
| [13:29] <binoy_> https://bugs.launchpad.net/maas/+bug/1496360 | |
| [13:30] <David_Orange> I check | |
| [13:30] <David_Orange> one interface configured on eth1 | |
| [13:31] <David_Orange> but eth0 waas configured then removed | |
| [13:31] <kiko> okay | |
| [13:31] <kiko> so what you are seeing is that the node is getting the address for eth0 when commissioning? | |
| [13:33] <David_Orange> in the preseed of the node, | |
| [13:33] <David_Orange> http://pastebin.geany.org/u4dy9/ | |
| [13:34] <David_Orange> the metadata_url should point to the other network (192.168.2.0) | |
| [13:37] <David_Orange> Am I clear enough ? | |
| [13:41] <David_Orange> kiko: I change the setting maas_url in the maas_cluster.conf and it seems to change te preseed, I try a new commisioning | |
| [13:45] <kiko> David_Orange, I was going to say exactly that -- your maas_url may be wrong | |
| [13:46] <David_Orange> kiko: yes, and it works | |
| [13:46] <David_Orange> Have I missed a doc somewhere ? | |
| [13:46] <kiko> David_Orange, thanks very much. the maas_url being wrong is a visibility problem and there is a bug reported for it | |
| [13:47] <David_Orange> ok, thanks a lot for your time to help me | |
| [13:47] <mup> Bug #1496401 opened: Failure to grab the secret.lock <MAAS:Triaged> <https://launchpad.net/bugs/1496401> | |
| [13:50] <David_Orange> kiko, I continue my tests. Thanks ! | |
| === jfarschman is now known as MilesDenver | |
| [13:59] <mup> Bug #1496401 changed: Failure to grab the secret.lock <MAAS:Triaged> <https://launchpad.net/bugs/1496401> | |
| [14:05] <mup> Bug #1496360 changed: POST request using python-maas-client <MAAS:Invalid> <https://launchpad.net/bugs/1496360> | |
| [14:05] <mup> Bug #1496401 opened: Failure to grab the secret.lock <MAAS:Triaged> <https://launchpad.net/bugs/1496401> | |
| [14:11] <mup> Bug #1496360 opened: POST request using python-maas-client <MAAS:Invalid> <https://launchpad.net/bugs/1496360> | |
| [14:14] <mup> Bug #1496360 changed: POST request using python-maas-client <MAAS:Invalid> <https://launchpad.net/bugs/1496360> | |
| [15:48] <kflavin> I'm trying to setup the region controller and cluster controller on separate servers. I have two cluster controllers. When I attempt to import images, I get an exception in the pserv.log. When I dig a little further, I see it's a 500 error, caused by a database connection problem. | |
| [15:49] <kflavin> Here is the error that shows up in the apache logs: http://pastebin.com/iVJjUpRK | |
| [15:49] <kflavin> It looks like the cluster controller is trying to contact a database running locally, when it should be talking to the database on the region controller? | |
| [15:50] <kflavin> Did I miss something during setup? The cluster controller appeared to add correctly to the region controller, and I can see it from the web UI. | |
| [16:08] <mup> Bug #1496469 opened: IBM Power8 will not PXE boot to MAAS 1.8 <blocks-hwcert> <MAAS:New> <https://launchpad.net/bugs/1496469> | |
| [16:11] <mup> Bug #1496469 changed: IBM Power8 will not PXE boot to MAAS 1.8 <blocks-hwcert> <MAAS:New> <https://launchpad.net/bugs/1496469> | |
| [16:20] <mup> Bug #1496469 opened: IBM Power8 will not PXE boot to MAAS 1.8 <blocks-hwcert> <MAAS:New> <https://launchpad.net/bugs/1496469> | |
| === rbanffy_ is now known as rbanffy | |
| [20:36] <mup> Bug #1496562 opened: 1.9 doesn't set the dns-search option in the generate /etc/network/interfaces <networking> <curtin:Triaged> <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1496562> | |
| === zz_CyberJacob is now known as CyberJacob | |
| === CyberJacob is now known as zz_CyberJacob | |