FR: Updating clients remotely #6907

LunchBoxC · 2023-01-07T05:31:35Z

What are you trying to do?

I'm using Tailscale to connect to clients remotely using remote desktop software.

When an update for the Tailscale software exists I must manually visit these clients to update them as installing the new package over remote desktop disconnects the client and it can't be reconnected to until the setup process is fully completed and the installer exits.

How should we solve this?

It could be solved by the following:

Allow clients to be updates from the admin console

OR

allow for automatic updating of the clients

OR

Change the installer so that it briefly disconnects to do the install and then reconnects all clients before the installer exits as there is no way to click on "Finish" when tailscale is now in the disconnected state and preventing the remote desktop software from making a connection.

What is the impact of not solving this?

Waste of resources driving to clients to update their Tailscale application version.

It also means that clients run on outdated versions for longer.

Anything else?

It would also be great if we could pre-configure the installer and send it out with all options like "run unattended" and with the credentials already installed so the installer would make the connection after the install.

This would make sending it to someone to install a snap, rather than needing to configure it thereafter with novice users that don't understand what to click on.

Again to aid remote connection environments.

bradfitz · 2023-01-09T20:15:01Z

Much of this is currently underway.

Add `tailscale version --json` JSON output mode. This will be used later for a double-opt-in (per node consent like Tailscale SSH + control config) to let admins do remote upgrades via `tailscale update` via a c2n call, which would then need to verify the cmd/tailscale found on disk for running tailscale update corresponds to the running tailscaled, refusing if anything looks amiss. Plus JSON output modes are just nice to have, rather than parsing unstable/fragile/obscure text formats. Updates #6995 Updates #6907 Change-Id: I7821ab7fbea4612f4b9b7bdc1be1ad1095aca71b Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

Add `tailscale version --json` JSON output mode. This will be used later for a double-opt-in (per node consent like Tailscale SSH + control config) to let admins do remote upgrades via `tailscale update` via a c2n call, which would then need to verify the cmd/tailscale found on disk for running tailscale update corresponds to the running tailscaled, refusing if anything looks amiss. Plus JSON output modes are just nice to have, rather than parsing unstable/fragile/obscure text formats. Updates tailscale#6995 Updates tailscale#6907 Change-Id: I7821ab7fbea4612f4b9b7bdc1be1ad1095aca71b Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

…pport Updates tailscale#6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

SilverBut · 2023-03-03T22:24:24Z

Great feature I'm waiting for.

Also, it would be great if the remote updating will failsafe, so that if a server is lockdown (for example, only allowing login from other devices in the tailnet) and client update failed, the old client process can still working.

DentonGentry · 2023-06-04T01:25:27Z

The initial step in this is tailscale update

The flag is hidden and a noop for now. Adding propagation to tailscaled and persistence only. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

The flag is hidden and a noop for now. Adding propagation to tailscaled and persistence only. The prefs field is wrapped in a struct to allow for future expansion (like update schedule). Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

An optional (for now) request body for POST /update messages to carry the suggested version. This removes the need from clients to figure out what the latest available version is. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

The flags are hidden for now. Adding propagation to tailscaled and persistence only. The prefs field is wrapped in a struct to allow for future expansion (like update schedule). Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

Cache the last `ClientVersion` value that was received from coordination server and pass it in the localapi `/status` response. When running `tailscale status`, print a message if `RunningAsLatest` is `false`. Updates #6907

Cache the last `ClientVersion` value that was received from coordination server and pass it in the localapi `/status` response. When running `tailscale status`, print a message if `RunningAsLatest` is `false`. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

The flags are hidden for now. Adding propagation to tailscaled and persistence only. The prefs field is wrapped in a struct to allow for future expansion (like update schedule). Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

Cache the last `ClientVersion` value that was received from coordination server and pass it in the localapi `/status` response. When running `tailscale status`, print a message if `RunningAsLatest` is `false`. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

The flags are hidden for now. Adding propagation to tailscaled and persistence only. The prefs field is wrapped in a struct to allow for future expansion (like update schedule). Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

Cache the last `ClientVersion` value that was received from coordination server and pass it in the localapi `/status` response. When running `tailscale status`, print a message if `RunningAsLatest` is `false`. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

Log some progress info to make updates more debuggable. Also, track whether an active update is already started and return an error if a concurrent update is attempted. Some planned future PRs: * add JSON output to `tailscale update` * use JSON output from `tailscale update` to provide a more detailed status of in-progress update (stage, download progress, etc) Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

…#9205) Cache the last `ClientVersion` value that was received from coordination server and pass it in the localapi `/status` response. When running `tailscale status`, print a message if `RunningAsLatest` is `false`. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

noncombatant · 2023-12-07T00:56:33Z

News on this bug: Proposed solution (2) is done; see the Beta release of auto-updates if you haven't already.

Proposed solution (1) is in development now. We cannot provide a guarantee of when it will land, but it is a key part of our plan for taking auto-updates out of Beta, and we are working on it now.

LunchBoxC · 2023-12-07T01:55:32Z

Thank you!

The flags are hidden for now. Adding propagation to tailscaled and persistence only. The prefs field is wrapped in a struct to allow for future expansion (like update schedule). Updates tailscale#6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com> Signed-off-by: Alex Paguis <alex@windscribe.com>

Log some progress info to make updates more debuggable. Also, track whether an active update is already started and return an error if a concurrent update is attempted. Some planned future PRs: * add JSON output to `tailscale update` * use JSON output from `tailscale update` to provide a more detailed status of in-progress update (stage, download progress, etc) Updates tailscale#6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com> Signed-off-by: Alex Paguis <alex@windscribe.com>

…tailscale#9205) Cache the last `ClientVersion` value that was received from coordination server and pass it in the localapi `/status` response. When running `tailscale status`, print a message if `RunningAsLatest` is `false`. Updates tailscale#6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com> Signed-off-by: Alex Paguis <alex@windscribe.com>

LunchBoxC added fr Feature request needs-triage labels Jan 7, 2023

bradfitz removed the needs-triage label Jan 9, 2023

bradfitz mentioned this issue Jan 21, 2023

version, cmd/tailscale: add version.Meta, tailscale version --json #7029

Merged

bradfitz added a commit that referenced this issue Jan 21, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update su…

8c82b12

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

bradfitz mentioned this issue Jan 21, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update support #7031

Merged

bradfitz added a commit that referenced this issue Jan 23, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update su…

dcb6744

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

bradfitz added a commit that referenced this issue Jan 23, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update su…

7eda973

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

bradfitz added a commit that referenced this issue Jan 23, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update su…

d1945dd

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

bradfitz added a commit that referenced this issue Jan 23, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update su…

85f9207

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

bradfitz added a commit that referenced this issue Jan 23, 2023

envknob, hostinfo, ipn/ipnlocal: add start of opt-in remote update su…

b6aa1c1

…pport Updates #6907 Change-Id: I85db4f6f831dd5ff7a9ef4bfa25902607e0c1558 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>

awly assigned noncombatant and awly Aug 11, 2023

awly added a commit that referenced this issue Aug 11, 2023

cmd/tailscale,ipn: add auto-update flag and pref

34f9ad8

The flag is hidden and a noop for now. Adding propagation to tailscaled and persistence only. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

awly mentioned this issue Aug 11, 2023

cmd/tailscale,ipn: add auto-update flags and prefs #8861

Merged

awly added a commit that referenced this issue Aug 11, 2023

cmd/tailscale,ipn: add auto-update flag and pref

19dcf91

The flag is hidden and a noop for now. Adding propagation to tailscaled and persistence only. Updates #6907 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>

awly mentioned this issue Sep 1, 2023

cmd/tailscale/cli,ipn: mention available update in "tailscale status" #9205

Merged

awly mentioned this issue Sep 7, 2023

ipn/ipnlocal: add logging and locking to c2n /update #9290

Merged

awly closed this as completed Jan 24, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FR: Updating clients remotely #6907

FR: Updating clients remotely #6907

LunchBoxC commented Jan 7, 2023

bradfitz commented Jan 9, 2023

SilverBut commented Mar 3, 2023 •

edited by DentonGentry

Loading

DentonGentry commented Jun 4, 2023

noncombatant commented Dec 7, 2023 •

edited

Loading

LunchBoxC commented Dec 7, 2023

FR: Updating clients remotely #6907

FR: Updating clients remotely #6907

Comments

LunchBoxC commented Jan 7, 2023

What are you trying to do?

How should we solve this?

What is the impact of not solving this?

Anything else?

bradfitz commented Jan 9, 2023

SilverBut commented Mar 3, 2023 • edited by DentonGentry Loading

DentonGentry commented Jun 4, 2023

noncombatant commented Dec 7, 2023 • edited Loading

LunchBoxC commented Dec 7, 2023

SilverBut commented Mar 3, 2023 •

edited by DentonGentry

Loading

noncombatant commented Dec 7, 2023 •

edited

Loading