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