Your message dated Mon, 22 Jan 2024 01:38:57 +0000
with message-id <[email protected]>
and subject line Re: lxd: Flags `--property` & `-f` and option `source.wipe`
don't work
has caused the Debian Bug report #1052318,
regarding lxd: Flags `--property` & `-f` and option `source.wipe` don't work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1052318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052318
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxd
Version: 5.0.2-5
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
Let me describe, what I did and what I got after that:
0. Reinstalled Debian 12.1;
1. installed lxd package: `sudo apt install lxd`;
2. run init command: `sudo lxd init`;
3. configured managed network (lxdbr0) and btrfs pool using lvm logical volume
during init;
4. run launching command: `sudo lxc launch images:debian/12 deb-container`;
5. stopped instance;
First issue: flag `--property` doesn't work.
1. I tried to get some basic properties:
`sudo lxc config get deb-container name --property`;
2. received error:
`Error: unknown flag: --property`;
I expected to get `deb-container`.
I learned about this flag from the official documentation:
https://documentation.ubuntu.com/lxd/en/latest/howto/instances_configure/
Second issue: flag `-f` & option `storage.wipe=true` don't work.
1. I tried to create storage pool manually using lvm logical volume, that was
used before.
1.1. When I tried to create pool without additional options, I got error:
Command:
`sudo lxc storage create pool2 btrfs source=/dev/vg1/lv1-5gb`;
Response:
`Error: Failed to format block device: Failed to run: mkfs.btrfs -L pool2
/dev/vg1/lv1-5gb: exit status 1 (ERROR: /dev/vg1/lv1-5gb appears to contain a
partition table (dos)
ERROR: use the -f option to force overwrite of /dev/vg1/lv1-5gb)`;
1.2. Then I tried to set recommended option `source.wipe=true` but I got
another error:
Command:
`sudo lxc storage create pool2 btrfs source=/dev/vg1/lv1-5gb source.wipe=true`
Response:
`Error: Invalid option "source.wipe"`;
1.3. When I tried to use recommended flag `-f` I got one more error:
Command:
`sudo lxc storage create pool2 btrfs source=/dev/vg1/lv1-5gb -f`;
Response:
`Error: unknown shorthand flag: 'f' in -f`;
I expected to get a ready to use storage pool.
By running command: `sudo wipefs -af /dev/vg1/lv1-5gb` - this solves the
problem, but the issue is still there.
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lxd depends on:
ii adduser 3.134
ii attr 1:2.5.1-4
ii ca-certificates 20230311
ii init-system-helpers 1.65.2
ii libacl1 2.3.1-3
ii libc6 2.36-9+deb12u1
ii libcap2 1:2.66-4
ii libdqlite0 1.11.1-1
ii libgcc-s1 12.2.0-14
ii liblxc-common 1:5.0.2-1
ii liblxc1 1:5.0.2-1
ii libsqlite3-0 3.40.1-2
ii libudev1 252.12-1~deb12u1
ii lxcfs 5.0.3-1
ii lxd-client 5.0.2-5
ii rsync 3.2.7-1
ii squashfs-tools 1:4.5.1-1
ii uidmap 1:4.13+dfsg1-1+b1
ii xz-utils 5.4.1-0.2
Versions of packages lxd recommends:
ii apparmor 3.0.8-3
ii dnsmasq-base [dnsmasq-base] 2.89-1
ii lxd-agent 5.0.2-5
Versions of packages lxd suggests:
ii btrfs-progs 6.2-1
pn ceph-common <none>
ii gdisk 1.0.9-2.1
ii lvm2 2.03.16-2
ii lxd-tools 5.0.2-5
pn zfsutils-linux <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.0.2+git20231211.1364ae4-1
Upstream commits 988acb43ca163e10c421d34321377a6c99612db2 and
59afadbc36540dd0d30f9cae86200fbb828cd5f3 in the stable-5.0 branch
appear to fix the two reported issues. They are included in the
snapshot release of LXD currently in unstable.
I tested that the `--property` and `source.wipe=true` options now
work as expected.
Mathias
signature.asc
Description: This is a digitally signed message part
--- End Message ---
