After spending a while with ilkermeroc to try and verify the bug, we actually discovered that the subsequent parsing done by Launchpad of the apport payload is *expecting* LF endings, and thus breaks down if using CRLF.
So, to summarize: apport in -updates fails against qastaging when trying to PUT the blob because the new multipart expects CRLF line endings, but succeeds against production since multipart was reverted. apport in -proposed succeeds against qastaging on the PUT since it now uses CRLF endings, but the postprocessing afterwards fails *because* of CRLFs, **and** it's the same scenario against production (successful PUT, fail at postprocessing). There are several potential fixes for the problem on the LP side, but clearly this SRU should be reverted until it's sorted on the Launchpad side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2096327 Title: apport cannot upload blobs to launchpad - X-Launchpad-Blob-Token missing from http response -> "assert ticket" To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2096327/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
