1786307 - Gecko interactive tasks are unable to connect (missing shell prompt)

Status: RESOLVED FIXED

(Release Engineering :: Firefox-CI Administration, defect, P3)

Description

[Andrew Halberstadt [:ahal]]

STR:

1. Find a test or lint task on try in Treeherder
2. From three dot menu bottom left, select "Create Interactive Task"
3. Wait for the create-interac action task to complete
4. Go to it's task details, click on the dependent task.
5. Append /connect to the URL
6. Click the shell option

Expected:
You are now in an interactive shell.

Actual:
No shell prompt is displayed. Shell cursor is red and stuck in top left. No text can be entered. This is consistent with what happens when the firewall blocks connecting to L3 tasks.

My theory is that this regressed when we switched test tasks over to GCP. Maybe we need to update the firewall rules.

Comment 1

[Andrew Halberstadt [:ahal]]

I did test out an interactive task in the application-services repo, and could connect successfully. So this at least isn't a firefox-ci wide issue. My hunch is GCP, but I haven't tried connecting to any AWS pools to verify.

Comment 2

[Michelle Goossens [:masterwayz]]

Workaround:

1. Start the interactive task shell.
2. Press F12 to open the browser console.
3. Go to the console tab.
4. Open the wss:// link in a browser tab of which it states that it is failing due to an untrusted cert, but make it https://
5. Trust the certificate
6. Refresh the page with the shell.

Comment 3

[Andrew Halberstadt [:ahal]]

Just to summarize what happened here, the livelog cert baked into the GCP image is outdated and the interactive feature apparently uses the same certificate. So this did regress when Michelle and I migrated tasks over to GCP. Bug 1785152 tracks updating the certificate in the GCP image, so when that is fixed, interactive tasks should magically work again. In the meantime, the workaround from comment 2 should be "good enough".

I'll leave this bug open (even though no action will be taken here) in case others happen to come looking for an existing bug.

Comment 4

[Michelle Goossens [:masterwayz]]

This should be fixed now.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

I've tried to run a Mn job on a Linux machine and I can indeed get access to the shell again. \o/

Thanks a lot for fixing that Michelle!