That's a common symptom of a version conflict, either past or present. While attempting to pull in the registrations for those repository types, Python's packaging system is erroring out, saying that a package we depend on isn't available or a version range we require doesn't match what's installed.
There should be a "VersionConflict" error in the reviewboard.log or Apache error_log. If there's not, you can try running:
rb-site manage /path/to/sitedir registerscmtools
That will force a re-registration, and if there's a VersionConflict still occurring, you should see it then. Let me know what you see and I can assist in resolving it.
Christian