| === jhebden is now known as jhebden-lunch | ||
| mup | Bug #1787567 opened: MAAS Node Failed to Commision; Post PXE boot: Kernel Modules failed to load <MAAS:New> <https://launchpad.net/bugs/1787567> | 10:34 |
|---|---|---|
| boritek | hi. after adding hardware manually in maas with IPMI, it shows a green power button as it can see it is powered on, however maas cannot commission any machine | 11:29 |
| boritek | logs say: Failed to query node's BMC - (inew) - No rack controllers can access the BMC of node | 11:29 |
| boritek | hmm it just started to work now on one of the nodes | 11:47 |
| boritek | i dont know what changed | 11:47 |
| boritek | how can I rename a machine after it has been created? | 11:47 |
| boritek | what is the default user pass of a deployed ubuntu 18.04 image? | 12:28 |
| boritek | ok, i could rename it :) | 13:04 |
| roaksoax | boritek: you can ssh into it | 14:20 |
| boritek | roaksoax: with wich username and password? | 14:22 |
| roaksoax | boritek: no password | 14:23 |
| roaksoax | boritek: maas imports your ssh keys | 14:23 |
| roaksoax | when the machine is 'deployed' | 14:23 |
| roaksoax | boritek: ubuntu@ | 14:23 |
| boritek | roaksoax: the problem is that i am at a different machine right now | 14:24 |
| boritek | so I dont have the key | 14:24 |
| boritek | btw does maas only need a one-time pxe booting set on the server or a permanent pxe booting? | 14:25 |
| boritek | because my dell server keeps resetting to normal booting even though I set it to be on pxe network booting | 14:26 |
| roaksoax | boritek: when maas power manages the machine, it tells it to pxe boot | 14:33 |
| roaksoax | boritek: it is strange that the server is resetting to localboot | 14:33 |
| roaksoax | boritek: if you have manually changed that in the BIOS | 14:34 |
| boritek | roaksoax: i only changed it in the idrac settings | 14:40 |
| boritek | is it possible to save discovered items to "?achines" instead of to "Devides"? | 14:41 |
| boritek | to make it easier setting them up | 14:42 |
| roaksoax | boritek: yes | 14:42 |
| boritek | roaksoax: how? i can only add them to Devices but not to the Machines? | 14:43 |
| boritek | button says: "Save and go to device listing" | 14:45 |
| boritek | and Type only allows me to chooose: device and Interface | 14:47 |
| roaksoax | boritek: you are right | 14:58 |
| roaksoax | for some reason i thought i allowed you to make those machines | 14:59 |
| roaksoax | let me check | 14:59 |
| boritek | this thing is weird because it is the machine that is used most of the time and the most useful thing, Devices which are non-deployable things are far less ipmortant and not used most of the time | 15:00 |
| boritek | or maybe i am just overlooking something? | 15:01 |
| roaksoax | boritek: yeah it seems we never really finished it | 15:07 |
| roaksoax | maybe its only avialable over the PAI | 15:08 |
| roaksoax | boritek: you could file a bug though | 15:08 |
| boritek | how can I reach it through the API? | 15:13 |
| boritek | i guess through the maas command | 15:19 |
| boritek | i see I need to login even on the controller | 15:19 |
| boritek | btw, where do I need to open the bug report? | 15:20 |
| boritek | about the machine discovery addition | 15:20 |
| roaksoax | yes you can file abug if you would like | 15:32 |
| boritek | roaksoax: https://bugs.launchpad.net/maas/+bug/1787617 | 16:13 |
| mup | Bug #1787617 opened: Cannot add discovered units to "Machines" (only to "Devices") <MAAS:New> <https://launchpad.net/bugs/1787617> | 16:13 |
| roaksoax | boritek: thanks | 16:20 |
| boritek | yw | 16:20 |
| mup | Bug #1787621 opened: [2.5. [erformance] Every time I access the images tab I see RPC communication <performance> <track> <MAAS:Triaged> <https://launchpad.net/bugs/1787621> | 16:43 |
| mup | Bug #1787628 opened: [2.5, UI] Machines, Controllers, Dashboard, Events Details pages don't list all nodes <track> <ui> <MAAS:Triaged by blr> <https://launchpad.net/bugs/1787628> | 18:11 |
| mup | Bug #1787631 opened: [2.5, UI] IP address not shown when the machine is commissioning <MAAS:New> <https://launchpad.net/bugs/1787631> | 18:11 |
| mup | Bug #1787632 opened: [2.5, UI] IP address not shown when the machine is commissioning <2.5> <track> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1787632> | 18:11 |
| someguy123-web | hey guys, I've got a strange problem, not sure if I've done something wrong, or if this is a bug in MAAS enlistment | 18:33 |
| someguy123-web | https://gist.github.com/Someguy123/f379c90b677b1bbb59c4c297d266cbfa | 18:33 |
| someguy123-web | what's happening is that the node which is trying to enlist, for some reason, sends the full URL in the POST request | 18:33 |
| someguy123-web | commissioning, deployment etc. works just fine, it's just enlistment which is being strange | 18:34 |
| someguy123-web | oh boy | 18:41 |
| someguy123-web | a 3 year old bug | 18:41 |
| someguy123-web | https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1387281 | 18:41 |
| mup | Bug #1787637 opened: UEFI PXE grub boot fails for add-on adapter i350 1Gb interface <MAAS:New> <https://launchpad.net/bugs/1787637> | 18:47 |
| mup | Bug #1787637 changed: UEFI PXE grub boot fails for add-on adapter i350 1Gb interface <MAAS:New> <https://launchpad.net/bugs/1787637> | 18:50 |
| mup | Bug #1787637 opened: UEFI PXE grub boot fails for add-on adapter i350 1Gb interface <MAAS:New> <https://launchpad.net/bugs/1787637> | 18:59 |
| mup | Bug #1787637 changed: UEFI PXE grub boot fails for add-on adapter i350 1Gb interface <MAAS:Invalid> <https://launchpad.net/bugs/1787637> | 19:14 |
| mup | Bug #1787646 opened: Switch localboot to chain to the shim <track> <MAAS:Incomplete> <MAAS 2.3:Incomplete> <MAAS 2.4:Incomplete> <https://launchpad.net/bugs/1787646> | 20:14 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!