-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
Unset
-
No
-
-
-
Platform A&M Sprint 71
Permissions during seeding are not being populated as seed process was interrupted by issue caused by using Kafka for notification service.
Suggested solution to restructuralize role(permission) seeds:
send notification off after the role and permissions are setWill be completed in another ticket in the epic- wrap related database operations in a transaction so if it fails, we don't end up with bad data
gracefully handle kafka exceptions and log/alert when we do, to allow seeds to workWill be completed in another ticket in the epic
There is discussion about issue:
There is https://issues.redhat.com/browse/RHCLOUD-23137 where issue was solved by workaround.