MAAS 2.3 does not revert system proxy back to original state when MAAS is removed

Bug #1749281 reported by David A. Desrosiers on 2018-02-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Andres Rodriguez

Bug Description

When MAAS is installed on a host that has an existing proxy configured and running with Squid, it disables this instance of Squid, replacing it with its own, and points /usr/sbin/squid to the MAAS proxy configuration in /var/lib/maas/maas-proxy.conf.

When removing MAAS (for any reason, rebuild, teardown), MAAS will remove its own proxy configuration, but does not return the system squid back to a running state as it found it when it was installed.

If the system is configured to look for the system proxy on :3128, such as http{,s}_proxy environment variables in /etc/environment, Acquire::http::Proxy in /etc/apt/apt.conf or elsewhere, shutting down or removing MAAS will leave the system in a degraded/broken state.

Ideally, MAAS could run its own proxy process on a separate port, negating the need to clobber the system configuration and ports, but there may be other concerns preventing that configuration from being supported.

This bug is to track MAAS storing of some level of system/host state, so it can return the system to that state when the MAAS is removed from the system.

Related branches

summary: - MAAS 2.3 does not revert system Squid back to original state when
- removed
+ MAAS 2.3 does not revert system proxy back to original state when MAAS
+ is removed
description: updated
Changed in maas:
milestone: none → 2.4.x
assignee: nobody → Andres Rodriguez (andreserl)
importance: Undecided → Medium
status: New → Triaged
Changed in maas:
milestone: 2.4.x → 2.4.0alpha2
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers