upload options do not support local SSL urls nor self-signed certificates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sosreport (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
Bug Description
The current versions of sosreport (3.9 on Bionic and 4.0 on Focal) do not appear to support passing the --upload-url to a non-Canonical URL, for example a LAN-side host to collect those sosreports.
sudo sosreport --batch -o pci --upload --upload-url=https:/
This results in the error of:
Your sosreport has been generated and saved in:
/tmp/
Size 7.04KiB
Owner root
md5 3095adb8d50728e
Please send this file to your support representative.
Upload attempt failed: No upload destination provided by policy or by --upload-url
Additionally, when configuring a reproducer (nginx configured with SSL + PUT support), sosreport appears to ignore that endpoint, and fails with:
Upload attempt failed: No upload destination provided by policy or by --upload-url
Updating the `/usr/lib/
Upload attempt failed: HTTPSConnection
There does not appear to be a way to tell sosreport to ignore a self-signed certificate, or ignore verification of that certificate, even when it's correctly imported into /usr/local/
There is a temporary workaround, using curl to directly push that file to the nginx endpoint, using:
sudo curl -k -T sosreport-
But sosreport itself, does not appear to support custom URLs, nor self-signed certificates.
Changed in sosreport (Ubuntu): | |
status: | Confirmed → Won't Fix |
status: | Won't Fix → Incomplete |
This appears to be fixed in upstream github master branch. There are varying levels of issues with DAV on nginx accepting the PUT over SSL from sosreport, but that's unrelated to sosreport itself.