[01:13] Bug #1660211 changed: MAAS fails to properly configure two NICs with different subnets [04:19] Bug #1633663 changed: [2.1] Unlink interfaces creates a new link === frankban|afk is now known as frankban === junaidal1 is now known as junaidali [09:16] oke, i can't seem to find the correct place for the changelog [09:16] where can i find the changelog for 2.1.3, and also for the dev versions? [10:58] Hi someone problem with maas-region-controller trying to reinstall [10:58] https://pastebin.ubuntu.com/23875672/ [11:05] thiagolib, this seems to come up often. dunno. roaksoax? ^^^ [11:09] pmatulis: So I'm just trying to install the mass-region-controller without losing its dbconfig files. [11:51] hi [11:52] when deploying CentOS7 images I see "tar... mkdir: no space left on device" [11:52] doing the same deploy using CentOS6 or ubuntu image works fine [11:52] Any idea? [12:42] roaksoax: please ping me when ever you have time. [13:00] Hello there, i have a custom ubuntu image loaded into maas. And it worked perfectly until a few weeks ago. Now it doesn't configure the network config to be DHCP or static or any thing. [13:00] How can i force maas or curtain to put the network to dhcp in /etc/network/interface? [15:09] What is the current way to create custom images for Maas-2? [15:19] jlec__: you can do that several ways. What i did i just used kvm as a client, and extracted/tarred out all the data from that image, and uploaded that image to maas :) [15:19] don't forget to install cloud-init if you want key's and network etc.. to be correct [15:20] BlackDex: so the whole magic is stage 3 tarball plus cloud-init? [15:20] nice [15:20] * jlec__ likes that [15:22] jlec__: Also make sure to include curtin. [15:23] vogelc: does curtin come from pip? [15:23] mmh no [15:30] jlec__: I extracted it from / of build using the centos provided by MAAS. [15:31] That's also possible [15:32] Has any successfully implemented LVM for use on Centos? [15:33] During build curtin keeps trying to install grub on /dev/dm-0 and it complains it is an LVM device. [15:33] vogelc: curtin is distutils installable. so easy thing [15:35] vogelc: https://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/doc/topics/storage.rst seems to be some support for LVM in curtin [15:38] jlec__: thats exactly what I follow. Let me do a build and show the output. [15:38] vogelc: I am also fighting with CentOS and MAAS [15:43] jlec__: here is a link to my storage config. http://chopapp.com/#n7d4c4w1 [15:43] so you are really chunking it up? [15:44] Might be my problem too. [15:44] If I use standard partitions no LVM it works. [15:47] Here is the error: grub2-install: warning: File system `ext2' doesn't support embedding. grub2-install: error: embedding is not possible, but this is required for RAID and LVM install. [15:48] This is what is being run: ['chroot', '/tmp/tmpt0crqezh/target', 'grub2-install', '--recheck', '/dev/dm-0'] [16:03] Bug #1660370 opened: [UX Improvement] Surface the filter selection better on the UI [17:17] jlec: pong [17:35] went to commission my nodes [17:35] and now I see this [17:35] [error] ceph-mon1: Unable to set any default storage layout because it has no writable disks. [17:36] It was working, but we had to reset everything [17:36] now it isn't finding any of the disks? [17:58] also what username / password does MAAS create on the machine? I can't phyiscally login at the host! === frankban is now known as frankban|afk [18:33] went to recommission a node [18:33] [error] ceph-mon1: Unable to set any default storage layout because it has no writable [18:33] disks. [18:33] [error] ceph-mon1: Unable to set any default storage layout because it has no writable disks [18:48] Bug #1660418 opened: Uploading a new custom image does not remove the old image [18:59] is anyone aware of an update to knife for MAAS so it will work with api/2.0? [19:00] g3: commission your nodes with an HWE kernel [19:00] g3: the stock kernel probabaly doesnt; have the drivers [19:00] g3: and we use SSH to access a deployed system [19:22] roaksoax: is there some up2date guide around custom images? [19:23] roaksoax: I need ubuntu LTS including python, and I would like to create CentOS 7.3 images [19:24] roaksoax: secondly, I am trying to deploy CentOS. 6.6 works, but 7.0 with the same settings has problems with filesystem and network [19:55] jlec: what are your issues with centos7 ? the images that maas provides are the latest centos available as per their released cloud-images [19:58] roaksoax: interesting. They are still labelled 7.0 in Maas. As I cannot deploy them I neever could check what they really are. [19:58] roaksoax: How can I debug a failed deploy if the network setup fails? [19:59] roaksoax: Is there anything special I need ot do to the FS? I just set the whole disk to be / with xfs. Any suggestions? [20:04] jlec: yeah there's a bug for that [20:05] jlec: maas provides an installation log (you can see it in the WebUI or get it with: "maas admin node-results read system_id=4tbcnh result_type=1 | grep data | cut -d"\"" -f4 | base64 --decode" [20:06] maas node-results read system_id= result_type=1 | grep data | cut -d"\"" -f4 | base64 --decode [20:06] jlec: do that on a failed deployment machine [20:06] jlec: or you ncan get rsyslog form /var/log/maas/rsyslog/ [20:07] roaksoax: thanks. I will look into that tomorrow. Perhaps I can figure out what it is. [20:08] jlec: yeah, let me know./ We know there are some deployment failures with centos when deploying with UEFI === Salty is now known as SaltySolomon [20:08] which we are working on fixing [20:09] roaksoax: this is with a old IBM blade setup [20:11] roaksoax: only BIOS and manual power cycle [20:12] roaksoax: have you run into an error where curtin trys to install grub2 on /dev/dm-0 when using LVM on CentOS? This does not happen when using flat storage. [20:15] jlec: strange! [20:15] vogelc: maas doesn't support lvm+centos [20:18] roaksoax, how do you specify which kernel to use when commissioning? I've only seen that option via deploy [20:19] g3: in the settings page you can select which kernel you want to use. [20:20] Oh interesting [20:20] I'm curious as to why it was working before? [20:21] roaksoax: Is lvm and centos support on the roadmap? [20:42] Bug #1660439 opened: MAAS should automatically "vacuum" the database to remove deleted images. [20:42] Bug #1660440 opened: MAAS should notify users when boot image storage space is low [20:51] vogelc: it is but not in the next 6 months, we are prioritizing other work atm [22:27] hello does it works with something different than ubuntu ? [22:28] too nice to be good [22:28] what if i want to deploy centos or arch ? [22:29] im stuck to deploy only ubuntu ? [22:56] roaksoax, unfortunately that didn't work.. [23:17] hmp [23:34] netmonk: you can deploy centos [23:34] netmonk: maas provides centos images [23:35] Are you chatting with me? [23:35] g3: what didn't work? maas discovering storage on a HWE kernel ? [23:35] Yes you are correct [23:35] From the commissioning output of lshw it sees all of the drives [23:36] g3: what types of drives are these ? [23:36] but according to the logs in /var/log/maas it states that it is Unable to set any default storage layout because it has no writable disks. [23:36] it was working [23:36] but I swizzled some subnet things then started over [23:36] they are sata ssd's [23:36] and a pcie ssd [23:36] and on the OSD machines there are 12 sata spinners, 2 sata ssd's and 2 pcie ssd's [23:37] All 5 machines are reporting the same error of the disks are not writable [23:37] g3: uhmm strange... did you by anychance manually delete those disks and commissioning wont recognize them again ? [23:37] I didn't [23:37] I deleted the machines [23:37] and started over [23:37] g3: can you pleas efell a bug with details on what errors it is showing you and attaching logs so we can look into that ? [23:37] I can [23:38] bug comming but also a forumn post [23:38] https://ubuntuforums.org/showthread.php?t=2351047 [23:38] well basically there is a bug already [23:38] https://bugs.launchpad.net/maas/+bug/1573084 [23:48] g3: are you using MAAS 1.9 ? [23:49] no I jsut realized that [23:49] 2.1.3 [23:50] g3: please do file a bug and attach to it the cloud-init logs which you can get from /var/log/maas/rsyslog/ [23:54] Bug #1660495 opened: Can't commission node because it has no writable disks [23:58] done done and done