I can confirm the bug as well. Followed all the defaults from the wiki,
how-ever am using public IP's and not private IP's. Upon launch all
nodes got the same 'bad mirror archive'.
After editing the squid-deb-proxy acl the nodes were able to connect and
update
It would be great if the wiki could
I had the same problem and solved it adding my subnet address (e.g
200.100.3.0/24 ) in /etc/squid-deb-proxy/allowed-networks-src.acl and
restarting squid-deb-proxy. service squid-dev-proxy restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
If someone could confirm this I can file it as a bug.
** Changed in: ubuntu
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+question/198548
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
It is also worth mentioning that I followed the Ubuntu wiki step by step
and my node had internet access after booting via PXE. I did not specify
a proxy when setting up the MAAS server as it was not needed. It took a
long time to find this issue because I was able to setup a cloud in
virtual box o
Attached the hardware-summary log in case it's needed
** Attachment added: "hardware-summary"
https://bugs.launchpad.net/ubuntu/+bug/1005027/+attachment/3164924/+files/hardware-summary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "syslog"
https://bugs.launchpad.net/bugs/1005027/+attachment/3164922/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005027
Title:
MAAS does not add the correct
