conjure-up dropping privs did not work
Metadata
Current evaluation
User hit "dropping privs did not work" from conjure-up/lxd after a native+snap LXD install clash. No fix or PR; maintainer ~mr-cal closed it as stale in Aug 2026.
Resolution: closed stale
Reason: The only comment is maintainer ~mr-cal's "Closing as stale." after roughly 8 years of inactivity; no resolving PR, commit, or patch was referenced in snapcraft or the LXD snap, and the underlying cause (both native and snap LXD packages present, requiring lxd.migrate) was never addressed in the tracker.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Im not able to deploy openstack using conjure-up
commands ran are listed below
sudo snap install conjure-up --classic
[sudo] password for emb-aravkum:
snap "conjure-up" is already installed, see 'snap help refresh'
emb-aravkum@emb-ban-298:~$ sudo snap install lxd
snap "lxd" is already installed, see 'snap help refresh'
emb-aravkum@emb-ban-298:~$ /snap/bin/lxd init
Would you like to use LXD clustering? (yes/no) [default=no]:
Do you want to configure a new storage pool? (yes/no) [default=yes]:
Name of the new storage pool [default=default]:
The requested storage pool "default" already exists. Please choose another name.
Name of the new storage pool [default=default]: storagepool
Name of the storage backend to use (btrfs, ceph, dir, lvm, zfs) [default=zfs]: dir
Would you like to connect to a MAAS server? (yes/no) [default=no]:
Would you like to create a new local network bridge? (yes/no) [default=yes]:
What should the new bridge be called? [default=lxdbr0]:
What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]: none
Would you like LXD to be available over the network? (yes/no) [default=no]:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]:
emb-aravkum@emb-ban-298:~$ /snap/bin/lxd.migrate
error: This tool must be run as root.
emb-aravkum@emb-ban-298:~$ sudo /snap/bin/lxd.migrate
error: The following packages depend on [lxd lxd-client]: juju-2.0
emb-aravkum@emb-ban-298:~$ sudo usermod -a -G lxd $USER
emb-aravkum@emb-ban-298:~$ newgrp lxd
Cannot execute : No such file or directory
emb-aravkum@emb-ban-298:~$ sudo newgrp lxd
root@emb-ban-298:~# sudo newgrp lxd
root@emb-ban-298:~# /snap/bin/lxc storage list
dropping privs did not work: No such file or directory
root@emb-ban-298:~# sudo /snap/bin/lxc storage list
Error: Both native and snap packages are installed on this system
Run "lxd.migrate" to complete your migration to the snap package
root@emb-ban-298:~# lxd.migrate
dropping privs did not work: No such file or directory
root@emb-ban-298:~# systemctl stop lxd
Warning: Stopping lxd.service, but it can still be activated by:
lxd.socket
root@emb-ban-298:~# systemctl stop lxd.socket
root@emb-ban-298:~# systemctl start lxd.socket
root@emb-ban-298:~# conjure-up
dropping privs did not work
root@emb-ban-298:~# conjure-up
dropping privs did not work
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | User hit "dropping privs did not work" from conjure-up/lxd after a native+snap LXD install clash. No fix or PR; maintainer ~mr-cal closed it as stale in Aug 2026. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as stale after prolonged inactivity; no fix, resolving PR, or commit was cited. | |
| stealth/space-bunny-alpha | — | closed stale | Closed unresolved after conjure-up was deprecated; no fixing PR or commit was recorded for the LXD privilege-dropping failure. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The conjure-up project was deprecated and abandoned, superseding this privilege dropping error. Users are advised to use alternative deployment tools. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
100
Complexity:
20
Confidence:
95
Support Request:
80
|
close stale | User reports 'conjure-up dropping privs did not work' error while deploying OpenStack. Issue is 7+ years old, tool is discontinued, and error is a known legacy configuration conflict. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
100
Complexity:
20
Confidence:
90
Support Request:
75
|
close stale | User reports conjure-up failing with dropping privs did not work due to LXD/snap conflicts. Issue is 7+ years old, tool is deprecated, and shows no maintainer activity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
85
|
close stale | User reports deployment failure with conjure-up due to LXD privilege dropping errors. The issue is over seven years old, lacks maintainer interaction, and concerns a deprecated tool with environment-specific configuration conflicts. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1772885
(confidence 72%)
Still-open report of the same 'dropping privs did not work' LXD error on the same host tooling, indicating the problem was never resolved here.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1772885 dropping privs did not work: No data available | snapcraft (launchpad) | open | User asks for help with `sudo lxd init` failing with 'dropping privs did not work: no data available' while setting up Snapcraft — an LXD/host environment support question, not a Snapcraft defect; no labels, no replies. |