squid-deb-proxy is not started when installing MaaS with 13.10 server CD
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Undecided
|
Unassigned | ||
| maas (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
| Saucy |
Invalid
|
Undecided
|
Unassigned | ||
| squid-deb-proxy (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Precise |
Won't Fix
|
High
|
Unassigned | ||
| Saucy |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
When installing a MaaS server from the Saucy server install CD, the squid-apt-proxy service is not started by default, which results in the provisionning of nodes to fail.
Steps to reproduce:
(boilerplate)
1. Install a MaaS server using the Ubuntu Server 13.10 server media (Choose "Multiple server install with MaaS" at the CD boot prompt and follow the installer).
2. login to your newly created system
3. run "sudo maas createsuperuser", run "sudo maas-import-
4. setup your maas server from the UI (DHCP, DNS etc...)
5. PXE boot a node. The discovery phase succeeds, the node is listed in the nodes list as enlisted.
(actual bug)
6. mark the node for provisionning in the UI
7. (if needed) boot the node
What is happening:
The provisionning fails because the nodes are configured to use the maas server as an apt proxy on port 8000 and running "sudo service squi-deb-proxy status" confirms it is not running.
What should be happening:
Installing the maas server from the server install CD should start the squid-deb-proxy service at some point of the installation process, in order to install a functional maas system.
Workaround:
Manually running the deb proxy with "sudo service squid-deb-proxy start" makes the provisonning step succeed.
At the very least, the workaround should appear in http://
Related branches
- squid-deb-proxy-developers: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifiedinit-common.sh (+1/-1)
| tags: | added: landscape |
| summary: |
- squid-deb-proxy is not started when installing MaaS with server CD + squid-deb-proxy is not started when installing MaaS with 13.10 server CD |
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in maas: | |
| status: | New → Invalid |
| Robert Ayres (robert-ayres) wrote | #2 |
| Robert Ayres (robert-ayres) wrote | #3 |
| Chris Glass (tribaal) wrote | #4 |
| Robert Ayres (robert-ayres) wrote | #5 |
| Robert Ayres (robert-ayres) wrote | #6 |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #7 |
| tags: | added: patch |
| Serge Hallyn (serge-hallyn) wrote | #8 |
| Serge Hallyn (serge-hallyn) wrote | #9 |
| Changed in squid-deb-proxy (Ubuntu): | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Chris Glass (tribaal) wrote | #11 |
| Changed in squid-deb-proxy (Ubuntu Saucy): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in maas (Ubuntu Saucy): | |
| status: | New → Invalid |
| Changed in maas (Ubuntu): | |
| status: | New → Invalid |
| James Page (james-page) wrote | #12 |
| Changed in squid-deb-proxy (Ubuntu Precise): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Launchpad Janitor (janitor) wrote | #13 |
| Changed in squid-deb-proxy (Ubuntu): | |
| status: | Triaged → Fix Released |
| Rolf Leggewie (r0lf) wrote | #14 |
| Changed in squid-deb-proxy (Ubuntu Saucy): | |
| status: | Triaged → Won't Fix |
| Steve Langasek (vorlon) wrote | #15 |
| Changed in squid-deb-proxy (Ubuntu Precise): | |
| status: | Triaged → Won't Fix |
| Changed in maas (Ubuntu Precise): | |
| status: | New → Won't Fix |
Re-targeting as this is a packaging bug. Out of interest, are there any errors in its log?