maas 1.7 upgrade: document potential need for maas-proxy.conf manual setup migration

Bug #1394306 reported by JuanJo Ciarlante
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
High
Unassigned
maas (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

MaaS 1.7 new specific maas-proxy service doesn't migrate user
customization from 1.5 squid-deb-proxy, requiring the user
to manually do it - this is relevant e.g. for an installation
previously setup to use an intermediate proxy.

Suggest either augmenting 1.7 release notes 'maas-proxy'
section, and/or noticing this at maas-proxy dpkg install time.

JuanJo Ciarlante (jjo)
description: updated
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Packaging bug.

Changed in maas:
status: New → Triaged
importance: Undecided → High
Changed in maas:
status: Triaged → Won't Fix
Changed in maas (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.