Public bug reported:
Steps to reproduce:
1. Setup a MAAS server
2. Setup the MAAS IP on a public IP block
3. Setup maas-dhcp to hand out IPs on the subnet added in step 2
4. PXE boot a node
The node will fail to enlist complaining about a Bad Mirror Archive.
After booting the node in debug mode and inspecting the logs I noticed
that the node uses the MAAS server as a proxy to retrieve file from the
Ubuntu archives. Next I checked the squid-deb-proxy acl file and noticed
that the my MAAS subnet was not in there. I added the subnet and
restarted the proxy and my node was able to enlist and commission.
syslog and hardware logs from the node are attached.
** Affects: ubuntu
Importance: Undecided
Status: New
--
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 IP subnet to the squid-deb-proxy ACL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1005027/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
