action #27901
closed
[qam] test fails in evolution_smoke - imap aol not responding
Added by pcervinka over 6 years ago.
Updated over 6 years ago.
Category:
Enhancement to existing tests
Description
Observation¶
openQA test in scenario sle-12-SP3-Desktop-DVD-Updates-x86_64-qam-regression-message@64bit fails in
evolution_smoke
Reproducible¶
Fails since (at least) Build 20171109-1
Expected result¶
Last good: 20171108-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Status changed from New to In Progress
There was definitely change on AOL side. I manually checked nooops_test3@aim.com mailbox, and there is note about change, which will begin after 7.11. Test stopped working 9.11.
Hi nooops_test3,
AOL is committed to protecting the privacy and security of our customers. This is why we're writing to inform you that your current third party email application is not using the latest, secure mail connection settings. In order to continue sending and receiving AOL Mail via your application, you must update your connection settings by November 7, 2017.
Please visit our help site for instructions on how to update your settings.
To avoid having to make changes in the future and to ensure you are using up-to-date security settings, we recommend that you download the AOL app or use mail.aol.com to send and receive your AOL Mail.
Very cool investigation :) You could check for that error condition within the test and apply the settings "manually" with a "record_soft_failure"
I'm just thinking to switch it from AOL to Gmail to avoid this situation. It will use same autodiscovery, just for different domain. Or I can softfail AOL and add Gmail to have more smoke. What do you think?
Hm, I don't know which one will be more stable so at best I would in the test try one and if it fails try the second, if both fail, then fail the test.
Upstream just fixed their bug and evolution_smoke works as before: http://10.100.12.105/tests/627#step/evolution_smoke/12
But I don't want throw away fix which I did, because it is failover for not responding AOL anyway.
I will just change soft-failure message to contain network error.
Or should I cancel my pull/merge requests?
keep it open. I will comment there.
- Category changed from Bugs in existing tests to Enhancement to existing tests
Upstream bug was solved, the discussion is about enhancement for failover in case of unreachable server.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF