CI/featureset010: validations aren't fatal
Bug #1737768 reported by
Emilien Macchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Medium
|
Gael Chamoulaud |
Bug Description
We're enabling tripleo-validations on featureset010: https:/
But the validations aren't fatal, since the nodes provided by nodepool don't have enough RAM.
In the future, we need to find a way to not make the validations fatal except for the RAM check. See comments in 525637.
If I understand correctly, the validations squad will manually verify the validation logs but the CI job won't fail if some validations are failing. It's technical debt now.
Changed in tripleo: | |
assignee: | nobody → Gael Chamoulaud (gael-chamoulaud) |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
milestone: | stein-3 → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
milestone: | train-2 → train-3 |
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
status: | Triaged → Incomplete |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
Changed in tripleo: | |
status: | Invalid → Won't Fix |
To post a comment you must log in.
Now handled by component pipeline.
Validations can be customized to provide values of parameters specific to their setting.