py3: 404 when fetching script attachment

Bug #1718748 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
Medium
Simon Poirier

Bug Description

For some reason, after I upgrade a working artful client registered machine, which was using landscape-client 16.04 from the archive and python2, to the ppa:landscape/trunk version that is using py3, script attachments stop working.

I send a dummy script to the machine via landscape and a dummy attachment. The py2 client fetches it from the server via GET as usual:
Sep 21 17:58:19 message-server-1 INFO 127.0.0.1 - - [21/Sep/2017:17:58:19 +0000] "GET /attachment/1 HTTP/1.1" 404 - "-" "landscape-client/17.04-0ubuntu0~ubuntu17.10.1"

And the script succeeds.

I then upgrade landscape-client to 17.04+bzr1002~bzr1040-0ubuntu0~ubuntu17.10.1 and create the same script activity again. This time the client gets a 404 when fetching the same thing:
Sep 21 17:58:19 message-server-1 INFO 127.0.0.1 - - [21/Sep/2017:17:58:19 +0000] "GET /attachment/1 HTTP/1.1" 404 - "-" "landscape-client/17.04-0ubuntu0~ubuntu17.10.1"

An entirely new script fails the same way:
Sep 21 18:08:58 message-server-1 INFO 127.0.0.1 - - [21/Sep/2017:18:08:58 +0000] "GET /attachment/4 HTTP/1.1" 404 - "-" "landscape-client/17.04-0ubuntu0~ubuntu17.10.1"

NOTE: this also happens on a fresh new py3 client, not just in an upgrade.

description: updated
Changed in landscape-client:
milestone: none → 18.01
Simon Poirier (simpoir)
Changed in landscape-client:
status: New → Confirmed
status: Confirmed → Triaged
Revision history for this message
Simon Poirier (simpoir) wrote :
Changed in landscape-client:
status: Triaged → In Progress
assignee: nobody → Simon Poirier (simpoir)
Changed in landscape-client:
importance: High → Medium
Simon Poirier (simpoir)
Changed in landscape-client:
status: In Progress → Fix Committed
Changed in landscape-client:
status: Fix Committed → Fix Released
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.