Launchpad silently fails when trying to link to a non-existent CVE
Bug #273536 reported by
Jamie Strandboge
This bug report is a duplicate of:
Bug #66877: Unknown CVE error message for $bug/+linkcve form is not displayed.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When using 'Link to CVE', if the CVE doesn't exist in Launchpad, the CVE is not added and no feedback is given to the user as to why the action was not performed. As a workaround, the CVE may be added to a comment which seems to work fairly well.
Revision history for this message
| Stefan Lesicnik (stefanlsd) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Confirmed |
To post a comment you must log in.
I can confirm this behaviour. Adding the CVE to the comment does link it, however as seen in an example here - https:/