Upgrade Linux OS and Posit Team — Alternative Path, Upgrade OS In-Place

flowchart LR
    A((0))
    B((1))
    C(("✔"))
    D((2))
    E(("#9829;"))
    F(("#9888;"))

    A------F
    A---B
    subgraph box[<b>Recommended Approach]
    B---C
    C---D
    D---E
    end
    A ~~~|"<a style="text-decoration:none" href="index.html">Overview</a>"|A
    B ~~~|"<a style="text-decoration:none" href="phase1-upgrade.html"><p style="background-color:none">Phase 1\n Install\n Upgraded\n Products</a>"|B
    C ~~~|"<a style="text-decoration:none" href="phase1-test.html"><p style="background-color:none">Test\n Phase 1</a>"|C
    D ~~~|"<a style="text-decoration:none" href="phase2-migrate.html"><p style="background-color:none">Phase 2\n Migrate\n Data</a>"|D
    E ~~~|"<a style="text-decoration:none" href="rollout.html"><p style="background-color:none">Rollout</a>"|E
    F ~~~|"<b>Upgrade\n OS in place</b>"|F
 

    click A href "index.html"
    click B href "phase1-upgrade.html"
    click C href "phase1-test.html"
    click D href "phase2-migrate.html"
    click E href "rollout.html"

    classDef activePage fill:#447099, stroke:#D1DBE5, color:#fff, padding:4px
    classDef inactivePage fill:#D1DBE5, stroke:#447099, color:#151515, padding:4px
    classDef activeDesc font-size:20px
    class A,B,C,D,E inactivePage
    class F activePage
    style box rx:40,ry:40

Applicability

An in-place upgrade of the Linux OS isn’t recommended, but consider if:

  • You are upgrading from a supported Posit product version to another supported product version. Refer to the list of Supported Pro product versions to determine applicability.

  • You have a staging server available to perform all work in an isolated environment. Without a staging environment, troubleshooting issues is challenging because the old environment isn’t available for reference.

  • If your OS vendor provides satisfactory support during the in-place OS upgrade.

  • You recognize that upgrading the OS in place presents the opportunity for OS system library incompatibility issues to arise, which are often intermittent, difficult to troubleshoot, and could arise months after the upgrade.

Important

If the Posit product(s) are out of support, use the recommended 2-phased approach instead to update your OS and product(s).

Overview

Don’t attempt this approach if the Posit product version / versions in production are no longer supported. Refer to the list of Supported Pro product versions to determine applicability.

For the new OS, upgrading in-place requires you to reinstall any software installed outside of the Linux package manager.

This includes, but isn’t limited to:

  • Reinstallation of the Posit product / products.
  • Reinstallation of all Python versions.
  • Reinstallation of all R versions.
  • Reinstallation of all Quarto versions.

Perform all work in a staging environment when conducting an OS upgrade in-place to minimize downtime and operational risk.

  1. Capture a backup, and duplicate the production environment in staging.

  2. Upgrade the OS in staging, then reinstall the Posit product / products at the same version as in production.

  3. Reinstall all versions of Python, all versions of R, and all versions of Quarto at the same version as production.

  4. Reinstall any other software installed outside of the Linux package manager (drivers, for example).

  5. Clear the existing Python and R package libraries on Workbench and content runtime caches on Connect because they’re incompatible with the new Linux OS. Remove the package libraries on Workbench and content runtime caches on Connect and rebuild as appropriate.

  6. Upgrade the Posit product / products per the applicable product documentation:

Back to top