[06:26] Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [06:26] getting timeout error [06:26] what will be the issue [06:27] configured region controller [06:27] and [06:27] sudo dpkg-reconfigure maas-cluster-controller [06:27] can anybody give a clue regarding this [07:41] jojden: not without seeing the full log, but that seems related to the machine not being able to contact the region controller, or the machine does not have networking [07:42] cluster and region configuration is correct and in maas cluster page showing it is connected. [07:43] roaksoax: while I am doing the curl http://169.254.169.254/latest/meta-data/ [07:43] I am getting 404 [07:44] any idea how to solve the out-of-sync for images that I get in a cluster ? [07:49] jojden: look at the logs and see if there's an issue there [07:49] jojden: what for what you've pasted, may be that your machines dont have access to the region controller [07:50] roaksoax: Its having the access to rc. [07:50] curl http://169.254.169.254 [07:51] gives the list of meta-data [07:51] and http://169.254.169.254/2009-04-04/meta-data/ gives 404 [07:51] jojden: did you look at the logs ? [07:51] yes [07:53] var/ log/ maas [07:53] right [07:56] checked in both rc and cc log [07:56] jojden: and ? [07:56] jojden: any tracebacks ? [07:56] but notmuch infor regarding this error [07:56] jojden: any errors ? [07:56] no [07:56] jojden: what version of maas are you using ? [07:56] jojden: do you have the full console log ? [07:56] 1.9 [07:56] jojden: 1.9.X ?? [07:57] jojden: 1.9.2? 1.9.3? [07:57] MAAS Version 1.9.0+bzr4533-0ubuntu1 (trusty1) [08:00] jojden: can you upgrade to 1.9.3 ? [08:00] your bug may be fixed there [08:21] ok sure [08:34] Bug #1560292 changed: cli login no longer works after an update to new 2.0 packages, requires logging out and back in [09:10] hi roaksoax [09:10] I have updated the maas to 1.9.3 [09:11] maas: [09:11] Installed: (none) [09:11] Candidate: 1.9.3+bzr4577-0ubuntu1~trusty1 [09:11] -- [09:11] maas-dns: [09:11] Installed: (none) [09:11] Candidate: 1.9.3+bzr4577-0ubuntu1~trusty1 [09:11] -- [09:11] maas-dhcp: [09:11] Installed: 1.9.0+bzr4533-0ubuntu1~trusty1 [09:11] Candidate: 1.9.3+bzr4577-0ubuntu1~trusty1 [09:11] root@maasrc:/var/log/maas/apache2# apt-cache policy maas{,-dns,-dhcp} | grep Installed -B1 -A1 [09:11] maas: [09:11] Installed: (none) [09:11] Candidate: 1.9.3+bzr4577-0ubuntu1~trusty1 [09:11] -- [09:11] maas-dns: [09:11] Installed: 1.9.0+bzr4533-0ubuntu1~trusty1 [09:11] Candidate: 1.9.3+bzr4577-0ubuntu1~trusty1 [09:11] -- [09:11] maas-dhcp: [09:11] Installed: (none) [09:11] Candidate: 1.9.3+bzr4577-0ubuntu1~trusty1 [09:13] jojden: cool, let's try to reproduce and please paste me the full console log while the machine is trying to access the metadata [09:14] atually I am trying to create the node using pxe boot. And using the following script [09:14] --name=maas-node-test \ [09:14] --connect=qemu:///system --ram=512 --vcpus=1 --hvm --virt-type=kvm \ [09:14] --pxe --boot network,hd \ [09:14] --os-variant=ubuntutrusty --graphics vnc --noautoconsole --os-type=linux --accelerate \ [09:14] --disk=/var/lib/libvirt/images/maas-node-test.qcow2,bus=virtio,format=qcow2,cache=none,sparse=true,size=10 \ [09:14] --network=network=vlan-20,model=virtio [09:15] maas rc in one node and maascc in another node [09:15] and they are connected it [09:15] jojden: right, that should be ok, but i'm interested in looking at the console log [09:15] jojden: to see what's actually going on [09:16] console log of newly created node right ? [09:17] i will take the console screenshots of the newly created node [09:17] is that fine ? [09:29] jojden: you can just put it in those websites were you can share pic [09:30] ok [09:31] http://postimg.org/gallery/2fqa982k/99188f9c/ [09:32] roaksoax [10:01] roaksoax are you busy [10:59] jojden: seems like you dont have connection [11:04] connection to where ? [11:04] @roaksoax [11:05] jojden: to the region, but the 3rd/4th image show a different interesting error [11:06] jojden: can you paste /var/log/maas/*.log ? like clusterd.log and regiond.log [11:08] sure [11:20] roaksoax http://pastebin.com/kAjbKAsr [11:21] http://pastebin.com/B1dJtVaL [11:24] jojden: isn't there a better regiond.log ? [11:24] jojden: the one you sent me doesn'y really show any API query [11:25] jojden: also, is apache2 running ? [11:25] apache2 is running , otherwise maas gui wont load right ? [11:25] actually I have cleared the log before creating the vm [11:26] then I started creating it [11:26] and this is the log details we have in [11:26] jojden: so regiond.log should be showing that you can/cannot access a machine [11:26] jojden: err [11:26] jojden: regiond.log would be showing when the machine is accessing the metadata server [11:26] jojden: but it is not [11:27] jojden: which is why I wonder if apache2 is failing in the forwarding [11:27] or something along those lines [11:27] let me check for access and error log [11:28] root@maasrc:/var/log/maas/apache2# /etc/init.d/apache2 status [11:28] * apache2 is running [11:29] jojden: can you share your apache2 access.log ? [11:29] ok [11:31] roaksoax: http://pastebin.com/6A4Uux5A [11:32] jojden: /MAAS/api/1.0/pxeconfig/?bios_boot_method=pxe&local=10.20.0.12&remote=10.20.0.174&cluster_uuid=68ac4a87-16d9-4ce2-a96c-19c6360eb9e1 HTTP/1.0" 200 534 "-" "provisioningserver.pserv_services.tftp.TFTPBackend" [11:32] jojden: tha's the only thing I see [11:32] jojden: no other access to metadata [11:32] jojden: which should be there [11:32] jojden: that's leading me to believe that your machine, after accessing the pehemeral environment [11:32] is not really contacting the maas server [11:32] jojden: what's your /etc/maas/clusterd.conf ? [11:33] root@maascc:/etc/maas# cat clusterd.conf [11:33] cluster_uuid: 68ac4a87-16d9-4ce2-a96c-19c6360eb9e1 [11:33] maas_url: http://192.168.122.159/MAAS [11:35] roaksoax this is the content [11:36] jojden: so that tells me that 192.168.122.159 is the IP address of your region controller where the metadata server is running [11:36] jojden: do the machines have access to that IP ? [11:37] yes [11:37] correct [11:38] ping 192.168.122.159 [11:38] PING 192.168.122.159 (192.168.122.159) 56(84) bytes of data. [11:38] 64 bytes from 192.168.122.159: icmp_seq=1 ttl=64 time=0.241 ms [11:38] 64 bytes from 192.168.122.159: icmp_seq=2 ttl=64 time=0.205 ms [11:38] 64 bytes from 192.168.122.159: icmp_seq=3 ttl=64 time=0.181 ms [11:44] jojden: right, so the previous logs don't show that at all [11:44] jojden: what's in /etc/maas/regiond.conf ? [11:44] root@maasrc:/etc/maas# cat /etc/maas/regiond.conf [11:44] database_host: localhost [11:44] database_name: maasdb [11:44] database_pass: EnUx90XzXHy3 [11:44] database_user: maas [11:44] maas_url: http://192.168.122.159/MAAS [11:45] jojden: and why are your machines PXE with local=10.20.0.12&remote=10.20.0.174 ? [11:46] jojden: that seems that maybe KVM/libvirt running its own DHCP ? [11:46] jojden: which may be interfiering with MAAS's / [11:46] ? [11:47] actually [11:47] eth1 if maascc is 10.20.0.12 [11:47] *of maascc [11:47] jojden: right, so that's were MAAS is DHCP'ing from [11:48] but don't know abt remote=10.20.0.174 [11:48] :( [11:48] jojden: i think that's the IP that the machine is obtaining [11:48] let me verify [11:49] jojden: what happens if you change /etc/maas/clusterd.conf to point to 10.20.0.12 instead ? [11:49] jojden: if you change that and restart maas-clusterd [11:49] i think things iwll just go fine [11:50] ok [11:51] 174 is obtaining ip [11:51] :) [11:51] let me do as you said [11:52] maas_url: http://192.168.122.159/MAAS [11:52] to maas_url: http://10.20.0.12/MAAS [11:52] in /etc/maas/clusterd.con [11:52] right [11:54] resatarted [11:54] let me try to create node with pxe boot again. [11:54] deleting the old node [11:56] Bootfailed [11:56] not a bootable disk [11:56] i think I need to reconfigure with 10.20.0.12 [11:56] roaksoax [12:02] i think I need to reconfigure with 10.20.0.11 (eth1 of rc) [12:03] now booting [12:03] roaksoax [12:05] what is the best way to prevent a system to poweroff during enlisting? === BlackDex_ is now known as BlackDex [13:13] Bug #1585628 opened: [2.0] Bulk actions-Nodes action doesn’t apply should be red [13:34] Also, is there a way to force a specific metadata url? [13:34] or IP address? [13:35] using maas 2.0 btw [13:35] BlackDex, there's a backdoor image process, just a second [13:38] kiko: https://maas.ubuntu.com/docs/troubleshooting.html that one right? [13:39] for the backdoor [13:41] BlackDex: or you can modify /etc/maas/preseeds/enlist_userdata to do what you want [13:42] http://askubuntu.com/questions/499316/how-to-create-a-backdoor-add-a-login-to-ephemeral-images [13:45] roaksoax: Thx ;) Thats a quicker way [13:45] thx kiko, that comment above the commands explains the steps very wel [14:02] Bug #1585649 opened: [2.0b5] After changing proxy, MAAS cannot install images [14:38] Bug #1585666 opened: Subnets-> Reserved->Purpose - Rephrase migration message [15:41] Bug #1585684 opened: Nodes-When going back to nodes listing after performing a bulk action show filtered by selected === frankban is now known as frankban|afk [19:18] Bug #1585759 opened: [2.0RC1] Display RAM amount to the first decimal place in the UI [19:18] Bug #1585760 opened: [2.0RC1] Expose the refresh rack controller action over the UI [19:36] Bug #1585768 opened: [2.0RC1] Rename maas-nodegrou-worker to MAAS [20:08] I have a dirty VM, may be caused by that but seeing this problem: May 25 19:58:25 maas-xenial maas.dhcp: [ERROR] Could not rewrite DHCPv4 server configuration (for network interfaces ens3): Command `maas-rack atomic-write --filename /var/lib/maas/dhcpd.conf --mode 0644` returned non-zero exit status 1:#012None [20:08] this just hangs: root@maas-xenial:/var/log/maas# sudo /usr/sbin/maas-rack atomic-write --filename /var/lib/maas/dhcpd.conf --mode 0644 [20:08] 2.0b5 ^ [20:57] Bug #1565467 opened: twistd3 crashed with PermissionError in touch(): [Errno 13] Permission denied: '/etc/maas/rackd.conf'

[22:07] Bug #1585814 opened: MAAS fails to add a DHCP snippet with "subnet6 statement is only supported in DHCPv6 mode." [22:13] Hi, I've just installed: beta5+bzr5026 and I notice that this command is no longer supported: [22:13] maas admin node-groups list [22:14] what is it's replacement I wonder? [23:19] Bug #1585822 opened: Is it impossible to create multiple fabrics which have duplicated subnets from other fabrics