snap-discard-ns fails

Bug #1819887 reported by Ondrej Kubik
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
Triaged
High
Zygmunt Krynicki

Bug Description

snapd: 2.37.2
Ubuntu 18.04
core snap: 6405
kernel: 4.15.0-29-generic

Preconditions:
 Snap updated base from core16 to core18
 Snap has one or more services
 there is forked process dangling around

Expected result:
 snap refreshes to new revision using new core18 base

Actual result:
 snapd fails to identify forked process and unmount namespace

This is related to: https://bugs.launchpad.net/snappy/+bug/1819875

Associated logs:
https://paste.ubuntu.com/p/99Pz3wQ79P/
This shows where base is actually core16 while it should be core18
https://paste.ubuntu.com/p/7w6nRX4Y4J/
Offending process was process forked by the snap service
https://paste.ubuntu.com/p/7DmG45TYnz/
https://paste.ubuntu.com/p/fGPY9WNRrp/
https://paste.ubuntu.com/p/SkBMzTPpHX/
https://paste.ubuntu.com/p/4S3VJyJJCv/
After killing offending process manually
https://paste.ubuntu.com/p/g9SgydYsdq/

Zygmunt Krynicki (zyga)
Changed in snappy:
assignee: nobody → Zygmunt Krynicki (zyga)
Zygmunt Krynicki (zyga)
Changed in snappy:
status: New → Triaged
importance: Undecided → High
Zygmunt Krynicki (zyga)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.