Starting meeting with "required" server type fails despite available server with correct type
Closed this issue · 0 comments
Ithanil commented
When using tagged servers and configuring a room with a tag + "required" option, starting the meeting fails with the corresponding error message (that no server with required type is available). This happens no matter if the server type is actually available or not.
I have no idea how this slipped through our final testing, but I blame rubocop, because the bug has been introduced in a rubocop-fixing commit: 67b802a ;-)
Mea culpa, I'm sorry!