Project

General

Profile

Bug #28230

Don't recreate grub.cfg everytime a Docker VM is launched

Added by Tim Lee over 1 year ago. Updated over 1 year ago.

Status:
Done
Priority:
Blocks Until Resolved
Assignee:
Marcelo Araujo
Category:
Middleware
Target version:
Seen in:
Severity:
High
Reason for Closing:
Reason for Blocked:
Need additional information
Needs QA:
Yes
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I updated from 11-MASTER-201712281257 to 11.1-U1 and unfortunately, the Rancher VM that did work no longer seems to boot. The VM is shown as running in the UI but the vm's console is blank and is also unreachable by SSH.

Associated revisions

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

- Don't recreate grub.cfg everytime a docker vm is launched.
Usually when we update RancherOS image it comes with a new kernel
version as well as a new initrd; so legacy images must be run with
previous settings we must keep them.

Ticket: #28230

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

- Don't recreate grub.cfg everytime a docker vm is launched.
Usually when we update RancherOS image it comes with a new kernel
version as well as a new initrd; so legacy images must be run with
previous settings we must keep them.

Ticket: #28230

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

- Don't recreate grub.cfg everytime a docker vm is launched. (#807)

Usually when we update RancherOS image it comes with a new kernel
version as well as a new initrd; so legacy images must be run with
previous settings we must keep them.

Ticket: #28230

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

- Don't recreate grub.cfg everytime a docker vm is launched. (#808)

Usually when we update RancherOS image it comes with a new kernel
version as well as a new initrd; so legacy images must be run with
previous settings we must keep them.

Ticket: #28230

History

#1 Updated by Dru Lavigne over 1 year ago

  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information

Tim: please attach a debug (System -> Advanced -> Save Debug) that was created shortly after a failed attempt at accessing the VM.

#2 Updated by Marcelo Araujo over 1 year ago

  • Status changed from Not Started to In Progress

I'm in touch with Tim Lee already, I have spoke with him during this week via Gtalk! I asked him to open this ticket just to account this case in my workflow.
He already setup the environment for my remote investigation of this issue.

I'm doing it now.

Thanks Dru an Tim.

#3 Updated by Marcelo Araujo over 1 year ago

  • Category set to Middleware
  • Assignee changed from Release Council to Marcelo Araujo
  • Priority changed from Important to Blocks Until Resolved
  • Target version set to 11.1-U2
  • Severity set to High

#4 Updated by Marcelo Araujo over 1 year ago

  • Status changed from In Progress to Done

#5 Updated by Dru Lavigne over 1 year ago

  • Subject changed from VM no longer boots after update to Don't recreate grub.cfg everytime a Docker VM is launched
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#6 Updated by Dru Lavigne over 1 year ago

  • Private changed from Yes to No

Also available in: Atom PDF