Machine resources path set incorrectly in rackd when using snap

Bug #1922433 reported by Sami Haahtinen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alberto Donato

Bug Description

A recent change changed the way how snap path was being written to Nginx configuration.

https://git.launchpad.net/maas/commit/src/provisioningserver/rackdservices/http.py?id=54e9d295af3f1e5b444e4b10142b372d66abcdc5

With the new code, when running inside a snap environment, the machine resources path points to the root of the snap package instead of the correct directory.

This issue only affects the 3.0 branch as far as I can tell.

Related branches

Alberto Donato (ack)
Changed in maas:
importance: Undecided → High
assignee: nobody → Alberto Donato (ack)
milestone: none → 3.0-beta2
Alberto Donato (ack)
Changed in maas:
status: New → 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  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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