-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
3
-
False
-
-
False
-
None
-
Unset
-
None
-
Sources Sprint 47, Sources Sprint 48, Sources Sprint 49, Sources Sprint 50, Sources Sprint 51, Sources Sprint 52
We spotted an issue where the "unavailable sources monitor" wouldn't pick sources with an empty availability status. That might be one of the causes of the very recent issue we've been dealing with, regarding not being able to see the availability status checks for a particular source related to a satellite.
This might imply:
- Checking that the validators run on create/update of sources, applications and endpoints.
- Create a migration to update all the empty and null availability statuses to "unavailable".
- Create a NOT NULL migration for the column.
- Default empty or nil availability statuses to "in_progress", and update the monitor to treat them along with "unavailable" sources.
Lindani suggested[1] that we should avoid having NULLs and empty values on that column.
- is duplicated by
-
RHCLOUD-20298 Add testing for invalid availability sources
-
- Closed
-
- relates to
-
RHCLOUD-19817 Satellite not showing up as connected when registered with sources
-
- Closed
-
-
RHCLOUD-19949 Unavailable sources are not getting picked by the "unavailable" sources monitor
-
- Closed
-
-
RHCLOUD-20299 [Spike] Figure out how / why nil status' is being set
-
- Closed
-