incorrect-calculation-of-lp-limit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
New
|
Critical
|
Unassigned |
Bug Description
Incorrectly getting 'limit reached' error even though the number of languagepacks is less than the configured limit.
Below is an example:
vagrant@
ERROR: Resource limit exceeded. Reason: Number of languagepacks reached limit of '10'.
vagrant@
+------
| uuid | name | description | status | source_uri |
+------
| 07687df7-
| 19806103-
| 42bb3908-
| b030baa2-
| bfd7baec-
| dd14a066-
+------
Notice that there are only six (6) languagepacks but still we are getting the 'limit reached' error.
Solution:
This error is being thrown because we are not checking for 'artifact_
https:/
The image table is used to store both languagepack images and application images (DU images).
Changed in solum: | |
importance: | Undecided → Critical |
description: | updated |