[00:13] Bug #1651280 opened: [2.1] MAAS fails to add SSH keys is server has duplicate keys [05:29] Bug #1651316 opened: Disks are found but not shown [05:35] Bug #1651316 changed: Disks are found but not shown [05:41] Bug #1651316 opened: Disks are found but not shown [12:02] I have local ubuntu local mirror, but mirroring only binary-amd64. When I commissioning nodes using trusty all is ok, when I’m using xenial I have commissioning failed status with erorrs on “Node commissioning failure - 'cloudinit' running config-apt-configure with frequency once-per-instance” and “Node commissioning failure - 'cloudinit' running modules for config” Does xenial need sources? in messages i got: Dec 20 11:26:04 adada-006 cloud-init[3158]: E: [12:02] Failed to fetch http://IP/ubuntu/dists/xenial-updates/InRelease Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file) [12:02] Dec 20 11:26:04 adada-006 cloud-init[3158]: E: Failed to fetch http://IP/ubuntu/dists/xenial-backports/InRelease Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file) [12:02] Dec 20 11:26:04 adada-006 cloud-init[3158]: E: Failed to fetch http://IP/ubuntu/dists/xenial-security/InRelease Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file) [12:02] Dec 20 11:26:04 adada-006 cloud-init[3158]: E: Some index files failed to download. They have been ignored, or old ones used instead. [12:03] someone have the same isssue? or can help me with it? === zz_CyberJacob is now known as CyberJacob [12:05] or i missed something? [12:13] from my experience if apt-get doesn't return 0 cloudinit return a failure [12:14] I had to edit sources.list to remove all the repo I didn't have [12:19] hmm, i think i do this in proper way [12:19] i put in /etc/cloud/cloud.cfg.d/99-apt-preserve-sources-list.cfg ‘apt_preserve_sources_list: True' [12:20] remove entires from /etc/cloud/templates/sources.list.ubuntu.tmpl [12:20] but it’s look like cloud init dont process proper this [12:21] in head of this template is written [12:21] ## template:jinja [12:21] ## Note, this file is written by cloud-init on first boot of an instance [12:21] ## modifications made here will not survive a re-bundle. [12:21] ## if you wish to make changes you can: [12:21] ## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg [12:21] ## or do the same in user-data [12:21] ## b.) add sources in /etc/apt/sources.list.d [12:21] ## c.) make changes to template file /etc/cloud/templates/sources.list.tmpl [12:32] I don't know if I did it correctly but I changed it in boot image [14:27] Bug #1651450 opened: [2.1, UI] All the "information" icons are replaced by "attention" icons === Guest67717 is now known as med_ [14:57] Bug #1651452 opened: EFI systems don't boot under maas in 2.1.3-proposed [14:57] Bug #1651455 opened: [2.1] For debugging purposes, we need a way to obtain a rendered PXE/grub config sent to machines on tftp [23:37] Bug #1651602 opened: [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails