[MGNLTEST-77] Update VNC sidekick health-check log hook after Selenium dependency update Created: 06/Aug/20 Updated: 08/Sep/20 Resolved: 11/Aug/20 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Sprint: | TE 8 |
| Story Points: | 1 |
| Description |
|
With Selenium 3.7.1 VNC side-kick container would expect a log statement "Connected", with Selenium 3.141.59 - "start recording". Why exactly that happens - I do not know (would assume changes in selenium debug node images). |
| Comments |
| Comment by Aleksandr Pchelintcev [ 11/Aug/20 ] |
|
After all turned out the issue was due to the docker-compose setup not arranging networking properly: selenium workers were in a compose service network, while recorders were in a docker global network, not being able to communicate to each other. The described symptom was happening due to recorder never being able to connect. After the networking issues were resolved, the previous healthcheck patterns started to work again rendering this issue obsolete. |