cloud-init clean traceback on instance dir symlink

Bug #1741093 reported by Chad Smith on 2018-01-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Low
Chad Smith

Bug Description

cloud-init clean command traces when attempting to del_dir on the 'instance' symlink if instance is ordered before 'instances' when traversing the /var/lib/cloud directory.

smoser@milhouse:~$ lxc launch ubuntu-daily:bionic b4
Creating b4
Starting b4
smoser@milhouse:~$ lxc exec b4 -- ls -l /var/lib/cloud
total 4
drwxr-xr-x 2 root root 6 Jan 3 17:35 data
drwxr-xr-x 2 root root 2 Jan 3 17:35 handlers
lrwxrwxrwx 1 root root 27 Jan 3 17:35 instance -> /var/lib/cloud/instances/b4
drwxr-xr-x 3 root root 3 Jan 3 17:35 instances
drwxr-xr-x 6 root root 6 Jan 3 17:35 scripts
drwxr-xr-x 3 root root 3 Jan 3 17:35 seed
drwxr-xr-x 2 root root 2 Jan 3 17:35 sem
smoser@milhouse:~$ lxc exec b4 cloud-init clean
ERROR: Could not remove instance: Cannot call rmtree on a symbolic link

Related branches

Chad Smith (chad.smith) on 2018-01-03
Changed in cloud-init:
importance: Undecided → Low
assignee: nobody → Chad Smith (chad.smith)
status: New → Incomplete
status: Incomplete → In Progress
Chad Smith (chad.smith) on 2018-01-03
Changed in cloud-init:
status: In Progress → Fix Committed

This bug is believed to be fixed in cloud-init in 18.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
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