| oyrogerg | Hi, is anyone around? | 04:55 |
|---|---|---|
| oyrogerg | Just in case: I would like to have our maas-dhcp server listen on four interfaces. | 04:56 |
| oyrogerg | I can make it briefly do that by adding them to /var/lib/maas/dhcpd-interfaces, but it quickly gets reverted | 04:57 |
| oyrogerg | A dirty solution is to chattr +i /var/lib/maas/dhcpd-interfaces (!) so that /usr/lib/maas/maas-write-file fails to revert it, but I'd like to do it more cleanly if possible. | 04:57 |
| === frankban|afk is now known as frankban | ||
| oyrogerg | I put the question here https://askubuntu.com/questions/956892/how-do-i-get-maas-dhcp-to-listen-on-multiple-interfaces | 08:18 |
| c06_ | hi all | 11:02 |
| c06_ | anyone on? | 11:02 |
| c06_ | facing "Marking node failed: Power on for the node failed: Could not contact node's BMC: Connection timed out while performing power action. Check BMC configuration and connectivity and try again." | 12:24 |
| c06_ | any suggestions? | 12:24 |
| mwe1 | c06: which BMC type? | 12:29 |
| c06_ | mwe1: ipmi | 12:29 |
| mwe1 | which hardware vendor? | 12:30 |
| c06_ | hp | 12:30 |
| mwe1 | have you checked the BMC variables (Nodes -> <select Node> -> Power? | 12:33 |
| mwe1 | is there any configurattion (IP address, etc.)? | 12:34 |
| c06_ | actually my machine got list as NEW state, and while doing commissioning getting the error | 12:35 |
| mwe1 | maas should detect the ipmi configuration during the commissioning task. Is IPMI already configured and accessibbe from the maas server? | 12:36 |
| mwe1 | AFAIK mass doesn't configure IPMI except adding a user (and activate IPMI over LAN) | 12:37 |
| c06_ | mwe1: we configured our maas server with nodes. unfortunately we lost the connectivity between maas and nodes. after that we are facing this issue | 12:40 |
| c06_ | mwe1: we removed the existing machine from maas and we restarted the nodes with PXE and the machine got into NEW state; while trying commission-> we are getting the above error | 12:41 |
| mwe1 | That means the machine is able to PxE-Boot via maas. After detecting (State 'NEW') the machine is automatically powered off by the PxE-bootet image. until now it seems to be fine. but... | 12:43 |
| mwe1 | Now MaaS has to start the machine to start the commission task. Because of not working IPMI MaaS isn't able to bootup the machine | 12:45 |
| mwe1 | look at the 'Power' configuration at the machine. Is everyting OK? | 12:46 |
| c06_ | mwe1: yes one sec i share whole logs may be that ll be help | 12:47 |
| mwe1 | If yes try to connect to the IPMI interface from the MaaS server. Is that working? | 12:47 |
| mwe1 | If Yes, look at the users-page of the IPMI-Interface. is there a user called 'maas'? | 12:48 |
| c06_ | give me a sec; i am checking... error logs https://paste.linux.community/view/95553113 | 12:48 |
| mwe1 | The logs of the commissioning-task would be great. | 12:48 |
| c06_ | mwe1: i think tat is the above log | 12:49 |
| mwe1 | --> Failed to change the boot order to PXE 10.3.18.26: /usr/sbin/ipmi-config: connection timeout | 12:49 |
| mwe1 | is the IP accessible from within the maas server? | 12:50 |
| c06_ | i am trying to 10.3.18.26. but its not accessable. any other command to check connectivity | 12:52 |
| c06_ | mwe1: becoz those IP are listing in MAAS dashbaord. !!! | 12:52 |
| mwe1 | als always: the network guys are resposible for your pain :D | 12:53 |
| c06_ | mwe1: oops morning its working fine. i will check with network people.. :( | 12:53 |
| mwe1 | what's the output of 'ping 10.3.18.26' (from within your maas server) | 12:54 |
| c06_ | mwe1: one sec 10.3.18.26 , 10.3.18.xx ip's are listing in subnet tab in MAAS dashboard | 12:54 |
| mwe1 | Do you have an ssh shell to your maas server? | 12:56 |
| c06_ | yes i have ping not working 100% packet loss | 12:56 |
| mwe1 | (at this point forget your dashboard ;-) ) | 12:56 |
| mwe1 | ip route ? | 12:56 |
| mwe1 | (is there a default GW) | 12:57 |
| c06_ | mwe1: its pinging; deault gw changed and its in dummy interface. now i changed to my network and its pinging | 12:58 |
| mwe1 | cool! try to commision your machine, again | 12:59 |
| c06_ | ok ty i am trying and i ll ping once i got the result.. ty dude.. :) | 13:00 |
| mwe1 | GW to dummy interface looks funny. | 13:00 |
| mwe1 | You're welcome | 13:00 |
| c06_ | mwe1: we are first time trying MAAS so only.. | 13:02 |
| === Sagar is now known as Guest14056 | ||
| Guest14056 | #roaksoax | 13:43 |
| Guest14056 | @roaksoax: Last week I was checking with you on uploading custom images in MAAS. You mentioned that currently MAAS does not support it, but there could be a workaround by modifying index.json | 13:44 |
| Guest14056 | I looked at the file and it is GPG encrypted | 13:45 |
| Guest14056 | any idea if I need to go non-secure way then you will I need to modify things? | 13:45 |
| v92 | hi, do you have any idea what issue can be when I have two A records for host but only one is valid ? | 13:46 |
| v92 | zone.maas:exp-imf-a-7 30 IN A 192.168.0.153 | 13:46 |
| v92 | zone.maas:exp-imf-a-7 30 IN A 192.168.0.165 | 13:46 |
| v92 | 192.168.0.165 is not allocated to host exp-imf-a-7 | 13:46 |
| v92 | only 0.153 | 13:47 |
| mwe1 | c06_: did it work? | 13:48 |
| c06_ | mwe1: Node failed to be commissioned, because of the following error: No rack controllers can access the BMC of node: maas | 13:52 |
| c06_ | i am searching in online so i forgot to ping | 13:52 |
| c06_ | mwe1: i configured dpkg-reconfigure maas-region-controller and maas-rack-controller to my maas node ip but still same error | 13:54 |
| mwe1 | but pinging from maas server (ssh) to the BMC is still working? 'ping 10.3.18.26' | 13:55 |
| mwe1 | maybe network-manager has reconfigured your gateway. | 13:56 |
| c06_ | yes ping is working to gateway. | 13:56 |
| c06_ | i think nodes are in shutdown state so ping to that particular node not working | 13:57 |
| mwe1 | ping to BMC should work in shutdown state also :D | 13:57 |
| mwe1 | that's the funktion of BMCs ;-) | 13:58 |
| c06_ | mwe1: serious oops its not working.. | 13:58 |
| c06_ | mwe1: i think as you told previously some admin people maybe played with network.. :( | 13:59 |
| mwe1 | as always: It's a network related issue :-) | 13:59 |
| c06_ | ok mwe1 ty for your suggestion i ll check with admin team :-D | 14:00 |
| mwe1 | It might be possible that your maas-server is changing the gateway entries from time to time. | 14:00 |
| c06_ | mwe1: my maas-server i didnt configure related to 10.3.18.x ip | 14:01 |
| mwe1 | So when you change it manually it will be reconfigured after a short timeperiod. | 14:01 |
| c06_ | **under subnet tab | 14:01 |
| mwe1 | Isn't it your default gateway that is changed? | 14:02 |
| c06_ | yes i changed in my maas machine after from maas server able to ping gateway(BMC-ipmi) | 14:02 |
| mwe1 | try setting your default gateway manually, again and test the ping. | 14:02 |
| mwe1 | if it works the commissioning should work also. | 14:03 |
| c06_ | i think in maas server some network configuration changes | 14:04 |
| c06_ | **changed.. from other machine able to ping to BMC(10.3.18.x).. oops i got into mess i think | 14:05 |
| mwe1 | what's the output of 'ip route' | 14:07 |
| mwe1 | (at the maas server) | 14:07 |
| c06_ | mwe1: https://paste.linux.community/view/12fcd22c | 14:14 |
| mwe1 | whith this configuration your BMC is pingable? | 14:15 |
| c06_ | its pinging to gateway but not going to other BMC | 14:16 |
| mwe1 | are you able to login to your gateway? | 14:16 |
| c06_ | am not having credential for that gateway | 14:17 |
| mwe1 | Than you have to contact your network-admins, I think :-( | 14:18 |
| c06_ | ok i think so i will try | 14:20 |
| mwe1 | forwarding from 192.168.0.0/24 to 10.3.18.0/24 via 192.168.0.254 has to work in order to install your maas setup. | 14:20 |
| mwe1 | that's your missing point, I think. | 14:20 |
| mwe1 | good luck | 14:21 |
| mwe1 | I have to leave for today. | 14:21 |
| c06_ | thanks four time and suggestion | 14:21 |
| mwe1 | You're welcome. | 14:21 |
| c06_ | thanks dude.. if possible tomorrow i ll ping | 14:21 |
| c06_ | have a nice day.. :) | 14:21 |
| mwe1 | cu | 14:21 |
| c06_ | :) | 14:21 |
| mup | Bug # changed: 1532047, 1621175, 1642298, 1676992, 1681801, 1684094, 1686246, 1688066, 1702703, 1703035, 1707850, 1708512, 1711414, 1711700, 1711714, 1712422, 1712423, 1712450, 1714273, 1715634 | 15:00 |
| mup | Bug #1717669 changed: Ephemeral boot has broken DNS <MAAS:New> <https://launchpad.net/bugs/1717669> | 15:21 |
| mup | Bug #1689557 changed: replace iscsi usage in ephemeral image with rooturl <MAAS:Fix Released by ltrager> <maas-images:Fix Released by ltrager> <https://launchpad.net/bugs/1689557> | 16:00 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1717983 opened: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration <amd64> <apparmor> <apport-bug> <artful> <avahi (Ubuntu):New> <cloud-init (Ubuntu):New> <controlaula (Ubuntu):New> <ddclient (Ubuntu):New> <dracut (Ubuntu):New> <ifupdown (Ubuntu):New> | 17:47 |
| mup | <ifupdown2 (Ubuntu):New> <initramfs-tools (Ubuntu):New> <isc-dhcp (Ubuntu):New> <libguestfs (Ubuntu):New> <maas (Ubuntu):New> <madwimax (Ubuntu):New> <netscript-2.4 (Ubuntu):New> <network-manager (Ubuntu):New> <ntp (Ubuntu):New> <openresolv (Ubuntu):New> <resolvconf (Ubuntu):New> <samba | 17:47 |
| mup | (Ubuntu):New> <sendmail (Ubuntu):New> <ubuntu-meta (Ubuntu):New> <walinuxagent (Ubuntu):New> <whereami (Ubuntu):New> <wicd (Ubuntu):New> <wifi-radar (Ubuntu):New> <https://launchpad.net/bugs/1717983> | 17:47 |
| mup | Bug #1717612 changed: MAAS uses region IP address for default DNS server, but DNS is provided by rack controllers <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Invalid> <https://launchpad.net/bugs/1717612> | 18:36 |
| mup | Bug #1718016 opened: MAAS failed to respond to POST'd deploy request but still deployed node <cdo-qa> <cdo-qa-blocker> <MAAS:New> <https://launchpad.net/bugs/1718016> | 19:43 |
| mup | Bug #1718016 changed: MAAS failed to respond to POST'd deploy request but still deployed node <cdo-qa> <cdo-qa-blocker> <MAAS:New> <https://launchpad.net/bugs/1718016> | 19:46 |
| mup | Bug #1718016 opened: MAAS failed to respond to POST'd deploy request but still deployed node <cdo-qa> <cdo-qa-blocker> <MAAS:New> <https://launchpad.net/bugs/1718016> | 19:49 |
| mup | Bug #1718039 opened: regiond logs errors when rackd not installed <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1718039> | 20:49 |
| mup | Bug #1718039 changed: regiond logs errors when rackd not installed <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1718039> | 20:58 |
| mup | Bug #1718039 opened: regiond logs errors when rackd not installed <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1718039> | 21:07 |
| mup | Bug #1718039 changed: regiond logs errors when rackd not installed <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1718039> | 21:19 |
| mup | Bug #1718044 opened: [2.2] Failed to process node status messages - twisted.internet.defer.QueueOverflow <MAAS:New> <https://launchpad.net/bugs/1718044> | 21:19 |
| mup | Bug #1718046 opened: [2.2, HA] could not serialize access due to concurrent update <MAAS:New> <MAAS 2.2:New> <https://launchpad.net/bugs/1718046> | 21:19 |
| mup | Bug #1718048 opened: [2.3] Traceback when no available machine matches constraints <MAAS:Triaged> <https://launchpad.net/bugs/1718048> | 21:19 |
| mup | Bug #1718048 changed: [2.3] Traceback when no available machine matches constraints <cdo-qa> <foundations-engine> <MAAS:Invalid> <https://launchpad.net/bugs/1718048> | 22:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!