[2.2] Adding custom repositories does not validate missing key
Bug #1665649 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
High
|
Unassigned | ||
Bug Description
When adding a custom repository, I avoided adding a GPG key. The custom repository was added successfully.
That said, the fact that there was no GPG key could have been a problem, provided it could have deployed.
MAAS should either:
1. prevent adding a custom repo without a GPG key
2. Warn the user about it adding a custom repo without a GPG key
====
After more investigation, we allow not adding a key, so it should probably do (2)
| Changed in maas: | |
| milestone: | none → 2.2.0 |
| importance: | Undecided → High |
| status: | New → Triaged |
| tags: | added: error-surface |
| description: | updated |
| Changed in maas: | |
| milestone: | 2.2.0 → 2.2.x |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Hi!
**This is an automated message**
We believe this is may no longer be an issue in the latest MAAS release. Due to the original date of the bug report, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.
Thanks