Document URL: Section Number and Name: Describe the issue: When specifying the --uploadproxy-url parameter in virtctl upload, if the user adds a trailing slash to the value the operation will fail. We should document this with a note to the user reminding them to not use a trailing slash. Suggestions for improvement: Add note as described above Additional information:
See https://bugzilla.redhat.com/show_bug.cgi?id=1660888 for the original bug.
Hey Adam, this is the way we have virtctl image-upload documented now: $ virtctl image-upload --uploadproxy-url=https://$(oc get route cdi-uploadproxy-route -o=jsonpath='{.status.ingress[0].host}') --pvc-name=upload-fedora-pvc --pvc-size=10Gi --image-path=/images/fedora28.qcow2 Do you expect that users will replace the --uploadproxy-url parameter value with a different URL? If not, I don't see how a user would run across the trailing slash issue. If you expect that some of the time, users will add their own URL, then I can definitely add a Known Issue to the Release Notes (or a note in the procedure itself). Just want to make sure before doing so.
In some situations a user may enter their own URL (hopefully rarely) so I think a Known Issue would still be appropriate.
I wrote something up: http://file.bos.redhat.com/pousley/021219/knownissues/cnv_release_notes/cnv_release_notes.html Let me know what you think - thanks!
Looks great!
Thanks, Adam! Moving to ON_QA. QE: note that the preview link in comment #4 doesn't include all the Release Notes (it's from Feb 12). Each BZ will likely have a different link.
Looks good, thanks.
The requested changes were published in the CNV 1.4 Release Notes: https://docs.openshift.com/container-platform/3.11/cnv_release_notes/cnv_release_notes.html#RN_known_issues