Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

previous_install.yaml logic breaks when rke2 is installed with an RPM and then later switched to TAR #193

Open
mddamato opened this issue Feb 29, 2024 · 2 comments
Open

previous_install.yaml logic breaks when rke2 is installed with an RPM and then later switched to TAR #193

mddamato opened this issue Feb 29, 2024 · 2 comments
Labels
triage Issues that need attention

Comments

@mddamato
Copy link
Contributor

No description provided.

@jcox10
Copy link
Contributor

jcox10 commented Apr 17, 2024 •
edited
Loading

It also breaks when you install RKE2 with the RPM, and then use Rancher to upgrade RKE2. You end up with the installed RPM being one version, but the running RKE2 version being different.

Perhaps what is needed is logic to install once with the RPM, then disable any further updates via the RPM repos. I have been doing this on my clusters by disabling the yum repo (enabled=0). All updates are then handled via Rancher.

@Daemonslayer2048 Daemonslayer2048 added the triage Issues that need attention label Jan 15, 2025
@aleiner
Copy link
Contributor

aleiner commented Jan 17, 2025

Switching between RPMs and Tarballs as the means to install RKE2 isn't something we want to support at the moment.

@jcox10, can you elaborate on what you said? DId you use rke2-ansible to build a downstream cluster and import it to Rancher?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage Issues that need attention
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mddamato @jcox10 @Daemonslayer2048 @aleiner