Hermes: username not assigned when use_ssl: True causes an error

[d-ylee]

Description

When configuring Hermes Daemon to use_ssl: True, Hermes has an error saying, local variable 'username' referenced before assignment

Steps to reproduce

1. Set messaging-hermes.use_ssl to True
2. Start the Daemon

Rucio Version

Daemons: 32.4.0

Additional Information

• Operating System: OKD Cluster/Kubernetes
• Bug is server side (in hermes daemon)
• ActiveMQ/RabbitMQ is the broker with STOMP plugin

After looking through the hermes daemon code, it looks like in the function setup_activemq, the username variable is only assigned when use_ssl is False:

rucio/lib/rucio/daemons/hermes/hermes.py

Line 190 in d1c0fae

return conns, destination, username, password, use_ssl

The only instance of username being assigned is here:

rucio/lib/rucio/daemons/hermes/hermes.py

Lines 152 to 155 in d1c0fae

	if not use_ssl:
	username = config_get("messaging-hermes", "username")
	password = config_get("messaging-hermes", "password")
	port = config_get_int("messaging-hermes", "nonssl_port")

This doesn't happen when use_ssl is True

[d-ylee]

One additional item: I think the same thing might happen with the password variable, since it is only assigned in the if not use_ssl statement.