=== frankban|afk is now known as frankban [08:34] Hi! Can anybody consult me about commercial support? I sent form from website, but employee that answer the first message didn't answer anymore [11:25] roaksoax: ^ [11:39] Bug #1709284 opened: curtin does not put mount_options passed by MAAS into /etc/fstab [11:45] Bug #1709284 changed: curtin does not put mount_options passed by MAAS into /etc/fstab [11:51] Bug #1709284 opened: curtin does not put mount_options passed by MAAS into /etc/fstab [12:43] hello, I new to mass (first install), and I do not see the next action... I followed the doc and now I have one Region and Rack controller with the status Ⓧ, all the services in the rack controller are in Ⓧ and there is no hints to restart/reconfigure them! Thanks in advance for your suggestion [13:51] Does anyone know of a way to disable the archive.ubuntu.com repos and use custom repos during deployment? [13:51] I tried adding apt sources to the Curtin preseed, but nodes are still trying to reach out to archive.ubuntu.com [13:52] And you can't disable that repo in the UI [13:55] exoduswtf, https://docs.ubuntu.com/maas/2.2/en/manage-repos ? [13:55] or, ok, those cannot be disabled? [13:56] Correct [13:56] Would like to use an internal mirror without needing outbound access [14:02] hmm [14:03] dancn, not sure i follow. what instructions are you following and what are you expecting? [14:04] exoduswtf, maas is supposed to be offline-ready [14:06] pmatulis: instructions at https://maas.io/install; now I have purged all mass and reinstalled, and now I have a different problem: the rack controller is not auto created and maas-rack register (on the same host) do not have effect (the contoller show only "Region controller") even after a reboot [14:11] making progress: spotted in the log: Region not available: An error occurred while connecting: 113: No route to host... seem strange since they are on the same host... I will dig deeper... [14:12] dancn, yeah. those aren't really the docs. not that it will necessarily solve your problem but try looking at the doc URL above [14:13] pmautils, that hasn't been my experience...but I might be missing something obvious [14:13] pmatulis: spotted the problem: the cut and paste from the page MAAS/#/nodes?tab=controllers after clicking "Add rack controller" contains the wrong region controller IP!!! [14:13] I'm able to sync the images from an internal mirror, but the builds seem to still reach out to external repos [14:15] dancn, good stuff [14:15] exoduswtf, right. i'm going to look into it === Guest13936 is now known as med_ === med_ is now known as medberry [14:24] exoduswtf, can you confirm that there is no way to *edit* the 'Ubuntu archive' URL under the 'Package repositories' tab? [14:25] exoduswtf, also, what version of MAAS are you running? [14:26] Version 2.2.1 [14:27] Editing the default repo seems reasonable... [14:27] exoduswtf, so it works? [14:27] Let me test it and see [14:28] thanks [14:28] Thank you [14:29] works? [14:36] Works [14:37] Told ya it was probably something obvious [14:39] hmm, I still need a little help... the rack controller seems ok (everything green) but I am not able to configure the subnets and dhcp... something somewhere must be wrong... [14:39] for example in the interface table on the rack controller i see the line: [14:40] enp2s0f0 Physical fabric-3 untagged 10.123.0.0/24 (t1) 10.123.0.1 (Static assign) [14:40] Pmautils - Thanks for the help [14:40] but the "ip addr show enp2s0f0" does not show the assigned ip: 10.123.0.1 [14:40] (Static assign) [16:40] [14:40] Pmautils - Thanks for the help [14:40] [14:42] I also see the incoming dhcp request with tcpdump but nobody replies === medberry is now known as med_ [14:48] ok, after setting the ip manually on the interface with "sudo ip addr del 10.20.0.1/32 dev enp1s0f1" the dhcp started responding... [15:30] exoduswtf, in terms of UX then, i take it that it was not clear that the URL could be changed? [15:30] exodusftw, welcome === frankban is now known as frankban|afk [17:03] hi friends! [17:03] I am try using cloud-init at image CentOS, but I can not work like used curtin_userdata parameters the cloud-init. Does anyone know about this it working with CentOS? [19:09] Bug #1709284 changed: curtin does not put mount_options passed by MAAS into /etc/fstab [21:12] Bug #1709482 opened: removing filesystem resets partition name and filesystem [21:30] Bug #1709482 changed: removing filesystem resets partition name and filesystem [21:33] Bug #1709482 opened: removing filesystem resets partition name and filesystem