| stormmore | r/b 7 | 00:33 |
|---|---|---|
| mup | Bug #1711012 opened: package maas-region-controller 2.2.0+bzr6054-0ubuntu2~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 <amd64> <apport-package> <xenial> <maas (Ubuntu):New> <https://launchpad.net/bugs/1711012> | 02:23 |
| === frankban|afk is now known as frankban | ||
| mup | Bug #1710241 opened: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241> | 06:15 |
| jlec___ | hi guys | 07:38 |
| jlec___ | for the curtin preseed file nomenclature, what is the _{hostname}? Is it the hostname part of the FQDN in MAAS? | 07:39 |
| D4RKS1D3 | hi jlec___ prefix_osystem_nodearch_nodesubarch_release_nodename | 09:05 |
| jlec___ | D4RKS1D3: yes, correct, not hostname but nodename. But what exactly is the node name? The system_id? of the hostname in the FQDN? | 09:06 |
| D4RKS1D3 | is the mac address | 09:07 |
| D4RKS1D3 | jlec___, If you sniff the traffic between the machine you are comissioning and the maas controller you can see the sequence of the tftp protocol | 09:14 |
| jlec___ | I have it enlisted and commisioned already. Just want to target a specific node ofr the preseed development | 09:16 |
| D4RKS1D3 | in the tftp rfc you have the standard of the protocol and the sequence | 09:19 |
| D4RKS1D3 | sorry jlec___ in the tftp rfc no, is the pxe rfc | 09:21 |
| jlec___ | There must be an easier way to name the curtin file | 09:22 |
| D4RKS1D3 | jlec___, you mean in maas? | 09:25 |
| jlec___ | D4RKS1D3: yes, in prefix_osystem_nodearch_nodesubarch_release_nodename, where do I get the nodename from? | 09:26 |
| D4RKS1D3 | but that way not have any sense | 09:26 |
| D4RKS1D3 | When you install a new machine, the machine doesn't exist in maas | 09:27 |
| D4RKS1D3 | and you need to inject the curtin file | 09:27 |
| D4RKS1D3 | the only unique in the hardware is the mac | 09:28 |
| D4RKS1D3 | are you agree with me? | 09:28 |
| jlec___ | no, this is the curtin for deployment. there are others for enlisting and commisioning. These are the stages where MAAs doesn't know anything about the node. | 09:29 |
| jlec___ | After commisioning Maas does | 09:29 |
| jlec___ | Also the osystem_nodearch_nodesubarch_release comes from your deployment selection | 09:29 |
| D4RKS1D3 | yes, you are right | 09:34 |
| === kukacz_ is now known as kukacz | ||
| === kukacz_ is now known as kukacz | ||
| mup | Bug #1710241 changed: Cannot deploy customized ubuntu cloud image <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1710241> | 12:24 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1711191 opened: [2.3, artful] maasserver.websockets.protocol: [critical] Error on request (24) bootresource.poll: 'DistroRelease' object is not subscriptable <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1711191> | 18:04 |
| mup | Bug #1711191 changed: [2.3, artful] maasserver.websockets.protocol: [critical] Error on request (24) bootresource.poll: 'DistroRelease' object is not subscriptable <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1711191> | 18:07 |
| mup | Bug #1711191 opened: [2.3, artful] maasserver.websockets.protocol: [critical] Error on request (24) bootresource.poll: 'DistroRelease' object is not subscriptable <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1711191> | 18:19 |
| marcoceppi | can we boot ubuntu-core with maas yet? | 19:21 |
| mup | Bug #1711203 opened: Deployments fail when Secure Boot enabled <MAAS:New> <https://launchpad.net/bugs/1711203> | 19:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!