/srv/irclogs.ubuntu.com/2018/05/17/#maas.txt

roaksoaxsentinel-prime: here00:18
sentinel-primeo/00:18
roaksoaxsentinel-prime: yes, so since you are using NAT00:18
roaksoaxsentinel-prime: the machines dont have access to the internet00:18
roaksoaxsentinel-prime: so you need to do iptables to allow them to access the internet00:18
roaksoaxsentinel-prime: or set http_proxy on the machines to use the proxy00:18
sentinel-primehttp proxy needs to be set in the maas controlor right00:19
sentinel-primeif so that is set tto maas built in00:20
sentinel-primeon the setting page00:20
roaksoaxsentinel-prime: right, but maas doesn't set http_proxy on the system. it only sets apt's proxy00:21
sentinel-primeso i have to set it to exturnal00:21
sentinel-primeor peer00:21
roaksoaxsentinel-prime: no00:22
roaksoaxsentinel-prime: the built-in proxy is fine00:22
roaksoaxsentinel-prime: but when the machine is deployed00:22
roaksoaxsentinel-prime: the deployed machine only gets apt proxy set, which allows apt to access the mirrors, but just for apt00:24
roaksoaxsentinel-prime: if you want the system itself to have accecess00:24
roaksoaxsentinel-prime: you can do: export http_proxy=http://ip-of-maas-server:8000/00:25
roaksoaxexport http_proxy=http://ip-of-maas-server:8000/00:25
roaksoaxexport https_proxy=http://ip-of-maas-server:8000/00:25
roaksoaxsentinel-prime: or you can try in port 312800:25
sentinel-primethats the command right00:29
sentinel-prime?00:35
roaksoaxsentinel-prime: yes, in the installed system you can do:00:36
roaksoaxexport http_proxy=http://ip-of-maas:8000/00:36
roaksoaxexport https_proxy=http://ip-of-maas:8000/00:36
roaksoaxboth commands00:36
sentinel-primei did that on the maas controlor00:36
roaksoaxsentinel-prime: ok so you have two options00:37
roaksoaxsentinel-prime: 1. configure the deployed machines system proxy00:37
roaksoax2. configure NAT in the MAAS server00:37
roaksoaxsentinel-prime: doing 1 is setting up http_proxy and https_proxy on the *deployeD* system00:38
roaksoaxdoing 2. is doing somethin like this: http://paste.ubuntu.com/p/xDXndWX7vF/00:38
roaksoaxsentinel-prime: what I do in my home lab, is setting up NAT in the MAAS server00:39
roaksoaxsentinel-prime: by doing this: http://paste.ubuntu.com/p/xDXndWX7vF/00:39
sentinel-primeif i do 2 will it auto configure any new machines added00:41
sentinel-primebecause it sounds like 1 has to be done for any new machines00:42
sentinel-prime?00:57
mupBug #1771711 opened: failed  smartctl-validate <MAAS:New> <https://launchpad.net/bugs/1771711>01:31
[Kid]does MAAS setup a password for the ubuntu user at all/01:55
[Kid]trying to access console if SSH keys are not available01:55
=== jhebden is now known as jhebden-afk
myrathello people i have a problem with creating keypair in openstack06:48
myrathelp me somebody please06:48
mupBug #1771777 opened: Node is stuck "exiting rescue mode" from failed deployment <MAAS:New> <https://launchpad.net/bugs/1771777>09:29
SiderisHi10:31
SiderisI have a problem with maas deployement10:31
Siderissomeone can help me10:31
mupBug #1771475 changed: maas cli making API calls on port 80 <MAAS:Won't Fix> <https://launchpad.net/bugs/1771475>13:54
mupBug #1682150 opened: [2.1] MAAS node memory detection problem : 0.0GiB <MAAS:New> <https://launchpad.net/bugs/1682150>13:57
klj1218wondering if I can get some help with a new maas deployment, using composable hardware (via virsh), and everytime I try to compose a new system it will fail commissioning20:56
klj1218running ubuntu 17.10 + maas 2.3.2, all updates20:57
klj1218what fails during commisioning is "00-maas-03-install-lldpd" and "99-maas-02-capture-lldp" (not suprising given the 1st failure)20:59
* klj1218 If I drill down on the "00-maas-03-install-lldpd" failure... it shows the following:20:59
klj1218"E: Unable to locate package lldpd"21:00
klj1218btw, all the other stages of commissioning pass (just the two stages fail)21:01
sentinel-primeroaksoax got to ask when is the best time to get your help21:45
mupBug #1771897 opened: PPC64 VMs run out of memory with 1024 MiB <MAAS:Triaged> <https://launchpad.net/bugs/1771897>22:37
mupBug #1771897 changed: [2.5] PPC64 VMs run out of memory with 1024 MiB <pods> <MAAS:Triaged> <https://launchpad.net/bugs/1771897>22:46
mupBug #1771897 opened: [2.5] PPC64 VMs run out of memory with 1024 MiB <pods> <MAAS:Triaged> <https://launchpad.net/bugs/1771897>22:49

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!