| mup | Bug #1761601 changed: [2.4] Multiple region/rack controller failures cause the UI to be very slow <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1761601> | 00:06 |
|---|---|---|
| parlos | Good Morning! | 06:08 |
| parlos | @ananke did you find a solution? | 06:08 |
| === frankban|afk is now known as frankban | ||
| mup | Bug #1763307 opened: MAAS unable to send power off to the node after commissioning it <MAAS:New> <https://launchpad.net/bugs/1763307> | 09:19 |
| ananke | parlos: I did. it's a known bug with ipmi timeouts while booting dell systems with idracs in a shared mode | 10:20 |
| ananke | parlos: https://bugs.launchpad.net/maas/+bug/1635107 | 10:20 |
| parlos | Great, so I should just be lucky that my shared idracs have worked out. :) | 10:27 |
| ananke | parlos: interesting that you didn't run into that problem | 10:28 |
| ananke | parlos: in my case I noticed that maas would power cycle the nodes roughly 60 seconds after turning them on. which is insane, because it's not even close to the amount of time required to POST | 10:29 |
| ananke | and afterwards, eventhough they booted to something from maas, maas didn't consider that as a valid comissioning | 10:29 |
| mup | Bug #1763307 changed: MAAS unable to send power off to the node after commissioning it <MAAS:Invalid> <https://launchpad.net/bugs/1763307> | 12:43 |
| roaksoax | ananke: that indicates there's a firmware issue | 13:43 |
| roaksoax | ananke: if the firmware is taking that log | 13:43 |
| roaksoax | ananke: if the firmware is taking that long | 13:43 |
| roaksoax | ananke: we have idrac's in our CI testing environments and non of these expose these issues | 13:43 |
| mup | Bug #1763010 changed: Block devices not discovered during commissioning <MAAS:Invalid> <https://launchpad.net/bugs/1763010> | 13:52 |
| ananke | roaksoax: firmware is up to date. however, the combination of the bios power cycling the shared NIC _and_ typical switch registering connection is causing the timeout to be long enough for maas to consider it a failure | 14:03 |
| ananke | clearly, it affects other people too. and this isn't the first time we see problems with shared idrac configuration. ironically enough, dell's own whitepaper on deploying maas specifically recommends using sharing nic setup | 14:05 |
| ananke | I may try the dedicated NIC for idracs and see how that behaves | 14:05 |
| roaksoax | ananke: what do you mean "sharing nic" ? | 14:05 |
| roaksoax | ananke: does that share a nic with the OS ? | 14:05 |
| ananke | roaksoax: idrac has two modes of operation: either dedicated NIC, or sharing the primary NIC with the system | 14:09 |
| ananke | and yes, the shared nic configuration does use the same nic that the OS would have access to | 14:10 |
| roaksoax | ananke: ugh!! that's ugly... i wouldn't use that at all IMHO | 14:10 |
| roaksoax | ananke: probably dell recommends it becuase they want ppl to use the "features" they built | 14:10 |
| roaksoax | but if they wanna use that, you might as well use AMT | 14:10 |
| roaksoax | ananke: and yes that's likely to cause a lot of issues | 14:11 |
| ananke | roaksoax: do you use the dedicated idrac port? does maas work correctly with it? | 14:12 |
| roaksoax | ananke: yeah we dont use shared nic at all | 14:12 |
| roaksoax | ananke: i have various dell systems in CI without shared nic config that work just fine | 14:13 |
| ananke | https://linux.dell.com/files/whitepapers/Deploying_Workloads_With_Juju_And_MAAS-14.04LTS-Edition.pdf . ohh, I think I might have misread that | 14:13 |
| roaksoax | ananke: some recent (*e.g. 1 year old) | 14:13 |
| ananke | 'r, as they will be powered on and off via IPMI commands, so be sure to turn on IPMI | 14:13 |
| ananke | over LAN. I' | 14:13 |
| roaksoax | ananke: some older (2/3 year old) systems | 14:13 |
| ananke | not sure why I thought this said to use in shared mode | 14:13 |
| ananke | I just now need a larger switch. I got 12 nodes in the stack currently, adding a couple more, and I only have a 24 port switch there | 14:14 |
| ananke | I wish the culprit of this issue was easier to identify though. maas itself offered little clue, other than the nodes 'failed' to commission | 14:15 |
| srihas | hi guys, How can I configure a sub-interface for ex. eth1.824 using MAAS ? | 15:28 |
| roaksoax | srihas: you need to add the vlan 824 in the same fabric | 15:47 |
| === frankban is now known as frankban|afk | ||
| Hey__ | Using a hyper-v VM.. my commmisining passes, however, it does not find storage. Do i simply Add Special and mount the drive? | 19:27 |
| srihas | roaksoax: i will try, thank you | 19:59 |
| ananke | hah, fio tests start at 1:00:00, eventhough they haven't ran yet | 20:25 |
| Hey__ | Maas changed my ipmi user and password: https://bugs.launchpad.net/maas/+bug/1523611 | 22:39 |
| Hey__ | when commissining | 22:39 |
| Hey__ | now it's frozen | 22:39 |
| Hey__ | This happenened during capture-lldp | 22:40 |
| Hey__ | This is the second time it's happened. | 22:41 |
| Hey__ | today | 22:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!