[11:40] <AskUbuntu> Juju/MAAS in vSphere to test OpenStack | http://askubuntu.com/q/364332
[16:41] <alok_> Question: I am trying to do a test install of MAAS on virtualbox. I am able to get as far as the MAAS gui and am able to manually add a node. However once I add the first node it appears to shut down and the gui shows a status of commissioning but appears to be stuck. Can anyone suggest steps to troubleshoot?
[16:51] <alok_> Does anyone have suggestions or links to troubleshoot a MAAS configuration? (see question above)
[17:51] <roaksoax> smoser: ping
[17:51] <roaksoax> smoser: getting this error when using juju/maas from cloud-archive: cloud-init.log:Oct 23 17:47:26 node01 [CLOUDINIT] cc_apt_update_upgrade.py[WARNING]: Source Error: deb http://ubuntu-cloud.archive.canonical.c
[17:52] <roaksoax> om/ubuntu precise-updates/cloud-tools main:failed to get key from keyserver.ubuntu.com
[17:52] <roaksoax> cloud-init-output.log:2013-10-23 17:47:26,606 - cc_apt_update_upgrade.py[WARNING]: Source Error: deb http://ubuntu-cloud.archive.canonical.com
[17:53] <mgz> roaksoax: there's a package in precise that contains the key
[17:57] <roaksoax> mgz: yep.. but this should have been added automatically
[17:58] <mgz> by whom? :)
[17:58] <roaksoax> mgz: cloud-init?
[17:58] <roaksoax> mgz: this is a juju bootstrap
[17:59] <mgz> roaksoax: (arguably by us...)
[18:00] <roaksoax> mgz: I'm using precise with cloud-archive:tools. juju on the bootstrap node cannot start because it failed to add the repository, hence failed to install juju/mongodb from cloud-archive:tools
[18:02] <smoser> roaksoax, where are you?
[18:02] <roaksoax> smoser: regency b
[18:04] <mgz> smoser: he's like, right next to you... unless you just arrived? :)
[18:04] <smoser> roaksoax, nothing should have hit keyserver.ubuntu.com
[18:04] <smoser> i just arrived. thanks
[18:05] <roaksoax> smoser: deploying again, should take a couple minutes so you can debug :)
[18:17] <roaksoax> smoser: bug #1243861
[18:18] <roaksoax> jamespage: bug #1243861
[18:20] <roaksoax> mgz: do you work on this stuff? 1243861
[18:20] <roaksoax> mgz: do you work on this stuff? bug @1243861
[18:21] <roaksoax> mgz: do you work on this stuff? bug #1243861
[18:21] <smoser> mgz, https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1243861
[18:37] <mgz> smoser: thanksyous
[21:16] <jtv> smoser: does this satisfy your need for creating users?  https://code.launchpad.net/~jtv/maas/api-add-user/+merge/192403
[21:18] <roaksoax> jtv: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1243917
[21:18] <roaksoax> :)
[21:19] <jtv> roaksoax: annoying.
[21:19] <roaksoax> :(
[21:19] <jtv> Looks easy.
[21:19] <jtv> Not related to what I just did, but if it hurts that much in practice, it's low-hanging fruit.
[21:22] <roaksoax> jtv: doesn't really but gaughen just found it :)
[21:23] <jtv> We can't make the email address optional, but we can make the error message clearer and document the requirement.
[21:37] <gaughen> jtv, it's the first bug I filed!
[21:39] <fizzi> hi all, i have just configure my mass controller ...
[21:40] <fizzi> i started one node ...
[21:40] <fizzi> the pxe work and the installation
[21:40] <fizzi> run
[21:40] <fizzi> but i retrive an error ... occurred when download packages
[21:41] <jtv> What kind of error?
[21:41] <fizzi> could not retrieve package from it.archive....
[21:41] <jtv> And... downloading packages onto the node you were setting up?  Or while downloading PXE install images onto the cluster controller?
[21:42] <fizzi> i guest that some configuration coming from maas is invalid
[21:42] <fizzi> the first
[21:42] <jtv> Do your nodes have direct access to the Ubuntu archive?  Or do you need to go through a proxy?
[21:43] <fizzi> direct connection
[21:43] <fizzi> the problem is that the maas dhcp write a wrong dns (he)
[21:44] <fizzi> i just try to modify che maas dhcp file configuation
[21:44] <fizzi> but ...
[21:44] <fizzi> nothing
[21:45] <jtv> No, modifying the DHCP config file shouldn't work — that gets rewritten.
[21:46] <fizzi> i try all of this in vmware esx 5 env
[21:47] <fizzi> but i dont think that esx can be a problem
[21:47] <fizzi> some suggestion
[21:47] <fizzi> some indication?
[21:47] <fizzi> thanks jtv
[21:47] <jtv> Sounds like MAAS_URL was not set right.
[21:48] <fizzi> '
[21:48] <fizzi> ?
[21:48] <jtv> The nodes use a proxy installed on the region controller.
[21:49] <jtv> But to get that working properly, they need to know the IP address where _they_ can reach the region controller.
[21:49] <jtv> This may be a different address from where you'd normally access the MAAS UI.
[21:49] <fizzi>  but this work fine i think
[21:49] <fizzi> ah
[21:49] <fizzi> i need 2 eth?
[21:50] <bigjools> MAAS_URL is the *internal* node-facing IP by which nodes can reach it
[21:50] <bigjools> it is also the dns server address
[21:50] <jtv> Oh, are you running everything on the same network?
[21:50] <jtv> Is MAAS managing the DHCP?
[21:50] <fizzi> yes MAAS manage dhcp
[21:50] <fizzi> yes i run now all for the same network
[21:51] <jtv> OK...
[21:51] <jtv> Is there anything else you can tell us about the incorrect DNS server address you saw in the DHCP config?
[21:52] <jtv> For example, was it the wrong address but on your network, or was it some completely different IP..?
[21:52] <fizzi> the problem is that is the same ip of MAAS ... but he can only resolv cluster nodes i think
[21:52] <fizzi> no no
[21:53] <fizzi> is the MAAS ip
[21:53] <fizzi> for example 150.145.133.19/MAAS
[21:53] <jtv> That should be OK (assuming you let MAAS manage DNS as well)
[21:53] <bigjools> http://maas.ubuntu.com/docs/configure.html#client-side-dns-configuration
[21:53] <fizzi> the nodes are set in resolv.conf 150.145.133.19
[21:55] <jtv> You shouldn't have the nodes in there AFAIK...
[21:55] <fizzi> but i wont install the ubuntu 12.04lts form maas ... is there a way ?
[21:55] <jtv> Well let's find out what exactly the problem is.
[21:56] <jtv> If you have the nodes in resolv.conf, that's going to confuse things.
[21:56] <fizzi> i think ... (not maas expert) ... the dns configuration
[21:56] <jtv> Ah
[21:56] <fizzi> from maas dhcp to nodes
[21:56] <jtv> Yes, MAAS writes the DNS configuration, and the nodes should be in there.
[21:56] <jtv> Right.
[21:57] <fizzi> yes
[21:57] <fizzi> but write incorrect
[21:57] <fizzi> dns
[21:57] <fizzi> for ubuntu installation i need to connect to internete
[21:57] <jtv> Yes, of course.
[21:57] <fizzi> and the maas ip ...(dns) not resolv internet addreses
[21:58] <fizzi> i work at NCR and we want test maas on some nodes
[21:59] <jtv> fizzi: sounds like the problem is that you're getting _only_ the DNS from the MAAS itself.
[21:59] <jtv> You _also_ need upstream DNS to resolve names on the internet.
[21:59] <fizzi> right
[22:00] <fizzi> the maas controller is ubuntu 12.04.03 LTS
[22:00] <fizzi> server 64bit 16gb ram
[22:00] <jtv> You can configure the DNS server in MAAS in /etc/maas/templates/dns/named.conf.template — MAAS uses that template file to rewrite the DNS config.
[22:01] <jtv> But I'm thinking if there's another way.
[22:01] <bigjools> you can set more than one nameserver in the resolv.conf
[22:01] <fizzi> yep
[22:04] <jtv> AIUI the nodes will download packages via the http proxy in MAAS...
[22:05] <jtv> So if you add a public DNS server to your resolv.conf on the MAAS server, this problem may be solved.
[22:05] <jtv> Because the nodes won't need to resolve the Ubuntu archive's hostname...  Only the MAAS server will have to do that.  I think.
[22:06] <fizzi> mmm
[22:06] <fizzi> i have this configuration
[22:06] <fizzi> and it doent work
[22:06] <fizzi> nameserver 150.145.70.13 nameserver 150.145.133.13
[22:06] <fizzi> the second ip ... is the MAAS
[22:07] <fizzi> the first is the public dns
[22:07] <jtv> Ah, roaksoax is here and he tells me that _on 12.04_ it doesn't work the way I was hoping for yet.
[22:07] <jtv> (On 13.10 it does).
[22:08] <jtv> So back to that config template:
[22:08] <jtv> /etc/maas/templates/dns/named.conf.template
[22:08] <jtv> You'll need to configure a fallback DNS server there.
[22:08] <fizzi> i not have this file
[22:09] <fizzi> i have /usr/share/pyshared/provisioningserver/dns/templates/named.conf.template
[22:09] <jtv> Ah!
[22:09] <jtv> I took the path from the source tree.
[22:10] <fizzi> include "{{named_rndc_conf_path}}";  # Zone declarations. {{for zone in zones}} zone "{{zone.zone_name}}" {     type master;     file "{{zone.target_path}}"; }; {{endfor}}
[22:10] <fizzi> is this ?
[22:10] <jtv> That's it.
[22:10] <jtv> Yup.
[22:10] <fizzi> ok ...
[22:10] <fizzi> how change ?
[22:10] <jtv> I'm looking it up...
[22:12] <fizzi> question ... but i always need that the maas have maas-dns (bind9) running
[22:12] <fizzi> right=
[22:12] <fizzi> ?
[22:14] <jtv> You can do without, but then you won't have DNS hostnames for the nodes.
[22:14] <jtv> http://www.dslreports.com/forum/r1274209-BIND-Question-Query-upstream-DNS-for-unknown-host may be helpful.
[22:14] <jtv> If it's OK to address your nodes by their IP addresses, then you don't need MAAS DNS.
[22:16] <fizzi> thanks for your time
[22:16] <fizzi> jtv:
[22:16] <jtv> Hope that helps!
[22:17] <fizzi> i try all of this tomorrow
[22:17] <roaksoax> fizzi: or you cloud install masa from the cloud-archive
[22:17] <roaksoax> and you wouldn't experience this issue
[22:17] <roaksoax> (i think)
[22:17] <roaksoax> s/masa/maas
[22:17] <fizzi> and i please past link roaksoax
[22:18] <roaksoax> fizzi: sudo apt-get install python-software-properties && sudo add-apt-repository cloud-archive:tools && sudo apt-get install maas (or you can do a sudo apt-get dist-upgrade)
[22:19] <fizzi> but i think to upgrade to 13.04 that as jtv say not have this problem
[22:19] <roaksoax> fizzi: that will upgrade maas to its latest released version
[22:20] <fizzi> now i need to go...
[22:20] <roaksoax> fizzi: you would still run precise, but with latest maas version
[22:20] <fizzi> yep roaksoax
[22:20] <fizzi> ok i see
[22:20] <fizzi> i unsterstand
[22:20] <fizzi> bye at all
[22:20] <fizzi> regards,
[22:20] <roaksoax> bye
[22:21] <jtv> bye
[22:42] <AskUbuntu> Juju deploy of Charm (Mysql) in MAAS provider failing after successful bootstrap. Juju status stuck in "Pending" state | http://askubuntu.com/q/364714