Attaching LVM logical volume to VM
by th3penguinwhisperer＠gmail.com
Hi,
I've just migrated from Libvirt/kvm to oVirt.
In libvirt I had a VM that had an LVM logical volume that was attached to a guest as a disk.
However in oVirt I can't immediately find such a capability. I understand that this would "pin" my VM to this host but that's perfectly fine.
Any pointers how this can be done?
Thanks in advance!
3 years
- 3
- 4
Hosted Engine Deploy Failure
by Gary Pedretty
Keep getting the following error on a new clean install of the Hosted Engine on CentOS Stream. This is latest updated CentOS Stream (version 8 not 9) and latest version of ovirt
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
Attempted via the Cockpit Web Interface Deployment Wizard.
Any ideas? Some really old references to this issue a few years ago, but nothing recent.
Gary
Deployment Log Snippet.
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials]
[ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user 'admin@internal': Unable to log in because the user account is disabled or locked. Contact the system administrator..
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user 'admin@internal': Unable to log in because the user account is disabled or locked. Contact the system administrator.."}
3 years
- 2
- 2
Re: Creating VMs from templates with their own disks
by Sina Owolabi
And Paul
when I try to add host_name, I get this error:
TASK [Creates new virtual machine]
****************************************************************************************************************************************************
fatal: [ovirt.ovirt.trove.internal]: FAILED! => {"changed": false,
"msg": "Unsupported parameters for (ovirt.ovirt.ovirt_vm) module:
host_name, regenerate_ssh_keys Supported parameter
affinity_group_mappings, affinity_label_mappings,
allow_partial_import, auth, ballooning_enabled, bios_type,
boot_devices, boot_menu, cd_iso, clone, clone_permissions, cloud_init,
cl
ics, cloud_init_persist, cluster, cluster_mappings, comment,
cpu_cores, cpu_mode, cpu_pinning, cpu_shares, cpu_sockets,
cpu_threads, custom_compatibility_version, custom_emulated_mach
m_properties, delete_protected, description, disk_format, disks,
domain_mappings, exclusive, export_domain, export_ova, fetch_nested,
force, force_migrate, graphical_console, high_ava
high_availability_priority, host, host_devices, id, initrd_path,
instance_type, io_threads, kernel_params, kernel_params_persist,
kernel_path, kvm, lease, lun_mappings, memory, memor
ed, memory_max, migrate, name, nested_attributes, next_run, nics,
numa_nodes, numa_tune_mode, operating_system, placement_policy,
placement_policy_hosts, poll_interval, quota_id, reas
acs, rng_device, role_mappings, serial_console, serial_policy,
serial_policy_value, smartcard_enabled, snapshot_name, snapshot_vm,
soundcard_enabled, sso, state, stateless, storage_do
rep, template, template_version, ticket, timeout, timezone, type,
usb_support, use_latest_template_version, vmware,
vnic_profile_mappings, wait, watchdog, xen"}
On Fri, Nov 26, 2021 at 5:11 PM Staniforth, Paul
<P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hi Sina,
> I get easily confused with cloud-init but shouldn't you be setting the hostname, username, etc before the custom script?
>
> Also, you could rename the disk as a separate play in your playbook.
>
> e.g.
>
> # Change Disk Name
> - ovirt.ovirt.ovirt_disk:
> id: 00000000-0000-0000-0000-000000000000
> storage_domain: data
> name: "new_disk_name"
> vm_name: rhel7
>
>
> Regards,
> Paul S.
>
> ________________________________
> From: Sina Owolabi <notify.sina(a)gmail.com>
> Sent: 26 November 2021 15:00
> To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
> Cc: users(a)ovirt.org <users(a)ovirt.org>
> Subject: Re: [ovirt-users] Re: Creating VMs from templates with their own disks
>
>
> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
>
> Thanks Paul.
>
> I seem to be getting this by hand, but trying with ansible, I think my skills are a bit lacking.
> I can create with ansible, and it seems to work well, except for the fact that the new vm is
> created with the hostname of the vm from which the template was made.
> The disk is also named by the template.
> My ansiblle yaml is below and I'm pretty sure its wrong (especially where it needs to use cloud-init to inject the correct hostname, and the other prepping I would like to add).
> Please can you help correct me?
>
> ---
> - hosts: ovirt.ovirt.mydom.internal
> tasks:
> - import_tasks: ovirt_auth.yml
>
> - name: Creates new virtual machine
> ovirt.ovirt.ovirt_vm:
> auth: "{{ ovirt_auth }}"
> name: "{{ vm_fqdn }}"
> state: present
> clone: true
> cluster: lrg0-ovirt-cluster
> storage_domain: lrg0-ovirt-mydom-internal-Local
> memory: 16GiB
> cpu_cores: 8
> cpu_sockets: 2
> template: template-test00-centos8
> type: server
> operating_system: other_linux
> sso: true
> disk_format: raw
> # disks:
> # - name: "{{ vm_fqdn }}-disk0"
> # bootable: true
> # nics:
> # - name: nic1
> # boot_protocol: dhcp
> # interface: virtio
> # profile_name: "{{ net_profile_name }}"
> graphical_console:
> protocol:
> - spice
> - vnc
> cloud_init:
> custom_script: |
> host_name: "{{ vm_fqdn }}"
> user_name: myadmin
> user_password: <password>
> write_files:
> - path: /tmp/setup.sh
> permissions: '0755'
> content: |
> #!/bin/bash
> echo "$(hostnamectl)" >> /tmp/myhostname.txt
>
> ipa-client-install --hostname=`hostname -f` \
> --mkhomedir --domain=services.mydom.internal \
> --realm=SERVICES.MYDOM.INTERNAL --no-ntp \
> --principal=admin --password=<password> \
> --enable-dns-updates --unattended
> runcmd:
> - [ /tmp/setup.sh, "{{ vm_fqdn }}" ]
>
> On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hello Sina,
>
> to use the template.
>
> Create new VM and select the template.
>
> Click the advanced options.
>
> In the boot section you can set the HD to be the first boot devices and unselect any CD.
> In the Resource Allocation section, you can set the storage allocation to clone instead of thin ( this will create a copy of the template disk), you can also set the disk alias name.
>
> you can also edit the template to make sure the HD is the first boot device.
>
> I don't know what's in your ansible yaml definition.
>
> Cloning is for copying VMs or snapshots not templates.
>
> Regards,
>
> Paul S.
> ________________________________
> From: Sina Owolabi <notify.sina(a)gmail.com>
> Sent: 24 November 2021 09:28
> To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
> Cc: users(a)ovirt.org <users(a)ovirt.org>
> Subject: Re: [ovirt-users] Re: Creating VMs from templates with their own disks
>
>
> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
>
> Hello
>
> Sorry for the late reply, work has been crazy.
>
> This doesnt seem to work as advertised, or I am still not getting it.
> Either way I would really appreciate some help and guidance.
>
> Steps I have attempted:
> 1. Create and configure VM as I want it to be (disk, partitioning, etc).
> 2. Shutdown the vm, create a template from it.
>
> Cloning manually:
> Cloning fails with this message:
> Error while executing action:
> clone00.domain.tld:
>
> Cannot add VM. One or more provided storage domains are either not in active status or of an illegal type for the requested operation.
>
> I cant modify the storage allocation, and the disk its attempting to use is the disk of the source VM.
>
> Manual template install:
> Choosing to install manually with a template requires me to add a new disk, and to boot off the CD (defined in the template) and manually set things up. This I do not wish to do, because I would rather automate.
>
> Cloning with ansible, defining the cloud-init script and using the template:
> VM is successfully created, but logging in with remote-viewer drops me into the installation process (setting up from the attached ISO). Which is also not desired.
>
> Please help me with what I am doing wrong.
> Again the goal is to have the vm setup with its own credentials.
>
>
> On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hello,
> The VMs can get created from a template otherwise the blank template is used if a particular template is used it can be thin dependent VM the VMs disks is linked to the Templates disk and it just carries the changes made in the VMs disk (this is quicker and uses less space if you a lot of disks). The other option is to create a cloned VM and this will copy the Templates disk to the VM so it's no longer dependent.
>
> In the ansible documentation look for the clone option.
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_...
>
> https://www.ovirt.org/documentation/virtual_machine_management_guide/inde...
> Virtual Machine Management Guide
> oVirt is a free open-source virtualization solution for your entire enterprise
> www.ovirt.org
> For the cloud-init does the cloud-init package need to be installed on the template image?
>
>
> Regards,
>
> Paul S.
> ________________________________
> From: notify.sina(a)gmail.com <notify.sina(a)gmail.com>
> Sent: 18 November 2021 07:34
> To: users(a)ovirt.org <users(a)ovirt.org>
> Subject: [ovirt-users] Re: Creating VMs from templates with their own disks
>
> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
>
> Im sorry, I am trying to wrap my head around this but it is difficult.
>
> I just want to be able to stand up new vms, with their own storage, similar to how I can with plain vanilla KVM, with a template or without, maybe even with a kickstart, and hopefully with ansible.
>
> Right now anytime I try to create a VM, using the template, (with ansible), it gets the template disk attached, and from the console I see the new vm is named as the vm I created the template with. Cloud init script that is meant to rename the vm, and join it to IPA, is ignored.
>
> If I create storage for the vm, before creating it, both the template storage and the new storage are attached to the vm, which is also confusing. Cloud init is also ignored.
>
> I didn't think something this straightforward would end up needing a shift in thinking about how vms are created, especially with a product that's more than likely using kvm under the hood.
>
> I would appreciate some straightforward guiding steps, if I can get them.
> Really. It's been a frustrating week.
>
>
> > On 2021-11-17 13:50, Sina Owolabi wrote:
> >
> >
> > You can create a template with no disk, then VM's created from that
> > template will also have no disk. Then add a new disk to the VM after you
> > create it. This is how the default blank template works. You can also
> > create a template with an empty disk, then every VM created will also
> > get an empty disk by default. You can always rename disks as well.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
>
>
>
> --
>
> cordially yours,
>
> Sina Owolabi
>
> +2348176469061
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
>
>
>
> --
>
> cordially yours,
>
> Sina Owolabi
>
> +2348176469061
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
--
cordially yours,
Sina Owolabi
+2348176469061
3 years
- 2
- 2
Re: Creating VMs from templates with their own disks
by Sina Owolabi
Thanks guys, not sure why the ansible isnt showing up,
Posting again:
- hosts: ovirt.ovirt.mydom.internal
tasks:
- import_tasks: ovirt_auth.yml
- name: Creates new virtual machine
ovirt.ovirt.ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ vm_fqdn }}"
state: present
clone: true
cluster: lrg0-ovirt-cluster
storage_domain: lrg0-ovirt-mydom-internal-Local
memory: 16GiB
cpu_cores: 8
cpu_sockets: 2
template: template-test00-centos8
type: server
operating_system: other_linux
sso: true
disk_format: raw
# disks:
# - name: "{{ vm_fqdn }}-disk0"
# bootable: true
# nics:
# - name: nic1
# boot_protocol: dhcp
# interface: virtio
# profile_name: "{{ net_profile_name }}"
graphical_console:
protocol:
- spice
- vnc
cloud_init:
custom_script: |
host_name: "{{ vm_fqdn }}"
user_name: myadmin
user_password: <password>
write_files:
- path: /tmp/setup.sh
permissions: '0755'
content: |
#!/bin/bash
echo "$(hostnamectl)" >> /tmp/myhostname.txt
ipa-client-install --hostname=`hostname -f` \
--mkhomedir --domain=services.mydom.internal \
--realm=SERVICES.MYDOM.INTERNAL --no-ntp \
--principal=admin --password=<password> \
--enable-dns-updates --unattended
runcmd:
- [ /tmp/setup.sh, "{{ vm_fqdn }}" ]
On Fri, Nov 26, 2021 at 5:11 PM Staniforth, Paul <
P.Staniforth(a)leedsbeckett.ac.uk> wrote:
> Hi Sina,
> I get easily confused with cloud-init but shouldn't you be
> setting the hostname, username, etc before the custom script?
>
> Also, you could rename the disk as a separate play in your playbook.
>
> e.g.
>
> # Change Disk Name- ovirt.ovirt.ovirt_disk:
> id: 00000000-0000-0000-0000-000000000000
> storage_domain: data
> name: "new_disk_name"
> vm_name: rhel7
>
>
> Regards,
> Paul S.
>
> ------------------------------
> *From:* Sina Owolabi <notify.sina(a)gmail.com>
> *Sent:* 26 November 2021 15:00
> *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
> *Cc:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* Re: [ovirt-users] Re: Creating VMs from templates with their
> own disks
>
>
> *Caution External Mail:* Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
> Thanks Paul.
>
> I seem to be getting this by hand, but trying with ansible, I think my
> skills are a bit lacking.
> I can create with ansible, and it seems to work well, except for the fact
> that the new vm is
> created with the hostname of the vm from which the template was made.
> The disk is also named by the template.
> My ansiblle yaml is below and I'm pretty sure its wrong (especially where
> it needs to use cloud-init to inject the correct hostname, and the other
> prepping I would like to add).
> Please can you help correct me?
>
> ---
> - hosts: ovirt.ovirt.mydom.internal
> tasks:
> - import_tasks: ovirt_auth.yml
>
> - name: Creates new virtual machine
> ovirt.ovirt.ovirt_vm:
> auth: "{{ ovirt_auth }}"
> name: "{{ vm_fqdn }}"
> state: present
> clone: true
> cluster: lrg0-ovirt-cluster
> storage_domain: lrg0-ovirt-mydom-internal-Local
> memory: 16GiB
> cpu_cores: 8
> cpu_sockets: 2
> template: template-test00-centos8
> type: server
> operating_system: other_linux
> sso: true
> disk_format: raw
> # disks:
> # - name: "{{ vm_fqdn }}-disk0"
> # bootable: true
> # nics:
> # - name: nic1
> # boot_protocol: dhcp
> # interface: virtio
> # profile_name: "{{ net_profile_name }}"
> graphical_console:
> protocol:
> - spice
> - vnc
> cloud_init:
> custom_script: |
> host_name: "{{ vm_fqdn }}"
> user_name: myadmin
> user_password: <password>
> write_files:
> - path: /tmp/setup.sh
> permissions: '0755'
> content: |
> #!/bin/bash
> echo "$(hostnamectl)" >> /tmp/myhostname.txt
>
> ipa-client-install --hostname=`hostname -f` \
> --mkhomedir --domain=services.mydom.internal \
> --realm=SERVICES.MYDOM.INTERNAL --no-ntp \
> --principal=admin --password=<password> \
> --enable-dns-updates --unattended
> runcmd:
> - [ /tmp/setup.sh, "{{ vm_fqdn }}" ]
>
> On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul <
> P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hello Sina,
>
> to use the template.
>
> Create new VM and select the template.
>
> Click the advanced options.
>
> In the boot section you can set the HD to be the first boot devices and
> unselect any CD.
> In the Resource Allocation section, you can set the storage allocation to
> clone instead of thin ( this will create a copy of the template disk), you
> can also set the disk alias name.
>
> you can also edit the template to make sure the HD is the first boot
> device.
>
> I don't know what's in your ansible yaml definition.
>
> Cloning is for copying VMs or snapshots not templates.
>
> Regards,
>
> Paul S.
> ------------------------------
> *From:* Sina Owolabi <notify.sina(a)gmail.com>
> *Sent:* 24 November 2021 09:28
> *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
> *Cc:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* Re: [ovirt-users] Re: Creating VMs from templates with their
> own disks
>
>
> *Caution External Mail:* Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
> Hello
>
> Sorry for the late reply, work has been crazy.
>
> This doesnt seem to work as advertised, or I am still not getting it.
> Either way I would really appreciate some help and guidance.
>
> Steps I have attempted:
> 1. Create and configure VM as I want it to be (disk, partitioning, etc).
> 2. Shutdown the vm, create a template from it.
>
> Cloning manually:
> Cloning fails with this message:
> Error while executing action:
> clone00.domain.tld:
>
> - Cannot add VM. One or more provided storage domains are either not
> in active status or of an illegal type for the requested operation.
>
> I cant modify the storage allocation, and the disk its attempting to use
> is the disk of the source VM.
>
> Manual template install:
> Choosing to install manually with a template requires me to add a new
> disk, and to boot off the CD (defined in the template) and manually set
> things up. This I do not wish to do, because I would rather automate.
>
> Cloning with ansible, defining the cloud-init script and using the
> template:
> VM is successfully created, but logging in with remote-viewer drops me
> into the installation process (setting up from the attached ISO). Which is
> also not desired.
>
> Please help me with what I am doing wrong.
> Again the goal is to have the vm setup with its own credentials.
>
>
> On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul <
> P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hello,
> The VMs can get created from a template otherwise the blank
> template is used if a particular template is used it can be thin dependent
> VM the VMs disks is linked to the Templates disk and it just carries the
> changes made in the VMs disk (this is quicker and uses less space if you a
> lot of disks). The other option is to create a cloned VM and this will copy
> the Templates disk to the VM so it's no longer dependent.
>
> In the ansible documentation look for the clone option.
>
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.an...>
>
>
> https://www.ovirt.org/documentation/virtual_machine_management_guide/inde...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> Virtual Machine Management Guide
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> oVirt is a free open-source virtualization solution for your entire
> enterprise
> www.ovirt.org
> <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ovir...>
> For the cloud-init does the cloud-init package need to be installed on the
> template image?
>
>
> Regards,
>
> Paul S.
> ------------------------------
> *From:* notify.sina(a)gmail.com <notify.sina(a)gmail.com>
> *Sent:* 18 November 2021 07:34
> *To:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* [ovirt-users] Re: Creating VMs from templates with their own
> disks
>
> Caution External Mail: Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
>
> Im sorry, I am trying to wrap my head around this but it is difficult.
>
> I just want to be able to stand up new vms, with their own storage,
> similar to how I can with plain vanilla KVM, with a template or without,
> maybe even with a kickstart, and hopefully with ansible.
>
> Right now anytime I try to create a VM, using the template, (with
> ansible), it gets the template disk attached, and from the console I see
> the new vm is named as the vm I created the template with. Cloud init
> script that is meant to rename the vm, and join it to IPA, is ignored.
>
> If I create storage for the vm, before creating it, both the template
> storage and the new storage are attached to the vm, which is also
> confusing. Cloud init is also ignored.
>
> I didn't think something this straightforward would end up needing a shift
> in thinking about how vms are created, especially with a product that's
> more than likely using kvm under the hood.
>
> I would appreciate some straightforward guiding steps, if I can get them.
> Really. It's been a frustrating week.
>
>
> > On 2021-11-17 13:50, Sina Owolabi wrote:
> >
> >
> > You can create a template with no disk, then VM's created from that
> > template will also have no disk. Then add a new disk to the VM after you
> > create it. This is how the default blank template works. You can also
> > create a template with an empty disk, then every VM created will also
> > get an empty disk by default. You can always rename disks as well.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> oVirt Code of Conduct:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> List Archives:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbe...>
>
>
>
> --
>
> cordially yours,
>
> Sina Owolabi
>
> +2348176469061
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbe...>
>
>
>
> --
>
> cordially yours,
>
> Sina Owolabi
>
> +2348176469061
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
>
>
--
cordially yours,
Sina Owolabi
+2348176469061
3 years
- 1
- 0
Re: Creating VMs from templates with their own disks
by Sina Owolabi
Thanks Paul.
I seem to be getting this by hand, but trying with ansible, I think my
skills are a bit lacking.
I can create with ansible, and it seems to work well, except for the fact
that the new vm is
created with the hostname of the vm from which the template was made.
The disk is also named by the template.
My ansiblle yaml is below and I'm pretty sure its wrong (especially where
it needs to use cloud-init to inject the correct hostname, and the other
prepping I would like to add).
Please can you help correct me?
---
- hosts: ovirt.ovirt.mydom.internal
tasks:
- import_tasks: ovirt_auth.yml
- name: Creates new virtual machine
ovirt.ovirt.ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ vm_fqdn }}"
state: present
clone: true
cluster: lrg0-ovirt-cluster
storage_domain: lrg0-ovirt-mydom-internal-Local
memory: 16GiB
cpu_cores: 8
cpu_sockets: 2
template: template-test00-centos8
type: server
operating_system: other_linux
sso: true
disk_format: raw
# disks:
# - name: "{{ vm_fqdn }}-disk0"
# bootable: true
# nics:
# - name: nic1
# boot_protocol: dhcp
# interface: virtio
# profile_name: "{{ net_profile_name }}"
graphical_console:
protocol:
- spice
- vnc
cloud_init:
custom_script: |
host_name: "{{ vm_fqdn }}"
user_name: myadmin
user_password: <password>
write_files:
- path: /tmp/setup.sh
permissions: '0755'
content: |
#!/bin/bash
echo "$(hostnamectl)" >> /tmp/myhostname.txt
ipa-client-install --hostname=`hostname -f` \
--mkhomedir --domain=services.mydom.internal \
--realm=SERVICES.MYDOM.INTERNAL --no-ntp \
--principal=admin --password=<password> \
--enable-dns-updates --unattended
runcmd:
- [ /tmp/setup.sh, "{{ vm_fqdn }}" ]
On Wed, Nov 24, 2021 at 9:26 PM Staniforth, Paul <
P.Staniforth(a)leedsbeckett.ac.uk> wrote:
> Hello Sina,
>
> to use the template.
>
> Create new VM and select the template.
>
> Click the advanced options.
>
> In the boot section you can set the HD to be the first boot devices and
> unselect any CD.
> In the Resource Allocation section, you can set the storage allocation to
> clone instead of thin ( this will create a copy of the template disk), you
> can also set the disk alias name.
>
> you can also edit the template to make sure the HD is the first boot
> device.
>
> I don't know what's in your ansible yaml definition.
>
> Cloning is for copying VMs or snapshots not templates.
>
> Regards,
>
> Paul S.
> ------------------------------
> *From:* Sina Owolabi <notify.sina(a)gmail.com>
> *Sent:* 24 November 2021 09:28
> *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
> *Cc:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* Re: [ovirt-users] Re: Creating VMs from templates with their
> own disks
>
>
> *Caution External Mail:* Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
> Hello
>
> Sorry for the late reply, work has been crazy.
>
> This doesnt seem to work as advertised, or I am still not getting it.
> Either way I would really appreciate some help and guidance.
>
> Steps I have attempted:
> 1. Create and configure VM as I want it to be (disk, partitioning, etc).
> 2. Shutdown the vm, create a template from it.
>
> Cloning manually:
> Cloning fails with this message:
> Error while executing action:
> clone00.domain.tld:
>
> - Cannot add VM. One or more provided storage domains are either not
> in active status or of an illegal type for the requested operation.
>
> I cant modify the storage allocation, and the disk its attempting to use
> is the disk of the source VM.
>
> Manual template install:
> Choosing to install manually with a template requires me to add a new
> disk, and to boot off the CD (defined in the template) and manually set
> things up. This I do not wish to do, because I would rather automate.
>
> Cloning with ansible, defining the cloud-init script and using the
> template:
> VM is successfully created, but logging in with remote-viewer drops me
> into the installation process (setting up from the attached ISO). Which is
> also not desired.
>
> Please help me with what I am doing wrong.
> Again the goal is to have the vm setup with its own credentials.
>
>
> On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul <
> P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hello,
> The VMs can get created from a template otherwise the blank
> template is used if a particular template is used it can be thin dependent
> VM the VMs disks is linked to the Templates disk and it just carries the
> changes made in the VMs disk (this is quicker and uses less space if you a
> lot of disks). The other option is to create a cloned VM and this will copy
> the Templates disk to the VM so it's no longer dependent.
>
> In the ansible documentation look for the clone option.
>
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.an...>
>
>
> https://www.ovirt.org/documentation/virtual_machine_management_guide/inde...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> Virtual Machine Management Guide
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> oVirt is a free open-source virtualization solution for your entire
> enterprise
> www.ovirt.org
> <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ovir...>
> For the cloud-init does the cloud-init package need to be installed on the
> template image?
>
>
> Regards,
>
> Paul S.
> ------------------------------
> *From:* notify.sina(a)gmail.com <notify.sina(a)gmail.com>
> *Sent:* 18 November 2021 07:34
> *To:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* [ovirt-users] Re: Creating VMs from templates with their own
> disks
>
> Caution External Mail: Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
>
> Im sorry, I am trying to wrap my head around this but it is difficult.
>
> I just want to be able to stand up new vms, with their own storage,
> similar to how I can with plain vanilla KVM, with a template or without,
> maybe even with a kickstart, and hopefully with ansible.
>
> Right now anytime I try to create a VM, using the template, (with
> ansible), it gets the template disk attached, and from the console I see
> the new vm is named as the vm I created the template with. Cloud init
> script that is meant to rename the vm, and join it to IPA, is ignored.
>
> If I create storage for the vm, before creating it, both the template
> storage and the new storage are attached to the vm, which is also
> confusing. Cloud init is also ignored.
>
> I didn't think something this straightforward would end up needing a shift
> in thinking about how vms are created, especially with a product that's
> more than likely using kvm under the hood.
>
> I would appreciate some straightforward guiding steps, if I can get them.
> Really. It's been a frustrating week.
>
>
> > On 2021-11-17 13:50, Sina Owolabi wrote:
> >
> >
> > You can create a template with no disk, then VM's created from that
> > template will also have no disk. Then add a new disk to the VM after you
> > create it. This is how the default blank template works. You can also
> > create a template with an empty disk, then every VM created will also
> > get an empty disk by default. You can always rename disks as well.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> oVirt Code of Conduct:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
> List Archives:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbe...>
>
>
>
> --
>
> cordially yours,
>
> Sina Owolabi
>
> +2348176469061
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
>
>
--
cordially yours,
Sina Owolabi
+2348176469061
3 years
- 3
- 2
Re: How to debug "Non Operational" host
by Strahil Nikolov
So, it's hard to follow the chain but so far I saw 'gluster volume heal info' showing '-' for 2 out of 3 hosts.
Can you provide the following from all nodes:
gluster pool listgluster peer statusgluster volume listfor i in $(gluster volume list); do gluster volume heal $i info summary; done
Also, it's safe to restart the 'glusterd.service' via 'systemctl restart glusterd.service'.
Note: restart glusterd one node at a time
Best Regards,Strahil Nikolov
On Wed, Nov 24, 2021 at 23:47, Staniforth, Paul<P.Staniforth(a)leedsbeckett.ac.uk> wrote: #yiv9281492485 P {margin-top:0;margin-bottom:0;}
That's where the ! mark would show any detected issues.It's always safer to restart when in maintenance mode.
the unsynched entries won't heal without the endpoints connected.
Have you managed to get the vmstore mounted on ovirt1?
Regard,
Paul S.
From: Gervais de Montbrun <gervais(a)demontbrun.com>
Sent: 24 November 2021 21:06
To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
Cc: users(a)ovirt.org <users(a)ovirt.org>
Subject: Re: [ovirt-users] How to debug "Non Operational" host
Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Hi Paul (and anyone else who wants to chime in),
By "host's section of webadmin," do you mean here?
If so, then there is no indication that gluster is not working properly (even if I take it out of maintenance mode and it is showing non-operational).
re: "gluster volume heal vmstore info summary"This is what I see:ovirt1:
[root(a)ovirt1.dgi ~]# gluster volume heal vmstore info summary
Brick ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Connected
Total Number of entries: 27
Number of entries in heal pending: 27
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
ovirt2:
[root(a)ovirt2.dgi ~]# gluster volume heal vmstore info summary
Brick ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Connected
Total Number of entries: 46
Number of entries in heal pending: 46
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
ovirt3:
[root(a)ovirt3.dgi ~]# gluster volume heal vmstore info summary
Brick ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Connected
Total Number of entries: 46
Number of entries in heal pending: 46
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing:
Forgive me for pasting all this in. My experience with gluster has been installing it as part of my hypervised ovirt install. It's generally just worked ok without any intervention.
I see similar things for the engine brick also. Example:ovirt2:
[root(a)ovirt2.dgi ~]# gluster volume heal engine info summary
Brick ovirt1-storage.dgi:/gluster_bricks/engine/engine
Status: Connected
Total Number of entries: 1
Number of entries in heal pending: 1
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/engine/engine
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/engine/engine
Status: Connected
Total Number of entries: 1
Number of entries in heal pending: 1
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Is it safe to restart glusterd on all the servers? So far, I only did a restart on ovirt1 as it was in maintenance mode anyway.
Cheers,
Gervais
On Nov 24, 2021, at 4:44 PM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
Hi Gervais,
The other mounts are the storage domains, as ovirt1 only has 1 storage domain mounted this is probably why the host is showing as non-operational.
In the host's section of webadmin does it indicate any gluster issues? sometimes it detects these and gives you the option to restart gluster in the general tab of the host.
Also, on any of the hosts to check all the gluster nodes are connected you can run
"gluster volume heal vmstore info summary"
then you can manually restart the glusterd service.
e.g. "systemctl restart glusterd.service"
Regards,
Paul S.
From: Gervais de Montbrun <gervais(a)demontbrun.com>
Sent: 24 November 2021 18:15
To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
Cc: users@ovirt.org <users(a)ovirt.org>
Subject: Re: [ovirt-users] How to debug "Non Operational" host Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.Hi Paul.
I've updated the /etc/hosts file on the engine and restarted the hosted-engine. It seems that the "Could not associate brick" errors have stopped. Thank you!No change in my issue though ☹️.
It looks like Glusterd is starting up OK. I did force start the bricks on ovirt1. [root(a)ovirt1.dgi ~]# systemctl status glusterd● glusterd.service - GlusterFS, a clustered file-system server Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/glusterd.service.d └─99-cpu.conf Active: active (running) since Wed 2021-11-24 16:19:25 UTC; 1h 42min ago Docs: man:glusterd(8) Process: 2321 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2354 (glusterd) Tasks: 92 (limit: 1648201) Memory: 63.7G CPU: 1h 17min 42.666s CGroup: /glusterfs.slice/glusterd.service ├─2354 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO ├─3247 /usr/sbin/glusterfsd -s ovirt1-storage.dgi --volfile-id vmstore.ovirt1-storage.dgi.gluster_bricks-vmstore-vmstore -p /var/run/gluster/vols/vmstore/ovirt1-storage.dgi-gluster_bricks-vmstore-vmstore.pid -S /var/run/gluster/fb93ffff591764c8.socket --brick-name /gluster_bricks/vmstore/vmstore -l /var/log/glusterfs/bricks/gluster_b> ├─3275 /usr/sbin/glusterfsd -s ovirt1-storage.dgi --volfile-id engine.ovirt1-storage.dgi.gluster_bricks-engine-engine -p /var/run/gluster/vols/engine/ovirt1-storage.dgi-gluster_bricks-engine-engine.pid -S /var/run/gluster/66ebd47080b528d1.socket --brick-name /gluster_bricks/engine/engine -l /var/log/glusterfs/bricks/gluster_bricks-en> └─3287 /usr/sbin/glusterfs -s localhost --volfile-id shd/engine -p /var/run/gluster/shd/engine/engine-shd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/gluster/c9b8692f3e532562.socket --xlator-option *replicate*.node-uuid=fdf2cf13-c2c5-4afa-8d73-76c50c69122a --process-name glustershd --client-pid=-6
Nov 24 16:19:22 ovirt1.dgi systemd[1]: Starting GlusterFS, a clustered file-system server...Nov 24 16:19:25 ovirt1.dgi systemd[1]: Started GlusterFS, a clustered file-system server.Nov 24 16:19:28 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:28.909836] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume engine. Stopping local bricks.Nov 24 16:19:28 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:28.910745] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume vmstore. Stopping local bricks.Nov 24 16:19:31 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:31.925206] C [MSGID: 106003] [glusterd-server-quorum.c:348:glusterd_do_volume_quorum_action] 0-management: Server quorum regained for volume engine. Starting local bricks.Nov 24 16:19:31 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:31.938507] C [MSGID: 106003] [glusterd-server-quorum.c:348:glusterd_do_volume_quorum_action] 0-management: Server quorum regained for volume vmstore. Starting local bricks.
The bricks are showing all green at least in the UI, but they never seem to catch up and not show any unsynced entries:<PastedGraphic-5.png>
As for mounting the bricks, they are mounting based on what is in /etc/fstab.[root(a)ovirt1.dgi ~]# cat /etc/fstab ## /etc/fstab# Created by anaconda on Wed Feb 17 20:17:28 2021## Accessible filesystems, by reference, are maintained under '/dev/disk/'.# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.## After editing this file, run 'systemctl daemon-reload' to update systemd# units generated from this file.#/dev/onn/ovirt-node-ng-4.4.9-0.20211026.0+1 / xfs defaults,discard 0 0UUID=07e9dfea-9710-483d-bc63-aea7dbb5801d /boot xfs defaults 0 0/dev/mapper/onn-home /home xfs defaults,discard 0 0/dev/mapper/onn-tmp /tmp xfs defaults,discard 0 0/dev/mapper/onn-var /var xfs defaults,discard 0 0/dev/mapper/onn-var_log /var/log xfs defaults,discard 0 0/dev/mapper/onn-var_log_audit /var/log/audit xfs defaults,discard 0 0/dev/mapper/onn-swap none swap defaults 0 0UUID=4e2c88e4-2bae-4b41-bb62-631820435845 /gluster_bricks/engine xfs inode64,noatime,nodiratime 0 0UUID=ad938b6e-44d2-492a-a313-c4d0c0608e09 /gluster_bricks/vmstore xfs inode64,noatime,nodiratime 0 0
[root(a)ovirt1.dgi ~]# mount |grep gluster_bricks/dev/mapper/gluster_vg_sdb-gluster_lv_engine on /gluster_bricks/engine type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=3072,noquota)/dev/mapper/gluster_vg_sdb-gluster_lv_vmstore on /gluster_bricks/vmstore type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=3072,noquota)
What does this "extra" mount?[root(a)ovirt1.dgi ~]# mount | grep storageovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
I've noticed that on my working servers, I see this output:[root@ovirt2.dgi ~]# mount | grep storageovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)ovirt1-storage.dgi:/vmstore on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
There is obviously something not mounting properly on ovirt1. I don't see how this can be a network issue as the storage for the hosted engine is working ok.
I truly appreciate the help. Any other ideas or logs/places to check?
Cheers,
Gervais
On Nov 24, 2021, at 4:03 AM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
Hi Gervais,
The engine doesn't need to be able to ping the IP address, just needs to know what it is so adding them to the /etc/hosts file should work.
Also, I would check ovirt1, is it mounting the brick, what does "systemctl status glusterd" show, what are the logs in /var/log/gluster ?
Regards,
Paul S.
From: Gervais de Montbrun <gervais(a)demontbrun.com>
Sent: 24 November 2021 01:16
To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
Cc: Vojtech Juranek <vjuranek(a)redhat.com>; users(a)ovirt.org <users(a)ovirt.org>
Subject: Re: [ovirt-users] How to debug "Non Operational" host Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.Hi Paul,
I don't quite get what you mean by this:
assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses
The storage network is on 10GB network cards and plugged into a stand-alone switch. The hosted-engine is not on the same network at all and can not ping the IP's associated with those cards. Are you saying that it needs access to that network, or that is needs to be able to resolve the IP's. I can add them to the /etc/hosts file on the ovirt-engine or do I need to reconfigure my setup? It was working as it currently configured before applying the update.
I have no idea why the ovirt1 server is not showing up with the fqdn. I set up all the servers the same way. It's been like that since I set things up. I have looked for where this might be corrected, but can't find it. Ideas?
The yellow bricks... I can force start them (and I have in the past), but now it turns green for a few minutes and then returns to red.
Cheers,
Gervais
On Nov 23, 2021, at 12:57 PM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
Hello Gervais,
is the brick mounted on ovirt1 ? can you mount it using the settings in /etc/fstab ?
The hostname is not using a FQDN for ovirt1
assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addressesovirt1-storage.dgi
ovirt2-storage.dgi
ovirt3-storage.dgi
So that it can assign them to the correct network.
When the volume is showing yellow you can force restart them again from the GUI.
Regards,
Paul S.
From: Gervais de Montbrun <gervais(a)demontbrun.com>
Sent: 23 November 2021 13:42
To: Vojtech Juranek <vjuranek(a)redhat.com>
Cc: users@ovirt.org <users(a)ovirt.org>
Subject: [ovirt-users] Re: How to debug "Non Operational" host Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Hi Vojta,
Thanks for the help.
I tried to activate my server this morning and captured the logs from vdsm.log and engine.log. They are attached.
Something went awry with my gluster (I think) as it is showing that the bricks on the affected server (ovirt1) are not mounted:
<PastedGraphic-2.png>
<PastedGraphic-3.png>
<PastedGraphic-4.png>
The networking looks fine.
Cheers,
Gervais
> On Nov 23, 2021, at 3:37 AM, Vojtech Juranek <vjuranek(a)redhat.com> wrote:
>
> On Tuesday, 23 November 2021 03:36:07 CET Gervais de Montbrun wrote:
>> Hi Folks,
>>
>> I did a minor upgrade on the first host in my cluster and now it is
>> reporting "Non Operational"
>>
>> This is what yum showed as updatable. However, I did the update through the
>> ovirt-engine web interface.
>>
>> ovirt-node-ng-image-update.noarch
>> 4.4.9-1.el8
>> ovirt-4.4 Obsoleting Packages
>> ovirt-node-ng-image-update.noarch
>> 4.4.9-1.el8
>> ovirt-4.4 ovirt-node-ng-image-update.noarch
>> 4.4.8.3-1.el8
>> @System ovirt-node-ng-image-update.noarch
>> 4.4.9-1.el8
>> ovirt-4.4
>> ovirt-node-ng-image-update-placeholder.noarch
>> 4.4.8.3-1.el8
>> @System
>>
>> How do I start to debug this issue?
>
> Check engine log in /var/log/ovirt-engine/engine.log on the machine where
> engine runs
>
>>
>>
>> Also, it looks like the vmstore brick is not mounting on that host. I only
>> see the engine mounted.
>
>
> Could you also attach relevant part of vdsm log (/var/log/vdsm/vdsm.log) from
> the machine where mount failed? You should see some mount related error there.
> This could be also a reason why hosts become non-operational.
>
> Thanks
> Vojta
>
>> Broken server:
>> root(a)ovirt1.dgi log]# mount | grep storage
>> ovirt1-storage.dgi:/engine on
>> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>> fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> 131072) Working server:
>> [root(a)ovirt2.dgi ~]# mount | grep storage
>> ovirt1-storage.dgi:/engine on
>> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>> fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> 131072) ovirt1-storage.dgi:/vmstore on
>> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type
>> fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> 131072)
>>
>>
>> I tried putting the server into maintenance mode and running a reinstall on
>> it. No change. I'de really appreciate some help sorting this our.
>>
>> Cheers,
>> Gervais
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/S...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/A...
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/4...
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/H...
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/F...
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/OZSTLXDSHK6...
3 years
- 2
- 2
About the SSL Certificates
by Jorge Visentini
Hi guys!
I read and read, and read more about the SSL Certificates on the oVirt and
Red Hat site, but I have a little fear of changing my Engine.
1 - What happens if the certificates expire?
2 - The certificates are updated if I run the engine-setup again?
3 - What have I done to change the CA and the other certificates?
Cheers!
--
Att,
Jorge Visentini
+55 55 98432-9868
3 years
- 1
- 0
Re: How to debug "Non Operational" host
by Gervais de Montbrun
Hi Paul (and anyone else who wants to chime in),
By "host's section of webadmin," do you mean here?
If so, then there is no indication that gluster is not working properly (even if I take it out of maintenance mode and it is showing non-operational).
re: "gluster volume heal vmstore info summary"
This is what I see:
ovirt1:
[root(a)ovirt1.dgi ~]# gluster volume heal vmstore info summary
Brick ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Connected
Total Number of entries: 27
Number of entries in heal pending: 27
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
ovirt2:
[root(a)ovirt2.dgi ~]# gluster volume heal vmstore info summary
Brick ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Connected
Total Number of entries: 46
Number of entries in heal pending: 46
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
ovirt3:
[root(a)ovirt3.dgi ~]# gluster volume heal vmstore info summary
Brick ovirt1-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Connected
Total Number of entries: 46
Number of entries in heal pending: 46
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/vmstore/vmstore
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing:
Forgive me for pasting all this in. My experience with gluster has been installing it as part of my hypervised ovirt install. It's generally just worked ok without any intervention.
I see similar things for the engine brick also. Example:
ovirt2:
[root(a)ovirt2.dgi ~]# gluster volume heal engine info summary
Brick ovirt1-storage.dgi:/gluster_bricks/engine/engine
Status: Connected
Total Number of entries: 1
Number of entries in heal pending: 1
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Brick ovirt2-storage.dgi:/gluster_bricks/engine/engine
Status: Transport endpoint is not connected
Total Number of entries: -
Number of entries in heal pending: -
Number of entries in split-brain: -
Number of entries possibly healing: -
Brick ovirt3-storage.dgi:/gluster_bricks/engine/engine
Status: Connected
Total Number of entries: 1
Number of entries in heal pending: 1
Number of entries in split-brain: 0
Number of entries possibly healing: 0
Is it safe to restart glusterd on all the servers? So far, I only did a restart on ovirt1 as it was in maintenance mode anyway.
Cheers,
Gervais
> On Nov 24, 2021, at 4:44 PM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
> Hi Gervais,
>
> The other mounts are the storage domains, as ovirt1 only has 1 storage domain mounted this is probably why the host is showing as non-operational.
>
> In the host's section of webadmin does it indicate any gluster issues? sometimes it detects these and gives you the option to restart gluster in the general tab of the host.
>
> Also, on any of the hosts to check all the gluster nodes are connected you can run
>
> "gluster volume heal vmstore info summary"
>
> then you can manually restart the glusterd service.
>
> e.g. "systemctl restart glusterd.service"
>
> Regards,
>
> Paul S.
> From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>
> Sent: 24 November 2021 18:15
> To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>>
> Cc: users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] How to debug "Non Operational" host
>
> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
> Hi Paul.
>
> I've updated the /etc/hosts file on the engine and restarted the hosted-engine. It seems that the "Could not associate brick" errors have stopped. Thank you!
> No change in my issue though ☹️.
>
> It looks like Glusterd is starting up OK. I did force start the bricks on ovirt1.
> [root@ <mailto:root@ovirt1.dgi>ovirt1.dgi <mailto:root@ovirt1.dgi> ~]# systemctl status glusterd
> ● glusterd.service - GlusterFS, a clustered file-system server
> Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled)
> Drop-In: /etc/systemd/system/glusterd.service.d
> └─99-cpu.conf
> Active: active (running) since Wed 2021-11-24 16:19:25 UTC; 1h 42min ago
> Docs: man:glusterd(8)
> Process: 2321 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, status=0/SUCCESS)
> Main PID: 2354 (glusterd)
> Tasks: 92 (limit: 1648201)
> Memory: 63.7G
> CPU: 1h 17min 42.666s
> CGroup: /glusterfs.slice/glusterd.service
> ├─2354 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
> ├─3247 /usr/sbin/glusterfsd -s ovirt1-storage.dgi --volfile-id vmstore.ovirt1-storage.dgi.gluster_bricks-vmstore-vmstore -p /var/run/gluster/vols/vmstore/ovirt1-storage.dgi-gluster_bricks-vmstore-vmstore.pid -S /var/run/gluster/fb93ffff591764c8.socket --brick-name /gluster_bricks/vmstore/vmstore -l /var/log/glusterfs/bricks/gluster_b>
> ├─3275 /usr/sbin/glusterfsd -s ovirt1-storage.dgi --volfile-id engine.ovirt1-storage.dgi.gluster_bricks-engine-engine -p /var/run/gluster/vols/engine/ovirt1-storage.dgi-gluster_bricks-engine-engine.pid -S /var/run/gluster/66ebd47080b528d1.socket --brick-name /gluster_bricks/engine/engine -l /var/log/glusterfs/bricks/gluster_bricks-en>
> └─3287 /usr/sbin/glusterfs -s localhost --volfile-id shd/engine -p /var/run/gluster/shd/engine/engine-shd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/gluster/c9b8692f3e532562.socket --xlator-option *replicate*.node-uuid=fdf2cf13-c2c5-4afa-8d73-76c50c69122a --process-name glustershd --client-pid=-6
>
> Nov 24 16:19:22 ovirt1.dgi systemd[1]: Starting GlusterFS, a clustered file-system server...
> Nov 24 16:19:25 ovirt1.dgi systemd[1]: Started GlusterFS, a clustered file-system server.
> Nov 24 16:19:28 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:28.909836] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume engine. Stopping local bricks.
> Nov 24 16:19:28 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:28.910745] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume vmstore. Stopping local bricks.
> Nov 24 16:19:31 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:31.925206] C [MSGID: 106003] [glusterd-server-quorum.c:348:glusterd_do_volume_quorum_action] 0-management: Server quorum regained for volume engine. Starting local bricks.
> Nov 24 16:19:31 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:31.938507] C [MSGID: 106003] [glusterd-server-quorum.c:348:glusterd_do_volume_quorum_action] 0-management: Server quorum regained for volume vmstore. Starting local bricks.
>
> The bricks are showing all green at least in the UI, but they never seem to catch up and not show any unsynced entries:
> <PastedGraphic-5.png>
>
> As for mounting the bricks, they are mounting based on what is in /etc/fstab.
> [root@ <mailto:root@ovirt1.dgi>ovirt1.dgi <mailto:root@ovirt1.dgi> ~]# cat /etc/fstab
> #
> # /etc/fstab
> # Created by anaconda on Wed Feb 17 20:17:28 2021
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk/'.
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
> #
> # After editing this file, run 'systemctl daemon-reload' to update systemd
> # units generated from this file.
> #
> /dev/onn/ovirt-node-ng-4.4.9-0.20211026.0+1 / xfs defaults,discard 0 0
> UUID=07e9dfea-9710-483d-bc63-aea7dbb5801d /boot xfs defaults 0 0
> /dev/mapper/onn-home /home xfs defaults,discard 0 0
> /dev/mapper/onn-tmp /tmp xfs defaults,discard 0 0
> /dev/mapper/onn-var /var xfs defaults,discard 0 0
> /dev/mapper/onn-var_log /var/log xfs defaults,discard 0 0
> /dev/mapper/onn-var_log_audit /var/log/audit xfs defaults,discard 0 0
> /dev/mapper/onn-swap none swap defaults 0 0
> UUID=4e2c88e4-2bae-4b41-bb62-631820435845 /gluster_bricks/engine xfs inode64,noatime,nodiratime 0 0
> UUID=ad938b6e-44d2-492a-a313-c4d0c0608e09 /gluster_bricks/vmstore xfs inode64,noatime,nodiratime 0 0
>
> [root@ <mailto:root@ovirt1.dgi>ovirt1.dgi <mailto:root@ovirt1.dgi> ~]# mount |grep gluster_bricks
> /dev/mapper/gluster_vg_sdb-gluster_lv_engine on /gluster_bricks/engine type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=3072,noquota)
> /dev/mapper/gluster_vg_sdb-gluster_lv_vmstore on /gluster_bricks/vmstore type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=3072,noquota)
>
> What does this "extra" mount?
> [root@ <mailto:root@ovirt1.dgi>ovirt1.dgi <mailto:root@ovirt1.dgi> ~]# mount | grep storage
> ovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
>
> I've noticed that on my working servers, I see this output:
> [root@ <mailto:root@ovirt2.dgi>ovirt2.dgi <mailto:root@ovirt2.dgi> ~]# mount | grep storage
> ovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
> ovirt1-storage.dgi:/vmstore on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
>
> There is obviously something not mounting properly on ovirt1. I don't see how this can be a network issue as the storage for the hosted engine is working ok.
>
> I truly appreciate the help. Any other ideas or logs/places to check?
>
> Cheers,
> Gervais
>
>
>
>> On Nov 24, 2021, at 4:03 AM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>> wrote:
>>
>>
>> Hi Gervais,
>>
>> The engine doesn't need to be able to ping the IP address, just needs to know what it is so adding them to the /etc/hosts file should work.
>>
>> Also, I would check ovirt1, is it mounting the brick, what does "systemctl status glusterd" show, what are the logs in /var/log/gluster ?
>>
>>
>> Regards,
>>
>> Paul S.
>> From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>
>> Sent: 24 November 2021 01:16
>> To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>>
>> Cc: Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>>; users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
>> Subject: Re: [ovirt-users] How to debug "Non Operational" host
>>
>> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
>> Hi Paul,
>>
>> I don't quite get what you mean by this:
>>
>>> assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses
>>
>>
>> The storage network is on 10GB network cards and plugged into a stand-alone switch. The hosted-engine is not on the same network at all and can not ping the IP's associated with those cards. Are you saying that it needs access to that network, or that is needs to be able to resolve the IP's. I can add them to the /etc/hosts file on the ovirt-engine or do I need to reconfigure my setup? It was working as it currently configured before applying the update.
>>
>> I have no idea why the ovirt1 server is not showing up with the fqdn. I set up all the servers the same way. It's been like that since I set things up. I have looked for where this might be corrected, but can't find it. Ideas?
>>
>> The yellow bricks... I can force start them (and I have in the past), but now it turns green for a few minutes and then returns to red.
>>
>> Cheers,
>> Gervais
>>
>>
>>
>>> On Nov 23, 2021, at 12:57 PM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>> wrote:
>>>
>>> Hello Gervais,
>>>
>>> is the brick mounted on ovirt1 ? can you mount it using the settings in /etc/fstab ?
>>>
>>> The hostname is not using a FQDN for ovirt1
>>>
>>> assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses
>>> ovirt1-storage.dgi
>>> ovirt2-storage.dgi
>>> ovirt3-storage.dgi
>>>
>>> So that it can assign them to the correct network.
>>>
>>> When the volume is showing yellow you can force restart them again from the GUI.
>>>
>>> Regards,
>>>
>>> Paul S.
>>> From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>
>>> Sent: 23 November 2021 13:42
>>> To: Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>>
>>> Cc: users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
>>> Subject: [ovirt-users] Re: How to debug "Non Operational" host
>>>
>>> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
>>>
>>> Hi Vojta,
>>>
>>> Thanks for the help.
>>>
>>> I tried to activate my server this morning and captured the logs from vdsm.log and engine.log. They are attached.
>>>
>>> Something went awry with my gluster (I think) as it is showing that the bricks on the affected server (ovirt1) are not mounted:
>>> <PastedGraphic-2.png>
>>>
>>> <PastedGraphic-3.png>
>>>
>>> <PastedGraphic-4.png>
>>>
>>>
>>> The networking looks fine.
>>>
>>> Cheers,
>>> Gervais
>>>
>>>
>>>
>>> > On Nov 23, 2021, at 3:37 AM, Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>> wrote:
>>> >
>>> > On Tuesday, 23 November 2021 03:36:07 CET Gervais de Montbrun wrote:
>>> >> Hi Folks,
>>> >>
>>> >> I did a minor upgrade on the first host in my cluster and now it is
>>> >> reporting "Non Operational"
>>> >>
>>> >> This is what yum showed as updatable. However, I did the update through the
>>> >> ovirt-engine web interface.
>>> >>
>>> >> ovirt-node-ng-image-update.noarch
>>> >> 4.4.9-1.el8
>>> >> ovirt-4.4 Obsoleting Packages
>>> >> ovirt-node-ng-image-update.noarch
>>> >> 4.4.9-1.el8
>>> >> ovirt-4.4 ovirt-node-ng-image-update.noarch
>>> >> 4.4.8.3-1.el8
>>> >> @System ovirt-node-ng-image-update.noarch
>>> >> 4.4.9-1.el8
>>> >> ovirt-4.4
>>> >> ovirt-node-ng-image-update-placeholder.noarch
>>> >> 4.4.8.3-1.el8
>>> >> @System
>>> >>
>>> >> How do I start to debug this issue?
>>> >
>>> > Check engine log in /var/log/ovirt-engine/engine.log on the machine where
>>> > engine runs
>>> >
>>> >>
>>> >>
>>> >> Also, it looks like the vmstore brick is not mounting on that host. I only
>>> >> see the engine mounted.
>>> >
>>> >
>>> > Could you also attach relevant part of vdsm log (/var/log/vdsm/vdsm.log) from
>>> > the machine where mount failed? You should see some mount related error there.
>>> > This could be also a reason why hosts become non-operational.
>>> >
>>> > Thanks
>>> > Vojta
>>> >
>>> >> Broken server:
>>> >> root(a)ovirt1.dgi <mailto:root@ovirt1.dgi> log]# mount | grep storage
>>> >> ovirt1-storage.dgi:/engine on
>>> >> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>>> >> fuse.glusterfs
>>> >> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>>> >> 131072) Working server:
>>> >> [root(a)ovirt2.dgi <mailto:root@ovirt2.dgi> ~]# mount | grep storage
>>> >> ovirt1-storage.dgi:/engine on
>>> >> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>>> >> fuse.glusterfs
>>> >> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>>> >> 131072) ovirt1-storage.dgi:/vmstore on
>>> >> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type
>>> >> fuse.glusterfs
>>> >> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>>> >> 131072)
>>> >>
>>> >>
>>> >> I tried putting the server into maintenance mode and running a reinstall on
>>> >> it. No change. I'de really appreciate some help sorting this our.
>>> >>
>>> >> Cheers,
>>> >> Gervais
>>> >
>>> > _______________________________________________
>>> > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>>> > To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>>> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>>> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/S6C7R6LUTJX... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>>>
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>>> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AWSWTXS6CEA... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>>> To view the terms under which this email is distributed, please go to:-
>>> https://leedsbeckett.ac.uk/disclaimer/email <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbe...>_______________________________________________
>>> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>>> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4YYEHIXZCSQ... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>> To view the terms under which this email is distributed, please go to:-
>> https://leedsbeckett.ac.uk/disclaimer/email <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbe...>_______________________________________________
>> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/H7SLDPRW6FJ... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email <https://leedsbeckett.ac.uk/disclaimer/email>_______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FCXTUGI2G2G... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/FCXTUGI2G2G...>
3 years
- 2
- 1
Re: How to debug "Non Operational" host
by Gervais de Montbrun
Hi Paul.
I've updated the /etc/hosts file on the engine and restarted the hosted-engine. It seems that the "Could not associate brick" errors have stopped. Thank you!
No change in my issue though ☹️.
It looks like Glusterd is starting up OK. I did force start the bricks on ovirt1.
[root(a)ovirt1.dgi ~]# systemctl status glusterd
● glusterd.service - GlusterFS, a clustered file-system server
Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/glusterd.service.d
└─99-cpu.conf
Active: active (running) since Wed 2021-11-24 16:19:25 UTC; 1h 42min ago
Docs: man:glusterd(8)
Process: 2321 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 2354 (glusterd)
Tasks: 92 (limit: 1648201)
Memory: 63.7G
CPU: 1h 17min 42.666s
CGroup: /glusterfs.slice/glusterd.service
├─2354 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
├─3247 /usr/sbin/glusterfsd -s ovirt1-storage.dgi --volfile-id vmstore.ovirt1-storage.dgi.gluster_bricks-vmstore-vmstore -p /var/run/gluster/vols/vmstore/ovirt1-storage.dgi-gluster_bricks-vmstore-vmstore.pid -S /var/run/gluster/fb93ffff591764c8.socket --brick-name /gluster_bricks/vmstore/vmstore -l /var/log/glusterfs/bricks/gluster_b>
├─3275 /usr/sbin/glusterfsd -s ovirt1-storage.dgi --volfile-id engine.ovirt1-storage.dgi.gluster_bricks-engine-engine -p /var/run/gluster/vols/engine/ovirt1-storage.dgi-gluster_bricks-engine-engine.pid -S /var/run/gluster/66ebd47080b528d1.socket --brick-name /gluster_bricks/engine/engine -l /var/log/glusterfs/bricks/gluster_bricks-en>
└─3287 /usr/sbin/glusterfs -s localhost --volfile-id shd/engine -p /var/run/gluster/shd/engine/engine-shd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/gluster/c9b8692f3e532562.socket --xlator-option *replicate*.node-uuid=fdf2cf13-c2c5-4afa-8d73-76c50c69122a --process-name glustershd --client-pid=-6
Nov 24 16:19:22 ovirt1.dgi systemd[1]: Starting GlusterFS, a clustered file-system server...
Nov 24 16:19:25 ovirt1.dgi systemd[1]: Started GlusterFS, a clustered file-system server.
Nov 24 16:19:28 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:28.909836] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume engine. Stopping local bricks.
Nov 24 16:19:28 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:28.910745] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume vmstore. Stopping local bricks.
Nov 24 16:19:31 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:31.925206] C [MSGID: 106003] [glusterd-server-quorum.c:348:glusterd_do_volume_quorum_action] 0-management: Server quorum regained for volume engine. Starting local bricks.
Nov 24 16:19:31 ovirt1.dgi glusterd[2354]: [2021-11-24 16:19:31.938507] C [MSGID: 106003] [glusterd-server-quorum.c:348:glusterd_do_volume_quorum_action] 0-management: Server quorum regained for volume vmstore. Starting local bricks.
The bricks are showing all green at least in the UI, but they never seem to catch up and not show any unsynced entries:
As for mounting the bricks, they are mounting based on what is in /etc/fstab.
[root(a)ovirt1.dgi ~]# cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Wed Feb 17 20:17:28 2021
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/onn/ovirt-node-ng-4.4.9-0.20211026.0+1 / xfs defaults,discard 0 0
UUID=07e9dfea-9710-483d-bc63-aea7dbb5801d /boot xfs defaults 0 0
/dev/mapper/onn-home /home xfs defaults,discard 0 0
/dev/mapper/onn-tmp /tmp xfs defaults,discard 0 0
/dev/mapper/onn-var /var xfs defaults,discard 0 0
/dev/mapper/onn-var_log /var/log xfs defaults,discard 0 0
/dev/mapper/onn-var_log_audit /var/log/audit xfs defaults,discard 0 0
/dev/mapper/onn-swap none swap defaults 0 0
UUID=4e2c88e4-2bae-4b41-bb62-631820435845 /gluster_bricks/engine xfs inode64,noatime,nodiratime 0 0
UUID=ad938b6e-44d2-492a-a313-c4d0c0608e09 /gluster_bricks/vmstore xfs inode64,noatime,nodiratime 0 0
[root(a)ovirt1.dgi ~]# mount |grep gluster_bricks
/dev/mapper/gluster_vg_sdb-gluster_lv_engine on /gluster_bricks/engine type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=3072,noquota)
/dev/mapper/gluster_vg_sdb-gluster_lv_vmstore on /gluster_bricks/vmstore type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=3072,noquota)
What does this "extra" mount?
[root(a)ovirt1.dgi ~]# mount | grep storage
ovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
I've noticed that on my working servers, I see this output:
[root(a)ovirt2.dgi ~]# mount | grep storage
ovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
ovirt1-storage.dgi:/vmstore on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
There is obviously something not mounting properly on ovirt1. I don't see how this can be a network issue as the storage for the hosted engine is working ok.
I truly appreciate the help. Any other ideas or logs/places to check?
Cheers,
Gervais
> On Nov 24, 2021, at 4:03 AM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote:
>
>
> Hi Gervais,
>
> The engine doesn't need to be able to ping the IP address, just needs to know what it is so adding them to the /etc/hosts file should work.
>
> Also, I would check ovirt1, is it mounting the brick, what does "systemctl status glusterd" show, what are the logs in /var/log/gluster ?
>
>
> Regards,
>
> Paul S.
> From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>
> Sent: 24 November 2021 01:16
> To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>>
> Cc: Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>>; users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] How to debug "Non Operational" host
>
> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
> Hi Paul,
>
> I don't quite get what you mean by this:
>
>> assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses
>
>
> The storage network is on 10GB network cards and plugged into a stand-alone switch. The hosted-engine is not on the same network at all and can not ping the IP's associated with those cards. Are you saying that it needs access to that network, or that is needs to be able to resolve the IP's. I can add them to the /etc/hosts file on the ovirt-engine or do I need to reconfigure my setup? It was working as it currently configured before applying the update.
>
> I have no idea why the ovirt1 server is not showing up with the fqdn. I set up all the servers the same way. It's been like that since I set things up. I have looked for where this might be corrected, but can't find it. Ideas?
>
> The yellow bricks... I can force start them (and I have in the past), but now it turns green for a few minutes and then returns to red.
>
> Cheers,
> Gervais
>
>
>
>> On Nov 23, 2021, at 12:57 PM, Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk <mailto:P.Staniforth@leedsbeckett.ac.uk>> wrote:
>>
>> Hello Gervais,
>>
>> is the brick mounted on ovirt1 ? can you mount it using the settings in /etc/fstab ?
>>
>> The hostname is not using a FQDN for ovirt1
>>
>> assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses
>> ovirt1-storage.dgi
>> ovirt2-storage.dgi
>> ovirt3-storage.dgi
>>
>> So that it can assign them to the correct network.
>>
>> When the volume is showing yellow you can force restart them again from the GUI.
>>
>> Regards,
>>
>> Paul S.
>> From: Gervais de Montbrun <gervais(a)demontbrun.com <mailto:gervais@demontbrun.com>>
>> Sent: 23 November 2021 13:42
>> To: Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>>
>> Cc: users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org <mailto:users@ovirt.org>>
>> Subject: [ovirt-users] Re: How to debug "Non Operational" host
>>
>> Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
>>
>> Hi Vojta,
>>
>> Thanks for the help.
>>
>> I tried to activate my server this morning and captured the logs from vdsm.log and engine.log. They are attached.
>>
>> Something went awry with my gluster (I think) as it is showing that the bricks on the affected server (ovirt1) are not mounted:
>> <PastedGraphic-2.png>
>>
>> <PastedGraphic-3.png>
>>
>> <PastedGraphic-4.png>
>>
>>
>> The networking looks fine.
>>
>> Cheers,
>> Gervais
>>
>>
>>
>> > On Nov 23, 2021, at 3:37 AM, Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>> wrote:
>> >
>> > On Tuesday, 23 November 2021 03:36:07 CET Gervais de Montbrun wrote:
>> >> Hi Folks,
>> >>
>> >> I did a minor upgrade on the first host in my cluster and now it is
>> >> reporting "Non Operational"
>> >>
>> >> This is what yum showed as updatable. However, I did the update through the
>> >> ovirt-engine web interface.
>> >>
>> >> ovirt-node-ng-image-update.noarch
>> >> 4.4.9-1.el8
>> >> ovirt-4.4 Obsoleting Packages
>> >> ovirt-node-ng-image-update.noarch
>> >> 4.4.9-1.el8
>> >> ovirt-4.4 ovirt-node-ng-image-update.noarch
>> >> 4.4.8.3-1.el8
>> >> @System ovirt-node-ng-image-update.noarch
>> >> 4.4.9-1.el8
>> >> ovirt-4.4
>> >> ovirt-node-ng-image-update-placeholder.noarch
>> >> 4.4.8.3-1.el8
>> >> @System
>> >>
>> >> How do I start to debug this issue?
>> >
>> > Check engine log in /var/log/ovirt-engine/engine.log on the machine where
>> > engine runs
>> >
>> >>
>> >>
>> >> Also, it looks like the vmstore brick is not mounting on that host. I only
>> >> see the engine mounted.
>> >
>> >
>> > Could you also attach relevant part of vdsm log (/var/log/vdsm/vdsm.log) from
>> > the machine where mount failed? You should see some mount related error there.
>> > This could be also a reason why hosts become non-operational.
>> >
>> > Thanks
>> > Vojta
>> >
>> >> Broken server:
>> >> root(a)ovirt1.dgi <mailto:root@ovirt1.dgi> log]# mount | grep storage
>> >> ovirt1-storage.dgi:/engine on
>> >> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>> >> fuse.glusterfs
>> >> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> >> 131072) Working server:
>> >> [root(a)ovirt2.dgi <mailto:root@ovirt2.dgi> ~]# mount | grep storage
>> >> ovirt1-storage.dgi:/engine on
>> >> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>> >> fuse.glusterfs
>> >> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> >> 131072) ovirt1-storage.dgi:/vmstore on
>> >> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type
>> >> fuse.glusterfs
>> >> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> >> 131072)
>> >>
>> >>
>> >> I tried putting the server into maintenance mode and running a reinstall on
>> >> it. No change. I'de really appreciate some help sorting this our.
>> >>
>> >> Cheers,
>> >> Gervais
>> >
>> > _______________________________________________
>> > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>> > To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/S6C7R6LUTJX... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>>
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AWSWTXS6CEA... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
>> To view the terms under which this email is distributed, please go to:-
>> https://leedsbeckett.ac.uk/disclaimer/email <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fleedsbe...>_______________________________________________
>> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
>> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4YYEHIXZCSQ... <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...>
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email <https://leedsbeckett.ac.uk/disclaimer/email>_______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/H7SLDPRW6FJ... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/H7SLDPRW6FJ...>
3 years
- 2
- 1
Re: Creating VMs from templates with their own disks
by Sina Owolabi
Hello
Sorry for the late reply, work has been crazy.
This doesnt seem to work as advertised, or I am still not getting it.
Either way I would really appreciate some help and guidance.
Steps I have attempted:
1. Create and configure VM as I want it to be (disk, partitioning, etc).
2. Shutdown the vm, create a template from it.
Cloning manually:
Cloning fails with this message:
Error while executing action:
clone00.domain.tld:
- Cannot add VM. One or more provided storage domains are either not in
active status or of an illegal type for the requested operation.
I cant modify the storage allocation, and the disk its attempting to use is
the disk of the source VM.
Manual template install:
Choosing to install manually with a template requires me to add a new disk,
and to boot off the CD (defined in the template) and manually set things
up. This I do not wish to do, because I would rather automate.
Cloning with ansible, defining the cloud-init script and using the template:
VM is successfully created, but logging in with remote-viewer drops me into
the installation process (setting up from the attached ISO). Which is also
not desired.
Please help me with what I am doing wrong.
Again the goal is to have the vm setup with its own credentials.
On Thu, Nov 18, 2021 at 9:24 AM Staniforth, Paul <
P.Staniforth(a)leedsbeckett.ac.uk> wrote:
> Hello,
> The VMs can get created from a template otherwise the blank
> template is used if a particular template is used it can be thin dependent
> VM the VMs disks is linked to the Templates disk and it just carries the
> changes made in the VMs disk (this is quicker and uses less space if you a
> lot of disks). The other option is to create a cloned VM and this will copy
> the Templates disk to the VM so it's no longer dependent.
>
> In the ansible documentation look for the clone option.
>
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_...
>
>
> https://www.ovirt.org/documentation/virtual_machine_management_guide/inde...
> Virtual Machine Management Guide
> <https://www.ovirt.org/documentation/virtual_machine_management_guide/inde...>
> oVirt is a free open-source virtualization solution for your entire
> enterprise
> www.ovirt.org
> For the cloud-init does the cloud-init package need to be installed on the
> template image?
>
>
> Regards,
>
> Paul S.
> ------------------------------
> *From:* notify.sina(a)gmail.com <notify.sina(a)gmail.com>
> *Sent:* 18 November 2021 07:34
> *To:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* [ovirt-users] Re: Creating VMs from templates with their own
> disks
>
> Caution External Mail: Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
>
> Im sorry, I am trying to wrap my head around this but it is difficult.
>
> I just want to be able to stand up new vms, with their own storage,
> similar to how I can with plain vanilla KVM, with a template or without,
> maybe even with a kickstart, and hopefully with ansible.
>
> Right now anytime I try to create a VM, using the template, (with
> ansible), it gets the template disk attached, and from the console I see
> the new vm is named as the vm I created the template with. Cloud init
> script that is meant to rename the vm, and join it to IPA, is ignored.
>
> If I create storage for the vm, before creating it, both the template
> storage and the new storage are attached to the vm, which is also
> confusing. Cloud init is also ignored.
>
> I didn't think something this straightforward would end up needing a shift
> in thinking about how vms are created, especially with a product that's
> more than likely using kvm under the hood.
>
> I would appreciate some straightforward guiding steps, if I can get them.
> Really. It's been a frustrating week.
>
>
> > On 2021-11-17 13:50, Sina Owolabi wrote:
> >
> >
> > You can create a template with no disk, then VM's created from that
> > template will also have no disk. Then add a new disk to the VM after you
> > create it. This is how the default blank template works. You can also
> > create a template with an empty disk, then every VM created will also
> > get an empty disk by default. You can always rename disks as well.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> oVirt Code of Conduct:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...
> List Archives:
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o...
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email
>
>
--
cordially yours,
Sina Owolabi
+2348176469061
3 years
- 2
- 1