complex layouts referencing $SNAP_DATA broken with parallel instances

Bug #1906821 reported by Maciej Borzecki on 2020-12-04
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
High
Maciej Borzecki

Bug Description

Reported in the forum:

https://forum.snapcraft.io/t/layout-issues-in-aws-iot-greengrass-with-parallel-instances/21450

The following layout is created incorrectly inside aws-iot-greengrass_prime snap:

layout:
  $SNAP/greengrass/config:
    bind: $SNAP_DATA/user-certs/config
  $SNAP/greengrass/certs:
    bind: $SNAP_DATA/user-certs/certs
  /usr/bin/python3.8:
    symlink: $SNAP/usr/bin/python3.8
  /usr/bin/python3.7:
    # python3.7 lambdas will be redirected to python3.8
    symlink: $SNAP/usr/bin/python3.8
  $SNAP/usr/bin/python3:
    symlink: $SNAP/usr/bin/python3.8
  /usr/bin/python2.7:
    symlink: $SNAP/usr/bin/python2.7
  $SNAP/usr/bin/python:
    symlink: $SNAP/usr/bin/python2.7
  /usr/bin/nodejs12.x:
    symlink: $SNAP/wrapper-scripts/exec-node.sh
  /usr/bin/node:
    symlink: $SNAP/node-v12.18.4-linux/bin/node
  /usr/bin/java8:
    symlink: $SNAP/usr/lib/jvm/java-8-openjdk-arch-symlink/jre/bin/java
  /usr/bin/java:
    symlink: $SNAP/usr/lib/jvm/java-8-openjdk-arch-symlink/jre/bin/java

It appears that $SNAP/greengrass/certs has content coming from /var/snap/aws-iot-greengrass/current/user-certs/certs rather than /var/snap/aws-iot-greengrass_prime/current/user-certs/certs

Download full text (87.8 KiB)

TARGET SOURCE FSTYPE OPTIONS PROPAGATION
/ /dev/loop5 squashfs ro,nodev,relatime private,slave
├─/usr/bin tmpfs tmpfs rw,relatime,mode=755 private
│ ├─/usr/bin/[ /dev/loop5[/usr/bin/[] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/aa-enabled /dev/loop5[/usr/bin/aa-enabled] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/aa-exec /dev/loop5[/usr/bin/aa-exec] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/addpart /dev/loop5[/usr/bin/addpart] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/arch /dev/loop5[/usr/bin/arch] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/b2sum /dev/loop5[/usr/bin/b2sum] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/base32 /dev/loop5[/usr/bin/base32] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/base64 /dev/loop5[/usr/bin/base64] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/basename /dev/loop5[/usr/bin/basename] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/bashbug /dev/loop5[/usr/bin/bashbug] squashfs ro,nodev,relatime private,slave
│ ├─/usr/bin/bootctl /dev/loop5[/usr/bin/bootctl] squashfs ro,nodev,re...

Changed in snapd:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Maciej Borzecki (maciek-borzecki)
milestone: none → 2.48.2
summary: - layouts referencing $SNAP and $SNAP_DATA broken with parallel instances
+ complex layouts referencing $SNAP_DATA broken with parallel instances
Changed in snapd:
status: In Progress → Fix Committed
Paweł Stołowski (stolowski) wrote :

Released with 2.48.2

Changed in snapd:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers