Your message dated Fri, 15 Oct 2021 19:21:39 +0200
with message-id <[email protected]>
and subject line Re: Bug#945584: Acknowledgement (vmdb2: lvcreate fails, as if 
noudevsync is in play)
has caused the Debian Bug report #945584,
regarding vmdb2: lvcreate fails, as if noudevsync is in play
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.)


-- 
945584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945584
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vmdb2
Version: 0.13.2+git20190215-1

Hi,

I'm switching from vmdebootstrap, and I always used to lvcreate beforehand,
so I was pleasantly surprised to see this facility in vmdb2. Unfortunately,
it seems not to work at all on the fresh Debian 10 system where I tried it
like this:

The first step in foo-bar-1.vmdb.yml was:

  - lvcreate: vg0
    name: "{{ image }}"
    size: 4G

The invocation was:

% sudo vmdb2 foo-bar-1.vmdb.yml --image /dev/vg0/foo-bar-1-root --verbose 
--log=foo-bar-1.vmd.log

The log said:

2019-11-27 11:19:02 DEBUG Python version: 3.7.3 (default, Apr  3 2019, 
05:39:12) 
[GCC 8.3.0]
2019-11-27 11:19:02 INFO Load spec file foo-bar-1.vmdb.yml
2019-11-27 11:19:02 INFO Running step: {'lvcreate': 'vg0', 'name': 
'/dev/vg0/foo-bar-1-root', 'size': '4G'}
2019-11-27 11:19:02 INFO Calling <bound method LvcreateStepRunner.run of 
<lvm2_plugin.LvcreateStepRunner object at 0x7fc7530ca748>>
2019-11-27 11:19:02 INFO Exec: ['lvcreate', '--name', 
'/dev/vg0/foo-bar-1-root', '--size', '4G', 'vg0']
2019-11-27 11:19:02 DEBUG run external command: [['lvcreate', '--name', 
'/dev/vg0/foo-bar-1-root', '--size', '4G', 'vg0']]
2019-11-27 11:19:02 DEBUG STDOUT: b'  Logical volume "foo-bar-1-root" 
created.\n'
2019-11-27 11:19:02 ERROR 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/vmdb/app.py", line 107, in 
run_steps_helper
    method(step, self.settings, state)
  File "/usr/lib/python3/dist-packages/vmdb/plugins/lvm2_plugin.py", line 74, 
in run
    assert os.path.exists(lvdev)
AssertionError
2019-11-27 11:19:02 INFO Something went wrong, cleaning up!
2019-11-27 11:19:02 INFO Running teardown: {'lvcreate': 'vg0', 'name': 
'/dev/vg0/foo-bar-1-root', 'size': '4G'}
2019-11-27 11:19:02 INFO Calling <bound method StepRunnerInterface.teardown of 
<lvm2_plugin.LvcreateStepRunner object at 0x7fc7530ca748>>
2019-11-27 11:19:02 ERROR An error occurred, exiting with non-zero exit code

It's as if it ran lvcreate with --noudevsync or something, but that
shouldn't be...

Please fix it. TIA.

-- 
Josip Rodin

--- End Message ---
--- Begin Message ---
Hi,

This bug doesn't seem to be present in the bullseye version any more,
lvcreate doesn't choke the same way any more.

-- 
Josip Rodin

--- End Message ---

Reply via email to