VPN is blocked in ON/OFF state after running <force_update_check> via Inspector

[data-sync-user]

Important details:

• Not reproducing on MacOS M1 using the same steps;
• In logs there are multiple mentions about v. 2.12 - trying to be downloaded but not found-  are displayed.
• Reproducing with/without the “Staging Update Server” feature being enabled;

Version/build found in:

• 2.22.0 (2.202404031720);

Reproducible on:

• Windows 10;

Prerequisites:

• Have the Mozilla VPN client installed;
• Have an account with subscription for Mozilla VPN;
• Be logged on stage;
• Have the Staging Update Server feature enabled;

Steps to reproduce:

1. Turn On the VPN client;
2. Open the Inspector and run force_update_check 2.10;
3. Go to Settings - About us - Check for updated;
4. “Update now”;
5. Try to turn OFF the VPN;

Expected result:

• The VPN cannot be turned OFF.

Actual results:

• The update seems to work, but after an installer popup is displayed, nothing happens.

Notes:

• We are partially blocked in testing the root CA;

┆Issue is synchronized with this Jira Bug ┆Reporter: Valentina Virlics

[data-sync-user]

➤ Valentina Virlics commented:

This is currently still happening, even after Balrog stage update to 2.21, while on Window 10/11.

[data-sync-user]

➤ Valentina Virlics commented:

[Naomi] I spent a bit of time looking into VPN-6287 on Friday and I came to the conclusion that this is the behavior we get whenever an update is started but terminates abnormally for some reason. It's not just a root CA thing. For example, trying to install a 2.21 version ontop of a 2.22 version always results in this situation. The cause is that the TaskRelease job assumes that once the update is started the update will kill the client, which is true if and only if the update succeeds.

CC: Naomi Kirby

[data-sync-user]

➤ Valentina Virlics commented:

Based on Naomi’s findings, I’ll remove the [root CA] tag.

[data-sync-user]

➤ Valentina Virlics commented:

Verified this while on Windows 10/11, using Mozilla VPN 2.22.0 (2.202404181556) build.

Following the above steps, I still cannot turn ON/OFF the client after trying to force update it.

Attaching logs and video.

[^mozillavpn-2024-4-19_1.log]

!turn off.mp4|width=536,height=800,alt="turn off.mp4"!

Reopening.

[data-sync-user]

➤ Valentina Virlics commented:

Later update:

• seems like the client can be currently turned on/off on machines with Windows 10/11 that are not enrolled in CSV (Cognizant) - our work main stations, and don’t have all sort of security restrictions. (2.22.0 (2.202404181556))

  • on these testing devices the client could not be turned ON/OFF while using prev builds;

• the Mozilla VPN client on the machines that are enrolled in CSV still does NOT work.

Logs below.

[data-sync-user]

➤ Valentina Virlics commented:

As this is specific to some main stations that are enrolled in CSV (Cognizant), we can lower Priority and consider not entirely blocking QA. Santiago Andrigo Naomi Kirby

[data-sync-user]

➤ Santiago Andrigo commented:

Valentina Virlics Since this is a Cognizant specific environment issue, shouldn’t this ticket be cancelled in lieu for a ticket with the Cognizant team to change whatever is blocking this from working? Or, is there anything the VPN team can do?