In progress: snapd 2.26.9

snapd
3

Submitted https://github.com/snapcore/snapd/pull/3285

4

The 2.26 release is available in the beta core snap now.

5

The 2.26 release is now also available on github and got uploaded to {trusty,xenial,yakkety,zesty,artful}-proposed.

6

A new 2.26.1 release was is in progress. The main reasons are:

7

2.26.1 is now available in the beta core snap and also uploaded to {trusty,xenial,yakkety,zesty}-proposed (waiting for approval) and to artful.

8

The core snap got updated to snapd 2.26.2. The only change is an update to the uboot.env handling to fix a crash for certain uboot.env files. It is only relevant for the uboot based devices. @fgimenez please run the beta validation with the new core from beta. A nice side-effect of the update is also that the version number of snapd now shows in snap info core :slight_smile:

1 Like
9

The core snap got updated to snapd 2.26.3. No code changes, just test updates for:

  • change in the snap info core output, the new core displays a richer version number now
  • the log-observer-consumer test had to be updated because we do not ship rsyslog on the image anymore

Please run the tests again on those @fgimenez

1 Like
10

Package updates for Fedora to v2.26.3 are pending:

11

The validation on beta went well for all the architectures:
Execution with an image built from the beta channel with kernel from stable:

Refresh core from stable image to beta channel before the execution:

console-conf automated tests:

2.25 hasn’t been promoted yet to stable due to aa problem found Snapd 2.25 blocked because of revert race condition as soon as it is unblocked 2.26 can be promoted to candidate.

12

A new 2.26.4 got released that fixes the issue outlined in Snapd 2.25 blocked because of revert race condition

13

@mvo “got released” means it is in stable, candidate or beta or just tagged in github? :slight_smile:

14

Ups, sorry! It means “got tagged on github” :slight_smile:

1 Like
15

The validation of 2.26.4 ot beta was successful:
Execution with an image built from the beta channel with kernel from stable:

Refresh core from stable image to beta channel before the execution:

console-conf automated tests:

core-revert test:

The snap is about to be promoted, I’ll post here once it is available on candidate.

2 Likes
16

The promotion to candidate has been done and the call for testing has been sent Call for testing: core snap 16-2.25, the manual checks performed by the snapd team at this stage will take us 1 additional day.

17

Thanks! We’re waiting it to be released. I can confirm that timezone interface fix worked fine.

1 Like
18

Unfortunately this release is also stuck right now because of Snapd 2.25 blocked because of revert race condition - we have a PR that should fix the issue under review, once that lands we can proceed with 2.26.

19

A new 2.26.6 release is available now and is available in the beta channel.

1 Like
20

I can confirm that time-zone fix is worked on the beta channel.

21

The validation of 2.26.8 on beta was successful and the snap has been promoted to candidate, these are the results:
Execution with an image built from the beta channel with kernel from stable:

Refresh core from stable image to beta channel before the execution:

console-conf automated tests:

core-revert test:
amd64: http://paste.ubuntu.com/25025726/

1 Like
22

The validation for the new 2.26.9 including fixes for the issue described in 2.26.8 libseccomp on trusty was successful and it has been promoted to candidate, these are the test results:

Execution with an image built from the beta channel with kernel from stable:

Refresh core from stable image to beta channel before the execution:

console-conf automated tests:

core-revert test:

snapd deb from proposed: