Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Upgrade kernel versions #798

Merged
merged 3 commits into from
Mar 8, 2021
Merged

Upgrade kernel versions #798

merged 3 commits into from
Mar 8, 2021

Conversation

gaby
Copy link
Contributor

@gaby gaby commented Mar 5, 2021

  • Upgrade from kernel 4.14.182 to 4.14.223
  • Upgrade from kernel 4.19.125 to 4.19.178
  • Upgrade from kernel 5.4.43 to 5.4.102

Source: https://www.kernel.org/

  • Note: Versions as of 2021-03-04

  • Future proposal: Instead of pinned patch versions, determine the latest patch version via CI. Add a scheduled github workflow that downloads the latest patch versions on a weekly basis.

Upgrade kernels to latest versions from kernel.org
@gaby gaby changed the title Update kernel outdated versions Upgrade outdated kernel versions Mar 5, 2021
@gaby
Copy link
Contributor Author

gaby commented Mar 5, 2021

Build failed:

time="2021-03-05T06:40:50Z" level=info msg="Waiting for the ssh daemon within the VM to start..."05:30
    TestConcurrentVMCreation: zconcurrent_vm_test.go:48: assertion failed: error is not nil: exit status 1: error waiting for the command to finish05:30
    TestConcurrentVMCreation: zconcurrent_vm_test.go:48: assertion failed: error is not nil: exit status 1: error waiting for the command to finish05:30
    TestConcurrentVMCreation: zconcurrent_vm_test.go:50: assertion failed: error is not nil: exit status 1: cmd: 05:30
        "/home/semaphore/ignite/bin/ignite rm -f e2e-test-concurrent-vm-create-1 e2e-test-concurrent-vm-create-2 e2e-test-concurrent-vm-create-3 e2e-test-concurrent-vm-create-4"05:30
        time="2021-03-05T06:40:57Z" level=fatal msg="can't find VM: no ID/name matches for \"e2e-test-concurrent-vm-create-4\""05:30
        05:30
    TestConcurrentVMCreation: zconcurrent_vm_test.go:50: failed to run "/home/semaphore/ignite/bin/ignite rm -f e2e-test-concurrent-vm-create-1 e2e-test-concurrent-vm-create-2 e2e-test-concurrent-vm-create-3 e2e-test-concurrent-vm-create-4": exit status 105:30
--- FAIL: TestConcurrentVMCreation (9.00s)05:30
FAIL05:30
FAIL	github.com/weaveworks/ignite/e2e	327.120s05:30
FAIL05:30
Makefile:281: recipe for target 'e2e-nobuild' failed05:30
make: *** [e2e-nobuild] Error 1

@gaby
Copy link
Contributor Author

gaby commented Mar 5, 2021

Should be good now :-)

Added configuration files for new Kernel versions.
@gaby gaby changed the title Upgrade outdated kernel versions Upgrade kernel versions Mar 6, 2021
@gaby
Copy link
Contributor Author

gaby commented Mar 7, 2021

I have no idea why this is failing now, if it wasn't before?

@darkowlzz
Copy link
Contributor

I have no idea why this is failing now, if it wasn't before?

Don't worry about that. There's some test flake we are aware of. Reran the job and it's green now 🙂
Thanks for the patch.

@gaby
Copy link
Contributor Author

gaby commented Mar 8, 2021

These kernels are already 1 patch outdated. I will update the PR later today.

@stealthybox
Copy link
Contributor

These kernels are already 1 patch outdated. I will update the PR later today.

We can't be perpetually up to date in a way that will scale with manual action -- We're inclined to merge this now.

How often would you like to see the newest patches pushed if we do this in an automated fashion?
Weekly like you mentioned in the patch description?
Would that be useful for you (or others)?

We did start some pre-requisite work scripting against upstream kernel.org tags and could use the release machinery to automate this weekly.

@stealthybox stealthybox merged commit cb14cf0 into weaveworks:master Mar 8, 2021
@stealthybox
Copy link
Contributor

Merged -- feel free to continue discussion here
We also meet on Zoom every Monday (US morning timezone)

@gaby
Copy link
Contributor Author

gaby commented Mar 8, 2021

@stealthybox Makes sense, weekly updates of kernel versions would be ideal.

@gaby gaby deleted the upgrade-kernels branch March 8, 2021 16:16
@gaby
Copy link
Contributor Author

gaby commented Mar 8, 2021

@stealthybox It seems none of the new images got released. Are the github actions for new images only running when a new tag is created?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants