Description of problem: Using '&' in MAIL_PASSWORD, give same failure, as if it was empty. When using the following settings in notifier.conf: MAIL_USER=istein, MAIL_ENABLE_SSL=true, MAIL_PASSWORD=& restartting notifier service fail on: Error: $MAIL_PASSWORD is not defined for SSL MAIL, please check for this in configuration file /etc/ovirt-engine/notifier/notifier.conf Version-Release number of selected component (if applicable): SI24.5 How reproducible: always Expected results: Have the '&' a valid charachter for MAIL_PASSWORD.
Ilanit, does this happen for any password containing this character? in any length? If it only happens if password is a single & character I would close as not fix, this password hardly if ever be found in a real life use case. Not worth the fix.
(In reply to comment #1) > If it only happens if password is a single & character I would close as not > fix, this password hardly if ever be found in a real life use case. Not > worth the fix. We were specifically asked in the past to support chars such as !@#$%^&*() We had bugs from customers where they were not supported.
This happen for any password containing this character. At any length.
(In reply to comment #2) > (In reply to comment #1) > > If it only happens if password is a single & character I would close as not > > fix, this password hardly if ever be found in a real life use case. Not > > worth the fix. > > We were specifically asked in the past to support chars such as !@#$%^&*() > We had bugs from customers where they were not supported. Agree, no problem with that, I was only wandering if it's just an issue with a password with length of one character. At any length as mentioned in comment #3 then it's a bug that needs fixing.
Verified on sf-8
3.2 has been released