Bug 475490 - koan does not aware where the lvm tools are [f-10]
koan does not aware where the lvm tools are [f-10]
Product: Fedora
Classification: Fedora
Component: koan (Show other bugs)
All Linux
urgent Severity high
: ---
: ---
Assigned To: Michael DeHaan
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-09 08:51 EST by Anton Arapov
Modified: 2014-06-18 04:02 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-09 09:20:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
proposed patch (1.99 KB, patch)
2008-12-09 09:05 EST, Anton Arapov
no flags Details | Diff

  None (edit)
Description Anton Arapov 2008-12-09 08:51:59 EST

how to reproduce:
  # cobbler list
    distro F-10-i386
       profile F-10-i386
    distro F-10-x86_64
       profile F-10-x86_64
       system vguest

  # cobbler system add --name vguest --profile F-10-x86_64 --virt-type qemu --virt-bridge virbr0 --virt-path vg
  # koan --server 'host' --virt --system vguest
   - reading URL: http://host/cblr/svc/op/ks/system/vguest
   install_tree: http://download.fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/x86_64/os/
   libvirtd (pid  2677) is running...
   /usr/sbin/vgs -o vg_name
   File descriptor 3 left open

   /usr/sbin/vgs --noheadings -o vg_free --units g vg
   File descriptor 3 left open
   /usr/sbin/lvs -o lv_name vg
   /bin/sh: /usr/sbin/lvs: No such file or directory

   /usr/sbin/lvcreate -L 5G -n vguest1-disk0 vg
   /bin/sh: /usr/sbin/lvcreate: No such file or directory
   LVM creation failed

WHERE IS MY [lvcreate|lvs|vgs] ?
  # which vgs lvs lvcreate

does this ring the bells? :)
Comment 1 Anton Arapov 2008-12-09 09:05:11 EST
Created attachment 326315 [details]
proposed patch

with this patch everything working as expected
Comment 2 Michael DeHaan 2008-12-09 09:19:45 EST
Thanks, this is fixed already on the development branch (as of yesterday) and will be included in the 1.4 release.

Note You need to log in before you can comment on or make changes to this bug.