[ovirt-users] Re: Cloning VM selecting part of the disks

2022-03-22 Thread Arik Hadas 
On Tue, Mar 22, 2022 at 12:16 PM Gianluca Cecchi 
wrote:

> Hello,
> in recent versions of oVirt (eg my last 4.4.10) there is the feature to
> make a clone of a running  VM.
> This operation passes through a temporary VM snapshot (then automatically
> deleted) and cloning of this snapshot.
>

For the most part, yes (we now skip the creation of the snapshot when the
VM uses MBS disks)


> Sometimes there is a need to clone a VM but only a subset of its disks is
> required (eg in my case I want to retain boot disk, 20Gb, and dedicated sw
> disk, 20Gb, but not data disk, that usually is big... in my case 200Gb).
> In this scenario I have to go the old path where I explicitly create a
> snapshot of the VM, where I can select a subset of the disks, then I clone
> the snapshot and last I delete the snapshot.
>
Do you think it is interesting to have the option of selecting disks when
> you clone a running VM and go automatic..?
>
If I want to open a bugzilla as RFE, what components and options I have to
> select?
>

The initial idea behind clone-VM was to have a simple operation for getting
an exact-clone (sure, with different ID, different MAC addresses and so on)
of an existing VM without going through the cycle you mentioned of:
creating a snapshot, cloning a VM from the snapshot and removing the
snapshot

While external contributions for adding the ability to filter the disks of
the cloned VM would be welcome, it's unlikely to be something we would get
to since there is an alternative way to achieve this and it's not
considered to be a common scenario


>
> Thanks,
> Gianluca
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/CO34RAB2EOA3IYA4LDSLTZYY4MR4UQJA/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/W5E6R53EYFUFDTCTAF5TMFJC4FF5TBCK/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Abe E 
Thank You.
I've tried to re-install the current ovirt package only 
(ovirt-engine-appliance-4.4-20220308105414.1.el8.x86_64.rpm). 

My Ovirt Hose is running 4.4. I am not sure if we can fully rely on the info 
ovirt reports being that it sees this server as "not responding" but these are 
specs:

OS Version:
RHEL - 8.6.2109.0 - 1.el8
OS Description:
oVirt Node 4.4.10
Kernel Version:
4.18.0 - 358.el8.x86_64
KVM Version:
6.0.0 - 33.el8s
LIBVIRT Version:
libvirt-7.10.0-1.module_el8.6.0+1046+bd8eec5e
VDSM Version:
vdsm-4.40.100.2-1.el8
SPICE Version:
0.14.3 - 4.el8
GlusterFS Version:
glusterfs-8.6-2.el8s
CEPH Version:
librbd1-16.2.7-1.el8s
Open vSwitch Version:
openvswitch-2.11-1.el8
Nmstate Version:
nmstate-1.2.1-0.2.alpha2.el8
Kernel Features:
MDS: (Mitigation: Clear CPU buffers; SMT vulnerable), L1TF: (Mitigation: PTE 
Inversion; VMX: conditional cache flushes, SMT vulnerable), SRBDS: (Not 
affected), MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: 
usercopy/swapgs barriers and __user pointer sanitization), SPECTRE_V2: 
(Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: 
conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: VMX disabled), 
TSX_ASYNC_ABORT: (Mitigation: Clear CPU buffers; SMT vulnerable), 
SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and 
seccomp)
VNC Encryption:
Disabled
FIPS mode enabled:
Disabled
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CCVHO5V7E3Z4OSG6LAIAQOA6GVL76F3T/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Nir Soffer 
On Tue, Mar 22, 2022 at 8:14 PM Abe E  wrote:

> Apologies, here it is
> [root@ovirt-2 ~]# vdsm-tool config-lvm-filter
> Analyzing host...
> Found these mounted logical volumes on this host:
>
>   logical volume:  /dev/mapper/gluster_vg_sda4-gluster_lv_data
>   mountpoint:  /gluster_bricks/data
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU
>
>   logical volume:  /dev/mapper/gluster_vg_sda4-gluster_lv_engine
>   mountpoint:  /gluster_bricks/engine
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU
>
>   logical volume:  /dev/mapper/onn-home
>   mountpoint:  /home
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:
> /dev/mapper/onn-ovirt--node--ng--4.4.10.1--0.20220202.0+1
>   mountpoint:  /
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:  /dev/mapper/onn-swap
>   mountpoint:  [SWAP]
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:  /dev/mapper/onn-tmp
>   mountpoint:  /tmp
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:  /dev/mapper/onn-var
>   mountpoint:  /var
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:  /dev/mapper/onn-var_crash
>   mountpoint:  /var/crash
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:  /dev/mapper/onn-var_log
>   mountpoint:  /var/log
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
>   logical volume:  /dev/mapper/onn-var_log_audit
>   mountpoint:  /var/log/audit
>   devices:
>  /dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY
>
> This is the recommended LVM filter for this host:
>
>   filter = [
> "a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|",
> "a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|",
> "r|.*|" ]
>
> This filter allows LVM to access the local devices used by the
> hypervisor, but not shared storage owned by Vdsm. If you add a new
> device to the volume group, you will need to edit the filter manually.
>
> This is the current LVM filter:
>
>   filter = [
> "a|^/dev/disk/by-id/lvm-pv-uuid-3QbgiW-WaOV-ejW9-rs5R-akfW-sUZb-AXm8Pq$|",
> "a|^/dev/sda|", "r|.*|" ]
>
> To use the recommended filter we need to add multipath
> blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:
>
>   blacklist {
>   wwid "364cd98f06762ec0029afc17a03e0cf6a"
>   }
>
>
> WARNING: The current LVM filter does not match the recommended filter,
> Vdsm cannot configure the filter automatically.
>
> Please edit /etc/lvm/lvm.conf and set the 'filter' option in the
> 'devices' section to the recommended value.
>
> Make sure /etc/multipath/conf.d/vdsm_blacklist.conf is set with the
> recommended 'blacklist' section.
>
> It is recommended to reboot to verify the new configuration.
>
> After configuring the LVM to the recommended
>
> I adjusted to the recommended filter although it is still returning the
> same results when i run the vdsm-tool config-lvm-filter command. Instead I
> did as you mentioned, I commented out my current filter and ran the
> vdsm-tool config-lvm-filter and it configured successfully and I rebooted
> the node.
>
> Now on boot it is returning the following which looks alot better.
> Analyzing host...
> LVM filter is already configured for Vdsm
>

Good, we solved the storage issue.


> Now my error on re-install is Host ovirt-2... installation failed. Task
> Configure host for vdsm failed to execute. THat was just a re-install and
> this host currently has and the log returns this output, let me know if
> youd like more from it but this is where it errors out it seems:
>
> "start_line" : 215,
> "end_line" : 216,
> "runner_ident" : "ddb84e00-aa0a-11ec-98dc-00163e6f31f1",
> "event" : "runner_on_failed",
> "pid" : 83339,
> "created" : "2022-03-22T18:09:08.381022",
> "parent_uuid" : "00163e6f-31f1-a3fb-8e1d-0201",
> "event_data" : {
>   "playbook" : "ovirt-host-deploy.yml",
>   "playbook_uuid" : "2e84fbd4-8368-463e-82e7-3f457ae702d4",
>   "play" : "all",
>   "play_uuid" : "00163e6f-31f1-a3fb-8e1d-000b",
>   "play_pattern" : "all",
>   "task" : "Configure host for vdsm",
>   "task_uuid" : "00163e6f-31f1-a3fb-8e1d-0201",
>   "task_action" : "command",
>   "task_args" : "",
>   "task_path" :
> "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/configure.yml:27",
>   "role" : "ovirt-host-deploy-vdsm",
>   "host" : "ovirt-2..com",
>   "remote_addr" : "ovirt-2..com",
>   "res" : {
> "msg" : "non-zero return code",
> "cmd" : [ "vdsm-tool", "configure", "--force" ],
>

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Abe E 
Apologies, here it is
[root@ovirt-2 ~]# vdsm-tool config-lvm-filter
Analyzing host...
Found these mounted logical volumes on this host:

  logical volume:  /dev/mapper/gluster_vg_sda4-gluster_lv_data
  mountpoint:  /gluster_bricks/data
  devices: 
/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU

  logical volume:  /dev/mapper/gluster_vg_sda4-gluster_lv_engine
  mountpoint:  /gluster_bricks/engine
  devices: 
/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU

  logical volume:  /dev/mapper/onn-home
  mountpoint:  /home
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-ovirt--node--ng--4.4.10.1--0.20220202.0+1
  mountpoint:  /
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-swap
  mountpoint:  [SWAP]
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-tmp
  mountpoint:  /tmp
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-var
  mountpoint:  /var
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-var_crash
  mountpoint:  /var/crash
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-var_log
  mountpoint:  /var/log
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

  logical volume:  /dev/mapper/onn-var_log_audit
  mountpoint:  /var/log/audit
  devices: 
/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY

This is the recommended LVM filter for this host:

  filter = [ 
"a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|", 
"a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|", 
"r|.*|" ]

This filter allows LVM to access the local devices used by the
hypervisor, but not shared storage owned by Vdsm. If you add a new
device to the volume group, you will need to edit the filter manually.

This is the current LVM filter:

  filter = [ 
"a|^/dev/disk/by-id/lvm-pv-uuid-3QbgiW-WaOV-ejW9-rs5R-akfW-sUZb-AXm8Pq$|", 
"a|^/dev/sda|", "r|.*|" ]

To use the recommended filter we need to add multipath
blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:

  blacklist {
  wwid "364cd98f06762ec0029afc17a03e0cf6a"
  }


WARNING: The current LVM filter does not match the recommended filter,
Vdsm cannot configure the filter automatically.

Please edit /etc/lvm/lvm.conf and set the 'filter' option in the
'devices' section to the recommended value.

Make sure /etc/multipath/conf.d/vdsm_blacklist.conf is set with the
recommended 'blacklist' section.

It is recommended to reboot to verify the new configuration.

After configuring the LVM to the recommended 

I adjusted to the recommended filter although it is still returning the same 
results when i run the vdsm-tool config-lvm-filter command. Instead I did as 
you mentioned, I commented out my current filter and ran the vdsm-tool 
config-lvm-filter and it configured successfully and I rebooted the node.

Now on boot it is returning the following which looks alot better.
Analyzing host...
LVM filter is already configured for Vdsm


Now my error on re-install is Host ovirt-2... installation failed. Task 
Configure host for vdsm failed to execute. THat was just a re-install and this 
host currently has and the log returns this output, let me know if youd like 
more from it but this is where it errors out it seems:

"start_line" : 215,
"end_line" : 216,
"runner_ident" : "ddb84e00-aa0a-11ec-98dc-00163e6f31f1",
"event" : "runner_on_failed",
"pid" : 83339,
"created" : "2022-03-22T18:09:08.381022",
"parent_uuid" : "00163e6f-31f1-a3fb-8e1d-0201",
"event_data" : {
  "playbook" : "ovirt-host-deploy.yml",
  "playbook_uuid" : "2e84fbd4-8368-463e-82e7-3f457ae702d4",
  "play" : "all",
  "play_uuid" : "00163e6f-31f1-a3fb-8e1d-000b",
  "play_pattern" : "all",
  "task" : "Configure host for vdsm",
  "task_uuid" : "00163e6f-31f1-a3fb-8e1d-0201",
  "task_action" : "command",
  "task_args" : "",
  "task_path" : 
"/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/configure.yml:27",
  "role" : "ovirt-host-deploy-vdsm",
  "host" : "ovirt-2..com",
  "remote_addr" : "ovirt-2..com",
  "res" : {
"msg" : "non-zero return code",
"cmd" : [ "vdsm-tool", "configure", "--force" ],
"stdout" : "\nChecking configuration status...\n\nlibvirt is already 
configured for vdsm\nSUCCESS: ssl configured to true. No conflicts\nManaged 
volume database is already configured\nlvm is configured for vdsm\nsanlock is

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Nir Soffer 
On Tue, Mar 22, 2022 at 7:17 PM Nir Soffer  wrote:
>
> On Tue, Mar 22, 2022 at 6:57 PM Abe E  wrote:
> >
> > Yes it throws the following:
> >
> > This is the recommended LVM filter for this host:
> >
> >   filter = [
"a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|",
"a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|",
"r|.*|" ]
>
> This is not complete output - did you strip the lines explaining why
> we need this
> filter?
>
> > This filter allows LVM to access the local devices used by the
> > hypervisor, but not shared storage owned by Vdsm. If you add a new
> > device to the volume group, you will need to edit the filter manually.
> >
> > This is the current LVM filter:
> >
> >   filter = [
"a|^/dev/disk/by-id/lvm-pv-uuid-3QbgiW-WaOV-ejW9-rs5R-akfW-sUZb-AXm8Pq$|",
"a|^/dev/sda|", "r|.*|" ]
>
> So the issue is that you likely have a stale lvm filter for a device
> which is not
> used by the host.
>
> >
> > To use the recommended filter we need to add multipath
> > blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:
> >
> >   blacklist {
> >   wwid "364cd98f06762ec0029afc17a03e0cf6a"
> >   }
> >
> >
> > WARNING: The current LVM filter does not match the recommended filter,
> > Vdsm cannot configure the filter automatically.
> >
> > Please edit /etc/lvm/lvm.conf and set the 'filter' option in the
> > 'devices' section to the recommended value.
> >
> > Make sure /etc/multipath/conf.d/vdsm_blacklist.conf is set with the
> > recommended 'blacklist' section.
> >
> > It is recommended to reboot to verify the new configuration.
> >
> >
> >
> >
> > I updated my entry to the following (Blacklist is already configured
from before):
> >   filter = [
"a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|","a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|","a|^/dev/sda|","r|.*|"
]
> >
> >
> > although then it threw this error
> >
> > [root@ovirt-2 ~]# vdsm-tool config-lvm-filter
> > Analyzing host...
> > Parse error at byte 106979 (line 2372): unexpected token
> >   Failed to load config file /etc/lvm/lvm.conf
> > Traceback (most recent call last):
> >   File "/usr/bin/vdsm-tool", line 209, in main
> > return tool_command[cmd]["command"](*args)
> >   File
"/usr/lib/python3.6/site-packages/vdsm/tool/config_lvm_filter.py", line 65,
in main
> > mounts = lvmfilter.find_lvm_mounts()
> >   File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py",
line 170, in find_lvm_mounts
> > vg_name, tags = vg_info(name)
> >   File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py",
line 467, in vg_info
> > lv_path
> >   File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py",
line 566, in _run
> > out = subprocess.check_output(args)
> >   File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
> > **kwargs).stdout
> >   File "/usr/lib64/python3.6/subprocess.py", line 438, in run
> > output=stdout, stderr=stderr)
> > subprocess.CalledProcessError: Command '['/usr/sbin/lvm', 'lvs',
'--noheadings', '--readonly', '--config', 'devices {filter=["a|.*|"ed
non-zero exit status 4.
>
>
> I'm not sure if this error comes from the code configuring lvm filter,
> or from lvm.
>
> The best way to handle this depends on why you have lvm filter that
> vdsm-tool cannot handle.
>
> If you know why the lvm filter is set to the current value, and you
> know that the system actually
> need all the devices in the filter, you can keep the current lvm filter.
>
> If you don't know why the curent lvm filter is set to this value, you
> can remove the lvm filter
> from lvm.conf, and run "vdsm-tool config-lvm-filter" to let the tool
> configure the default filter.
>
> In general, the lvm filter allows the host to access the devices
> needed by the host, for
> example the root file system.
>
> If you are not sure what are the required devices, please share the
> the *complete* output
> of running "vdsm-tool config-lvm-filter", with lvm.conf that does not
> include any filter.

Example of running config-lvm-filter on RHEL 8.6 host with oVirt 4.5:

# vdsm-tool config-lvm-filter
Analyzing host...
Found these mounted logical volumes on this host:

  logical volume:  /dev/mapper/rhel-root
  mountpoint:  /
  devices: /dev/vda2

  logical volume:  /dev/mapper/rhel-swap
  mountpoint:  [SWAP]
  devices: /dev/vda2

  logical volume:  /dev/mapper/test-lv1
  mountpoint:  /data
  devices: /dev/mapper/0QEMU_QEMU_HARDDISK_123456789

Configuring LVM system.devices.
Devices for following VGs will be imported:

 rhel, test

Configure host? [yes,NO]

The tool shows that we have 3 mounted logical volumes, and suggest to
configure lvmdevices file for 2 volume groups.

On oVirt 4.4, the configuration method is lvm filter, and suggests the
required
filter for the mounted logical volumes.
___
Users mailing list -- users@ovirt.org
To unsubscribe

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Nir Soffer 
On Tue, Mar 22, 2022 at 6:57 PM Abe E  wrote:
>
> Yes it throws the following:
>
> This is the recommended LVM filter for this host:
>
>   filter = [ 
> "a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|", 
> "a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|", 
> "r|.*|" ]

This is not complete output - did you strip the lines explaining why
we need this
filter?

> This filter allows LVM to access the local devices used by the
> hypervisor, but not shared storage owned by Vdsm. If you add a new
> device to the volume group, you will need to edit the filter manually.
>
> This is the current LVM filter:
>
>   filter = [ 
> "a|^/dev/disk/by-id/lvm-pv-uuid-3QbgiW-WaOV-ejW9-rs5R-akfW-sUZb-AXm8Pq$|", 
> "a|^/dev/sda|", "r|.*|" ]

So the issue is that you likely have a stale lvm filter for a device
which is not
used by the host.

>
> To use the recommended filter we need to add multipath
> blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:
>
>   blacklist {
>   wwid "364cd98f06762ec0029afc17a03e0cf6a"
>   }
>
>
> WARNING: The current LVM filter does not match the recommended filter,
> Vdsm cannot configure the filter automatically.
>
> Please edit /etc/lvm/lvm.conf and set the 'filter' option in the
> 'devices' section to the recommended value.
>
> Make sure /etc/multipath/conf.d/vdsm_blacklist.conf is set with the
> recommended 'blacklist' section.
>
> It is recommended to reboot to verify the new configuration.
>
>
>
>
> I updated my entry to the following (Blacklist is already configured from 
> before):
>   filter = [ 
> "a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|","a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|","a|^/dev/sda|","r|.*|"
>  ]
>
>
> although then it threw this error
>
> [root@ovirt-2 ~]# vdsm-tool config-lvm-filter
> Analyzing host...
> Parse error at byte 106979 (line 2372): unexpected token
>   Failed to load config file /etc/lvm/lvm.conf
> Traceback (most recent call last):
>   File "/usr/bin/vdsm-tool", line 209, in main
> return tool_command[cmd]["command"](*args)
>   File "/usr/lib/python3.6/site-packages/vdsm/tool/config_lvm_filter.py", 
> line 65, in main
> mounts = lvmfilter.find_lvm_mounts()
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py", line 
> 170, in find_lvm_mounts
> vg_name, tags = vg_info(name)
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py", line 
> 467, in vg_info
> lv_path
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py", line 
> 566, in _run
> out = subprocess.check_output(args)
>   File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
> **kwargs).stdout
>   File "/usr/lib64/python3.6/subprocess.py", line 438, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command '['/usr/sbin/lvm', 'lvs', 
> '--noheadings', '--readonly', '--config', 'devices {filter=["a|.*|"ed 
> non-zero exit status 4.


I'm not sure if this error comes from the code configuring lvm filter,
or from lvm.

The best way to handle this depends on why you have lvm filter that
vdsm-tool cannot handle.

If you know why the lvm filter is set to the current value, and you
know that the system actually
need all the devices in the filter, you can keep the current lvm filter.

If you don't know why the curent lvm filter is set to this value, you
can remove the lvm filter
from lvm.conf, and run "vdsm-tool config-lvm-filter" to let the tool
configure the default filter.

In general, the lvm filter allows the host to access the devices
needed by the host, for
example the root file system.

If you are not sure what are the required devices, please share the
the *complete* output
of running "vdsm-tool config-lvm-filter", with lvm.conf that does not
include any filter.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7BEWQBE5MRLPL7PDK3CPECZDOS5Q62X7/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Abe E 
Yes it throws the following:

This is the recommended LVM filter for this host:

  filter = [ 
"a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|", 
"a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|", 
"r|.*|" ]

This filter allows LVM to access the local devices used by the
hypervisor, but not shared storage owned by Vdsm. If you add a new
device to the volume group, you will need to edit the filter manually.

This is the current LVM filter:

  filter = [ 
"a|^/dev/disk/by-id/lvm-pv-uuid-3QbgiW-WaOV-ejW9-rs5R-akfW-sUZb-AXm8Pq$|", 
"a|^/dev/sda|", "r|.*|" ]

To use the recommended filter we need to add multipath
blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:

  blacklist {
  wwid "364cd98f06762ec0029afc17a03e0cf6a"
  }


WARNING: The current LVM filter does not match the recommended filter,
Vdsm cannot configure the filter automatically.

Please edit /etc/lvm/lvm.conf and set the 'filter' option in the
'devices' section to the recommended value.

Make sure /etc/multipath/conf.d/vdsm_blacklist.conf is set with the
recommended 'blacklist' section.

It is recommended to reboot to verify the new configuration.




I updated my entry to the following (Blacklist is already configured from 
before):
  filter = [ 
"a|^/dev/disk/by-id/lvm-pv-uuid-DxNDT5-3NH3-I1YJ-0ajl-ah6W-M7Kf-h5uZKU$|","a|^/dev/disk/by-id/lvm-pv-uuid-Yepp1J-dsfN-jLh7-xCxm-G7QC-nbaL-6rT2KY$|","a|^/dev/sda|","r|.*|"
 ]


although then it threw this error

[root@ovirt-2 ~]# vdsm-tool config-lvm-filter
Analyzing host...
Parse error at byte 106979 (line 2372): unexpected token
  Failed to load config file /etc/lvm/lvm.conf
Traceback (most recent call last):
  File "/usr/bin/vdsm-tool", line 209, in main
return tool_command[cmd]["command"](*args)
  File "/usr/lib/python3.6/site-packages/vdsm/tool/config_lvm_filter.py", line 
65, in main
mounts = lvmfilter.find_lvm_mounts()
  File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py", line 170, 
in find_lvm_mounts
vg_name, tags = vg_info(name)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py", line 467, 
in vg_info
lv_path
  File "/usr/lib/python3.6/site-packages/vdsm/storage/lvmfilter.py", line 566, 
in _run
out = subprocess.check_output(args)
  File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
**kwargs).stdout
  File "/usr/lib64/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/usr/sbin/lvm', 'lvs', 
'--noheadings', '--readonly', '--config', 'devices {filter=["a|.*|"ed non-zero 
exit status 4.




I thought maybe it required a reboot although now it failed to reboot so I am 
physically going to check on it.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PSEJMBG7Y45P4THKYO2RAPWG6LDPLDOI/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Nir Soffer 
On Tue, Mar 22, 2022 at 6:09 PM Abe E  wrote:
>
> Interestingly enough I am able to re-install ovirt from the engine to a 
> certain point.
> I ran a re-install and it failed asking me to run vdsm-tool config-lvm-filter
> Error: Installing Host ovirt-2... Check for LVM filter configuration error: 
> Cannot configure LVM filter on host, please run: vdsm-tool config-lvm-filter.

Did you try to run it?

Please the complete output of running:

   vdsm-tool config-lvm-filter

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MIHVMDALDKFZGVTIDGHO6C4UBFL63XLG/

[ovirt-users] Re: VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Abe E 
Interestingly enough I am able to re-install ovirt from the engine to a certain 
point.
I ran a re-install and it failed asking me to run vdsm-tool config-lvm-filter
Error: Installing Host ovirt-2... Check for LVM filter configuration error: 
Cannot configure LVM filter on host, please run: vdsm-tool config-lvm-filter.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WEF6VN5VB3YD6OWQHODG6MWNJKPLQMXU/

[ovirt-users] Re: Engine across Clusters

2022-03-22 Thread Abe E 
Interesting points, thank you btw
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HT3EXOVIJRR2BLKM6YQYKD5RUXNV66PA/

[ovirt-users] Re: Engine across Clusters

2022-03-22 Thread Abe E 
As always thank you Patrick!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/43NGSLFR67YROAXABHM2VTYLFI3OBVJP/

[ovirt-users] VDSM Issue after Upgrade of Node in HCI

2022-03-22 Thread Abe E 
So I have my 2nd node in my cluster that showed an upgrade option in OVIRT.
I put it in maint mode and ran the upgrade, it went through it but at one point 
it lost its internet connection or connection within the gluster, it didnt get 
to the reboot process and simply lost its connection to the engine from there.

I can see the gluster is still running and was able to keep all 3 glusters 
syncing but it seems the VDSM may be the culprit here.


ovirt-ha-agent wont start and the hosted-engine --connect-storage returns:

Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py",
 line 30, in 
timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT,
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 312, in connect_storage_server
sserver.connect_storage_server(timeout=timeout)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py",
 line 411, in connect_storage_server
timeout=timeout,
  File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", 
line 474, in connect_vdsm_json_rpc
__vdsm_json_rpc_connect(logger, timeout)
  File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", 
line 415, in __vdsm_json_rpc_connect
timeout=VDSM_MAX_RETRY * VDSM_DELAY
RuntimeError: Couldn't  connect to VDSM within 60 seconds


VDSM just keeps loop restart and failing, vdsm-tool configure --force throws 
this :

[root@ovirt-2 ~]# vdsm-tool configure --force

Checking configuration status...

sanlock is configured for vdsm
abrt is already configured for vdsm
Current revision of multipath.conf detected, preserving
lvm is configured for vdsm
Managed volume database is already configured
libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts

Running configure...
libsepol.context_from_record: type insights_client_var_lib_t is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert 
system_u:object_r:insights_client_var_lib_t:s0 to sid
invalid context system_u:object_r:insights_client_var_lib_t:s0
libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error 
code 255.
Traceback (most recent call last):
  File "/usr/bin/vdsm-tool", line 209, in main
return tool_command[cmd]["command"](*args)
  File "/usr/lib/python3.6/site-packages/vdsm/tool/__init__.py", line 40, in 
wrapper
func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py", line 145, 
in configure
_configure(c)
  File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py", line 92, 
in _configure
getattr(module, 'configure', lambda: None)()
  File "/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py", 
line 88, in configure
_setup_booleans(True)
  File "/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py", 
line 60, in _setup_booleans
sebool_obj.finish()
  File "/usr/lib/python3.6/site-packages/seobject.py", line 340, in finish
self.commit()
  File "/usr/lib/python3.6/site-packages/seobject.py", line 330, in commit
rc = semanage_commit(self.sh)
OSError: [Errno 0] Error



Anyone have ideas where I could recover this, I am not sure if something 
corrupted on update or on a reboot -- I would prefer updating notes from the 
CLI next time but unfortunately I have not looked that far, it would have 
helped me see what failed and where much easier.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RZQR5PNHTM4WNS4RHB6KIGYAANOLWSI3/

[ovirt-users] Re: Gluster issue with brick going down

2022-03-22 Thread Jiří Sléžka 

Hi,

On 3/21/22 14:12, Chris Adams wrote:

I have a hyper-converged cluster running oVirt 4.4.10 and Gluster 8.6.
Periodically, one brick of one volume will drop out, but it's seemingly
random as to which volume and brick is affected.  All I see in the brick
log is:

[2022-03-19 13:27:36.360727] W [MSGID: 113075] 
[posix-helpers.c:2135:posix_fs_health_check] 0-vmstore-posix: 
aio_read_cmp_buf() on /gluster_bricks/vmstore/vmstore/.glusterfs/health_check 
returned ret is -1 error is Structure needs cleaning
[2022-03-19 13:27:36.361160] M [MSGID: 113075] 
[posix-helpers.c:2214:posix_health_check_thread_proc] 0-vmstore-posix: 
health-check failed, going down
[2022-03-19 13:27:36.361395] M [MSGID: 113075] 
[posix-helpers.c:2232:posix_health_check_thread_proc] 0-vmstore-posix: still 
alive! -> SIGTERM

Searching around, I see references to similar issues, but no real
solutions.  I see a suggestion that changing the health-check-interval
from 10 to 30 seconds helps, but it looks like 30 seconds is the default
with this version of Gluster (and I don't see it explicitly set for any
of my volumes).

While "Structure needs cleaning" appears to be an XFS filesystem error,
I don't see any XFS errors from the kernel.

This is a low I/O cluster - the storage network is on two 10 gig
switches with a two-port LAG to each server, but typically is only
seeing a few tens of megabits per second.


I experience the same behavior. Workaround could be disabling 
health-check like


gluster volume set  storage.health-check-interval 0

In my case it helped with bricks randomly going offline.

There is something else broken in my hci cluster because I have also 
problem with sanlock which time to time cannot renew lock and wdmd 
reboots one or two hosts. I still cannot find the root of this behavior 
but it is probably hw related.


Cheers,

Jiri







smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/G4KBSP3Y7WEBTB6XV7L2P2RJPMD2E5ZA/

[ovirt-users] Re: Unable to deploy ovirt 4.4 on alma 8.5

2022-03-22 Thread atatur . yildirim 
Hi,
Most of the time these kind of errors are due to company/ISP firewall 
limitations. Please check and make sure they are ok.
Regards..
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DH435A3UXVYLUZDTFWKA7N66BN7QE7QM/

[ovirt-users] Re: Zanata user request

2022-03-22 Thread Sharon Gratch 
Hi Temuri,

I activated your account on Zanata (you already had one) and added you to
the Georgian translation group.
I'll send you the account details in a separate mail.

Thanks for willing to help with translations!
Sharon

On Mon, Mar 21, 2022 at 3:32 PM Sandro Bonazzola 
wrote:

> +Sharon Gratch  +Scott Dickerson 
>  +Michal Skrivanek  can you help here?
>
> Il giorno lun 21 mar 2022 alle ore 11:23 Temuri Doghonadze <
> temuri.doghona...@gmail.com> ha scritto:
>
>> Hello,
>> My name is Temuri and I'd like to ask for account for Zanata to help
>> with translation of ovirt to Georgian.
>>
>> I've done translation of zoiper, FreeCAD, part of gitlab, protonmail,
>> parts of gnome and KDE, etc etc etc.
>> In case of questions feel free to ask.
>> BR, Temuri
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RYKJ2ZFIOYA66XY3PRPXHF5Y5ZDSTKVG/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMW5EFPI4R27CNT2FKSUZ2Q7MPLSBBMT/

[ovirt-users] Cloning VM selecting part of the disks

2022-03-22 Thread Gianluca Cecchi 
Hello,
in recent versions of oVirt (eg my last 4.4.10) there is the feature to
make a clone of a running  VM.
This operation passes through a temporary VM snapshot (then automatically
deleted) and cloning of this snapshot.
Sometimes there is a need to clone a VM but only a subset of its disks is
required (eg in my case I want to retain boot disk, 20Gb, and dedicated sw
disk, 20Gb, but not data disk, that usually is big... in my case 200Gb).
In this scenario I have to go the old path where I explicitly create a
snapshot of the VM, where I can select a subset of the disks, then I clone
the snapshot and last I delete the snapshot.
Do you think it is interesting to have the option of selecting disks when
you clone a running VM and go automatic..?
If I want to open a bugzilla as RFE, what components and options I have to
select?

Thanks,
Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CO34RAB2EOA3IYA4LDSLTZYY4MR4UQJA/

[ovirt-users] Unable to deploy ovirt 4.4 on alma 8.5

2022-03-22 Thread Richa Gupta 
Hi Team,
While installing ovirt 4.4 on alma Linux 8.5 we are facing following issue:

[ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package]
[ ERROR ] fatal: [localhost -> 192.168.222.56]: FAILED! => {"changed": false, 
"msg": "Failed to download metadata for repo 'ovirt-4.4': Cannot download 
repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 
1, "results": []}

Using repo as following:
[ovirt-4.4]
name=Latest oVirt 4.4 Release
#baseurl=https://resources.ovirt.org/pub/ovirt-4.4/rpm/el$releasever/
mirrorlist=https://mirrorlist.ovirt.org/mirrorlist-ovirt-4.4-el$releasever
enabled=1
countme=1
fastestmirror=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.4

Can someone please help in resolving this issue?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NF4GMROYDB42H6FMTD5OV5UHTEUPEUMX/