[10:15] <julen> Hi there! Is there any way to access them during the nodes during commissioning?
[10:15] <julen> I mean, the nodes...
[10:56] <mup> Bug #1702276 opened: [2.2.1] Unable to add interface to device <MAAS:New> <https://launchpad.net/bugs/1702276>
[12:44] <ybaumy> so if anyone has a problem scanning vmware nodes on the vcenter and adding them to maas. you might want to take a look at https://bugs.launchpad.net/maas/+bug/1701476
[12:44] <ybaumy> i could find a solution
[13:07] <julen> Even do I set a custom NTP server, the nodes keep trying to reach ntp.ubuntu.com. Is there an easy way around that?
[13:55] <D4RKS1D3> It could be possible to deploy an OS with command line?
[13:55] <D4RKS1D3> maas ubuntu node commission node-xxxxx
[13:55] <D4RKS1D3> thanks
[13:57] <julen> @D4RKS1D3: Definitely
[13:57] <D4RKS1D3> could you explain me how?
[13:57] <D4RKS1D3> @julen
[13:58] <julen> I am not super expert, but it is the same as with all the rest of the environments, like virsh, opestack, lxc, docker, ...
[13:59] <julen> it's just about the syntax
[13:59] <julen> let me check very quick
[13:59] <julen> maas ubuntu machines read
[13:59] <julen> that shows the available machines
[14:00] <julen> maas testmaas machine -h
[14:00] <julen> that shows all the options
[14:02] <ybaumy> i have another problem now. maas is displaying 0 for memory
[14:02] <ybaumy> so when i use juju bootstrap. the command cannot find any machine with memory
[14:04] <julen> memory for the node?
[14:04] <julen> that is probably because the node has not been commissioned propely
[14:05] <ybaumy> julen: it says ready after commisioning
[14:05] <julen> oh! ok...
[14:06] <ybaumy> root@maas:~# maas baum machines read  | grep memory "memory": 0,
[14:06] <ybaumy> there is everywhere 0 for all machines
[14:06] <julen> so, if you make "maas ubuntu machines read |grep memory" it shows "memory": 0,   right?
[14:06] <ybaumy> correct
[14:07] <julen> is the CPU and the Disk info OK?
[14:07] <ybaumy> julen: yes thats correct
[14:07] <ybaumy> maybe that because i use vcenter 6.5
[14:08] <D4RKS1D3> @julen I saw that info but is nothing with deploy...
[14:09] <ybaumy> i tried juju bootstrap cloud ctrl --constraints mem=0G
[14:09] <ybaumy> but memory is set again to default value
[14:09] <julen> I don't know... maybe check on the commissioning logs, on the "00-maas-01-lshw" or something
[14:09] <ybaumy> not 0
[14:10] <julen> can you deploy the machines without juju?
[14:10] <ybaumy> gonna try
[14:15] <ybaumy> this works
[14:15] <ybaumy> but still no memory information
[14:16] <ybaumy> i will file a bugreport later
[14:16] <ybaumy> gotta go now
[14:17] <julen> ybaumy: then it is probably on the juju side
[15:47] <mup> Bug #1702329 opened: Set NTP server for 'timesyncd' <ntp> <MAAS:New> <https://launchpad.net/bugs/1702329>
[15:50] <mup> Bug #1702329 changed: Set NTP server for 'timesyncd' <ntp> <MAAS:New> <https://launchpad.net/bugs/1702329>
[15:53] <mup> Bug #1702329 opened: Set NTP server for 'timesyncd' <ntp> <MAAS:New> <https://launchpad.net/bugs/1702329>
[16:23] <mup> Bug #1702332 opened: http_proxy only for apt? <http-proxy> <MAAS:New> <https://launchpad.net/bugs/1702332>
[18:01] <ThiagoCMC> guys, I'm seeing that MaaS 2.2 is now at the PPA maas/stable, however, I'm on maas/next PPA. So, to "upgrade" to maas/stable, can I just run: "add-apt-repository ppa:maas/stable ; apt update ; apt full-upgrade ; ppa-purge ppa:maas/next" ?
[18:02] <ThiagoCMC> Sorry, I'll not run "apt full-upgrade" before "ppa purge ppa:maas/next"!
[18:03] <ThiagoCMC> Otherwise, it will upgrade from maas/next and the version that I have installed now, is the same that is now at maas/stable.
[18:29] <pmatulis> ThiagoCMC, what version are you on now? 2.2.0 is in 'stable'
[18:29] <pmatulis> and 2.2.1 is in 'next'
[18:31] <ThiagoCMC> I did not upgraded to 2.2.1. I have the same version that it is now at maas/stable (2.2.0+bzr6054).
[18:32] <ThiagoCMC> Looks like that if I move from maas/next (not upgraded to its latest), I'll end up with the same version, but diff PPA...
[18:32] <ThiagoCMC> I mean, from maas/next to maas/stable.
[18:33] <pmatulis> yes, correct, if you're on 2.2.0
[18:33] <pmatulis> ThiagoCMC, personally, i would just comment out the 'next' PPA lines (in its file) and then add 'stable'. then un/commenting lines you can toggle in the future
[18:34] <ThiagoCMC> Hmm... That might be a better idea.
[18:34] <ThiagoCMC> =)
[18:35] <ThiagoCMC> But I already executed the ppa-purge... lol
[18:35] <ThiagoCMC> Nothing really happened: "maas is already the newest version (2.2.0+bzr6054-0ubuntu1~16.04.1)."   :-D
[18:35] <ThiagoCMC> Worked!
[18:35] <ThiagoCMC> Just "curtin-common python3-curtin" and received a small upgrade.
[18:36] <ThiagoCMC> I mean, downgrade.
[18:36] <ThiagoCMC> Sorry, up! Damn...
[18:36] <ThiagoCMC> "Unpacking curtin-common (0.1.0~bzr505-0ubuntu1~16.04.1) over (0.1.0~bzr482-0ubuntu1~16.04.1)"
[18:36] <ThiagoCMC> Cheers!
[18:36] <pmatulis> it's all good. nicely done
[18:38] <ThiagoCMC> Thanks!