Project

General

Profile

Bug #50236

Update RancherOS to version 1.4.1

Added by Disk Didler almost 2 years ago. Updated over 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
Marcelo Araujo
Category:
OS
Target version:
Seen in:
Severity:
High
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Hi all,

RancherOS has been updated at this location.
https://github.com/rancher/os/releases

I'm not technically savvy enough, but is there a long term solution to updating the backend RancherOS build for users? I suspect once 11.2 is rolled out, with docker support? People are going to want this.

Is there a script which could clone a new RancherOS with the same VM settings (except filename obviously) then migrate all data across into the new VM?

I'm still learning docker, I know it supports an export feature which is apparently very powerful. Perhaps docker itself could migrate from one VM to another easily for the end users?
(Yes, this would temporarily require twice the disk space, memory, CPU etc)

Ultimately people have complained of the inability to update the dockerVM on the forums. Is there anything that can be done at all by you clever folk or is this just something end users will need to work around manually?

Either way, 1.4.1 is out, so the download script for a new DockerVM instance in the UI, should pull that.

Thanks again for all the help / hard work.


Related issues

Copied to FreeNAS - Bug #51102: Determine upgrade design for RancherOSClosed

Associated revisions

Revision 96da0636 (diff)
Added by Marcelo Araujo over 1 year ago

- Update RancherOS to version 1.4.1. Ticket: #50236

Revision feaffe89 (diff)
Added by Marcelo Araujo over 1 year ago

- Update RancherOS to version 1.4.1. (#1886) Ticket: #50236

Revision 26016ab7 (diff)
Added by Marcelo Araujo over 1 year ago

- Update RancherOS to version 1.4.1. (#1886) Ticket: #50236

History

#1 Updated by Dru Lavigne almost 2 years ago

  • Assignee changed from Release Council to Alexander Motin

#2 Updated by Alexander Motin almost 2 years ago

  • Assignee changed from Alexander Motin to Marcelo Araujo

#3 Updated by Marcelo Araujo almost 2 years ago

  • Status changed from Unscreened to In Progress
  • Severity changed from New to High

#4 Updated by Disk Didler over 1 year ago

I have just been made aware of the YAML file which people configure in order to map the dockers back to their real pool of data via CIFS.

This may need to be considered if a plan is put in place for upgrading or replace upgrading the VM.

Thanks.

#5 Updated by Bug Clerk over 1 year ago

  • Status changed from In Progress to Ready for Testing

#6 Updated by Bug Clerk over 1 year ago

  • Target version changed from Backlog to 11.3

#7 Updated by Dru Lavigne over 1 year ago

  • Subject changed from RancherOS has again updated a final build, 1.4.1 - solution going forward? to Update RancherOS to version 1.4.1
  • Status changed from Ready for Testing to In Progress

#8 Updated by Dru Lavigne over 1 year ago

  • Target version changed from 11.3 to 11.2-RC1

#10 Updated by Bug Clerk over 1 year ago

  • Status changed from In Progress to Ready for Testing

#11 Updated by Disk Didler over 1 year ago

Any thoughts on my comments about long term solutions to upgrades?
(I am right or wrong about the inability to upgrade easily?)

What does Kris think?

#12 Updated by Bonnie Follweiler over 1 year ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Test Passed in
Rancher OS is on v1.4.1

#13 Updated by Marcelo Araujo over 1 year ago

  • Target version changed from 11.2-RC1 to Backlog

Disk Didler wrote:

I have just been made aware of the YAML file which people configure in order to map the dockers back to their real pool of data via CIFS.

This may need to be considered if a plan is put in place for upgrading or replace upgrading the VM.

Thanks.

Thanks to point it out!
Nowadays I do most of things manually to create a RancherOS image for bhyve. I will research how I can automate this process.

But meanwhile

Disk Didler wrote:

Any thoughts on my comments about long term solutions to upgrades?
(I am right or wrong about the inability to upgrade easily?)

What does Kris think?

You are right about the inability to upgrade it easily and it is something that bothers me a lot as I don't yet have a long term solution.

The main issue right now is that I do need to know the Linux kernel version as well as initrd version to be able to generate the grub config file and be able to boot the VM.

I'm investigating a different approach to let users always have the latest RancherOS version or even multiples different RancherOS versions in their setup.

However right now I still don't know what would be the right approach to solve this issue. Sorry for the inconvenience.

Best,

#14 Updated by Dru Lavigne over 1 year ago

  • Target version changed from Backlog to 11.2-RC1

#15 Updated by Dru Lavigne over 1 year ago

  • Copied to Bug #51102: Determine upgrade design for RancherOS added

#16 Updated by Dru Lavigne over 1 year ago

  • Status changed from Passed Testing to Done
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

Also available in: Atom PDF