Creating an OCI Project without having oci.project.create.enabled causes an OOPS
Bug #1885700 reported by
Kristian Glass
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
If I attempt to create an OCI Project without having oci.project.
OOPS-1eb2c0fde902d58a6bc15f90cf97acec is an example of one on staging, but something in the OOPS pipeline seems broken as it's not turning up at oops.canonical.com
If #1885698 is unfixed then this bug seems high-ish priority as people will potentially encounter it easily and it's much more likely to result in erroneous OOPSen and/or support load
If #1885698 is already fixed then this bug seems lower priority as people would need to manually URL-fiddle to be able to attempt it
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: oci ui |
To post a comment you must log in.
