[00:18] sentinel-prime: here [00:18] o/ [00:18] sentinel-prime: yes, so since you are using NAT [00:18] sentinel-prime: the machines dont have access to the internet [00:18] sentinel-prime: so you need to do iptables to allow them to access the internet [00:18] sentinel-prime: or set http_proxy on the machines to use the proxy [00:19] http proxy needs to be set in the maas controlor right [00:20] if so that is set tto maas built in [00:20] on the setting page [00:21] sentinel-prime: right, but maas doesn't set http_proxy on the system. it only sets apt's proxy [00:21] so i have to set it to exturnal [00:21] or peer [00:22] sentinel-prime: no [00:22] sentinel-prime: the built-in proxy is fine [00:22] sentinel-prime: but when the machine is deployed [00:24] sentinel-prime: the deployed machine only gets apt proxy set, which allows apt to access the mirrors, but just for apt [00:24] sentinel-prime: if you want the system itself to have accecess [00:25] sentinel-prime: you can do: export http_proxy=http://ip-of-maas-server:8000/ [00:25] export http_proxy=http://ip-of-maas-server:8000/ [00:25] export https_proxy=http://ip-of-maas-server:8000/ [00:25] sentinel-prime: or you can try in port 3128 [00:29] thats the command right [00:35] ? [00:36] sentinel-prime: yes, in the installed system you can do: [00:36] export http_proxy=http://ip-of-maas:8000/ [00:36] export https_proxy=http://ip-of-maas:8000/ [00:36] both commands [00:36] i did that on the maas controlor [00:37] sentinel-prime: ok so you have two options [00:37] sentinel-prime: 1. configure the deployed machines system proxy [00:37] 2. configure NAT in the MAAS server [00:38] sentinel-prime: doing 1 is setting up http_proxy and https_proxy on the *deployeD* system [00:38] doing 2. is doing somethin like this: http://paste.ubuntu.com/p/xDXndWX7vF/ [00:39] sentinel-prime: what I do in my home lab, is setting up NAT in the MAAS server [00:39] sentinel-prime: by doing this: http://paste.ubuntu.com/p/xDXndWX7vF/ [00:41] if i do 2 will it auto configure any new machines added [00:42] because it sounds like 1 has to be done for any new machines [00:57] ? [01:31] Bug #1771711 opened: failed smartctl-validate [01:55] <[Kid]> does MAAS setup a password for the ubuntu user at all/ [01:55] <[Kid]> trying to access console if SSH keys are not available === jhebden is now known as jhebden-afk [06:48] hello people i have a problem with creating keypair in openstack [06:48] help me somebody please [09:29] Bug #1771777 opened: Node is stuck "exiting rescue mode" from failed deployment [10:31] Hi [10:31] I have a problem with maas deployement [10:31] someone can help me [13:54] Bug #1771475 changed: maas cli making API calls on port 80 [13:57] Bug #1682150 opened: [2.1] MAAS node memory detection problem : 0.0GiB [20:56] wondering 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 commissioning [20:57] running ubuntu 17.10 + maas 2.3.2, all updates [20:59] what 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: [21:00] "E: Unable to locate package lldpd" [21:01] btw, all the other stages of commissioning pass (just the two stages fail) [21:45] roaksoax got to ask when is the best time to get your help [22:37] Bug #1771897 opened: PPC64 VMs run out of memory with 1024 MiB [22:46] Bug #1771897 changed: [2.5] PPC64 VMs run out of memory with 1024 MiB [22:49] Bug #1771897 opened: [2.5] PPC64 VMs run out of memory with 1024 MiB