| godleon | https://www.irccloud.com/pastebin/VufwujBs/ | 06:40 |
|---|---|---|
| godleon | above is the content I got from /var/lib/maas/dhcp/dhcpd.leases in MAAS 1.9.3, is that normal? I thought one MAC address should always gets the same ip address, doesn't it ? | 06:41 |
| siva | roaksoax: Hi. I am getting MAAS commission fails issue. MAAS failed reason. http://paste.openstack.org/show/541592/ | 11:56 |
| siva | roaksoax : Could you please provide me the solution for this | 11:56 |
| siva | narindergupta: Hi . I am getting MAAS commission failed issue. Using MAAS 1.9.3. MAAS failed reason. http://paste.openstack.org/show/541592/ . I am not using any proxy or Firewall service . I saw the related issue from the following link https://bugs.launchpad.net/maas/+bug/1534013.Could you please provide me solution. | 12:37 |
| narindergupta | siva, i see you are using willy. Thats fine since I can not reproduce the issue will you please attached the log required as stated in bug https://bugs.launchpad.net/maas/+bug/1534013 looks like it needs the debugging. | 12:43 |
| narindergupta | please look for comment number #2 | 12:43 |
| narindergupta | also in our deployment we are not facing this issue in any of the lab. And it could be your environment specific. Like bridges on your jump host etc... | 12:44 |
| siva | narindergupta: Ok. Thank you. I will debug more. | 12:48 |
| narindergupta | siva, thanks | 12:50 |
| narindergupta | siva, also i think you need to look into console of VM whether pxe boot completes or not if not then it might be your network configuration of jumphost which might be breaking. If you can give me access to your environment then only i can have a look. | 12:52 |
| roaksoax | siva: Unforunately, same as last time, I cannot provide you with a solution when I don't even know what the issue is. Which is why I requested the cloud-init.log and cloud-init-output.log. That is found in the commissioning environment. For that, while you commission, you need to enable the SSH option and log into the server when it becomes available | 13:10 |
| roaksoax | also, Wily is End of Life already | 13:11 |
| siva | narindergupta: sorry. I am not authorized to give access as per my company policy. I have recorded video. I will send that. Please tell me how to send a video here. | 13:12 |
| narindergupta | siva, will you please look into roaksoax suggession as he is the product owner of MAAS and suggest you on MAAS. | 13:13 |
| siva | roaksoax: Yes. I tried as you said to get cloud-init.log. But i am unable to ssh to nodes from MAAS controller.. | 13:14 |
| roaksoax | siva: the other option, is to have a console log. Do you have a console log ? | 13:15 |
| siva | narindergupta: Ok. thank you. | 13:15 |
| siva | roaksoax: node console log? | 13:16 |
| siva | roaksoax: I have a small video. It has the info of how MAAS doing PXE boot then while running Cloud-init script, it was throwing network communication failed issue. Due to that commission failed may be. | 13:19 |
| roaksoax | siva: yes, if it is network communication issue then that's the reason why commissioning failed | 13:22 |
| siva | roaksoax: I am thinking Due to that network issue client node not able get internet access . Then Commission process is waiting upto 20 minutes and then throwing commission failed issue. | 13:22 |
| roaksoax | siva: yeah because while it access commissioning, i'm guessing it never finishes and maas waits for it to fail | 13:23 |
| roaksoax | siva: ok, so you need to look into why it is not accessing ? | 13:23 |
| roaksoax | siva: so are you under a proxy ? the machines don't have access to the internet ? have you set an upstream DNS server ? | 13:23 |
| siva | roaksoax: No. I didn't configure any proxy . | 13:24 |
| roaksoax | siva: so is MAAS directly connected to the internet and NOT the machines it manages ? | 13:26 |
| siva | roaksoax: In MAAS server I have taken two NICs. For One NIC I have given public network. Second NIC I configured as a extrenal router. And then i used IP forwarding. Then I installed virtual box. From virtual box I created one VM. I have one nic In this VM. | 13:31 |
| siva | roaksoax: And I configured virtual box VM interface with bridge network | 13:33 |
| siva | roaksoax: Now I installed MAAS on Virtuaklbox VM. Now maas controller and its clients are in the same network | 13:34 |
| siva | roaksoax: With single interface MAAS will manage both DHCP and DNS. | 13:37 |
| roaksoax | siva: right, to me it seems like an issue with the forwarding or similar | 13:54 |
| roaksoax | siva: have you tried putting an upstream DNS ? | 13:54 |
| roaksoax | siva: under the settings page ? | 13:54 |
| mup | Bug #1605756 changed: [ juju2 beta11 ] system show up in juju status as pending but there is no attempt to deploy in maas <oil> <oil-2.0> <juju-core:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1605756> | 13:55 |
| mup | Bug #1605756 opened: [ juju2 beta11 ] system show up in juju status as pending but there is no attempt to deploy in maas <oil> <oil-2.0> <juju-core:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1605756> | 14:10 |
| mup | Bug #1605756 changed: [ juju2 beta11 ] system show up in juju status as pending but there is no attempt to deploy in maas <oil> <oil-2.0> <juju-core:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1605756> | 14:16 |
| siva | roaksoax: No. i didn't tried. can I try it now? | 14:21 |
| roaksoax | siva: yeah you can try that. For example use 8.8.8.8 as upstream DNS and see if that fixes any resolution errors | 14:26 |
| siva | roaksoax; OK. thank you. | 14:27 |
| mup | Bug #1606264 opened: dns_servers and ntp_servers in _ConfigureDHCP are defined as strings <tech-debt> <MAAS:Triaged> <https://launchpad.net/bugs/1606264> | 14:55 |
| siva | roaksoax: Hi. I tried with 8.8.8.8 , 8.8.4.4 and local name server . But it was showing the same network communication failed issue. And In maas.log showing Marking node failed: Node operation 'Commissioning' timed out after 0:20:00. | 15:04 |
| roaksoax | siva: so /etc/maas/clusterd.conf , what does maas_url= say ? | 15:18 |
| === valeech_ is now known as valeech | ||
| siva | roaksoax: maas_url: http://192.168.10.2:5240/MAAS . | 15:21 |
| siva | roaksoax: I tried first with maas_url: http://localhost:5240/MAAS. Next instead of localhost I configured Cluster controller with IP. | 15:23 |
| mup | Bug #1606281 opened: omapi code does not deal well with ipv6 addresses <MAAS:Incomplete> <https://launchpad.net/bugs/1606281> | 15:31 |
| mup | Bug #1606329 opened: MAC address accessible in web UI, but UI is VERY obscure <MAAS:New> <https://launchpad.net/bugs/1606329> | 17:26 |
| roaksoax | siva: is 192.168.0.2 an IP address that the machines can access to ? | 19:41 |
| roaksoax | /win/win 3 | 20:16 |
| === valeech_ is now known as valeech | ||
| === valeech_ is now known as valeech | ||
| mup | Bug #1606386 opened: Apt Upgrade fails for maas-region-controller 2.0.0~rc2+bzr5156 to 2.0.0~rc3+bzr5171 <MAAS:New> <https://launchpad.net/bugs/1606386> | 21:59 |
| mup | Bug #1606386 changed: Apt Upgrade fails for maas-region-controller 2.0.0~rc2+bzr5156 to 2.0.0~rc3+bzr5171 <MAAS:New> <https://launchpad.net/bugs/1606386> | 22:29 |
| mup | Bug #1606386 opened: Apt Upgrade fails for maas-region-controller 2.0.0~rc2+bzr5156 to 2.0.0~rc3+bzr5171 <MAAS:New> <https://launchpad.net/bugs/1606386> | 22:32 |
| mup | Bug #1606386 changed: Apt Upgrade fails for maas-region-controller 2.0.0~rc2+bzr5156 to 2.0.0~rc3+bzr5171 <MAAS:New> <https://launchpad.net/bugs/1606386> | 22:35 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!