Can't remove snapshot
by David Johnson
Hi all,
I patched one of my Windows VM's yesterday. I started by snapshotting the
VM, then applied the Windows update. Now that the patch has been tested, I
want to remove the snapshot. I get this message:
Error while executing action:
win-sql-2019:
- Cannot remove Snapshot. The following attached disks are in ILLEGAL
status: win-2019-tmpl_Disk1 - please remove them and try again.
Does anyone have any thoughts how to recover from this? I really don't want
to keep this snapshot hanging around.
Thanks in advance,
*David Johnson*
3 years, 5 months
oVirt 2021 online conference
by Sandro Bonazzola
It is our pleasure to invite you to the oVirt 2021 online conference. The
conference, organized by the oVirt community, will take place online on
Monday, September 6th 2021!
oVirt 2021 is a free conference for oVirt community project users and
contributors coming to a web browser near you!
There is no admission or ticket charge for this event. However, you are
required to complete a free registration. Watch
https://blogs.ovirt.org/ovirt-2021-online-conference/ for updates about
registration.
Talks, presentations and workshops will all be in English.
We encourage students and new graduates as well as professionals to submit
proposals to oVirt conferences.
The theme of oVirt 2021 online conference will be about making it easy to
contribute to the oVirt project and celebrating 10 years of oVirt.
We will be looking for talks and discussions across virtualization, and how
oVirt 4.4 can effectively solve user issues around:
- Developing for oVirt
- Integrating with oVirt
- New features
- User stories
The deadline to submit abstracts is July 25th 2021.
To submit your abstract, please click on the following link: submission form
<https://forms.gle/CeCbGmNpvPs6fC2M8>
More information are available at
https://blogs.ovirt.org/ovirt-2021-online-conference/
Thanks,
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
3 years, 5 months
[ANN] oVirt 4.4.7 Second Release Candidate is now available for testing
by Sandro Bonazzola
oVirt 4.4.7 Second Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of oVirt 4.4.7
Second Release Candidate for testing, as of June 4th, 2021.
This update is the seventh in a series of stabilization updates to the 4.4
series.
Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.
Important notes before you try it
Please note this is a pre-release build.
The oVirt Project makes no guarantees as to its suitability or usefulness.
This pre-release must not be used in production.
If you are upgrading from 4.4.1 please check previous versions release
notes about Bug 1837864
<https://bugzilla.redhat.com/show_bug.cgi?id=1837864>
Installation instructions
For installation instructions and additional information please refer to:
https://ovirt.org/documentation/
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.4 or similar
* CentOS Stream 8
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 8.4 or similar
* CentOS Stream 8
* oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only)
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
Notes:
- oVirt Appliance is already available based on CentOS Stream 8
- oVirt Node NG is already available based on CentOS Stream 8
Additional Resources:
* Read more about the oVirt 4.4.7 release highlights:
http://www.ovirt.org/release/4.4.7/
* Get more oVirt project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.4.7/
[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
3 years, 5 months
[oVirt 4.4.6] Offline deployment of hosted engine
by sharma.ishan＠fujitsu.com
Hello,
I am trying to test oVirt node 4.4.6 inside my company’s network which needs proxy setting for internet access.
Is there any possibility to deploy host engine without any internet access? i.e. Is offline deployment of hosted engine possible?
I have added the following line at the end of the file /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml
environment:
https_proxy: "http://<proxy_host>:<proxy_port>"
http_proxy: "http://<proxy_host>:<proxy_port>"
But it gives error in the process of “hosted-engine --deploy”. I am not sure if this a typical issue in my company’s network but, it would be great if there is any offline installation method (without accessing internet repository).
I have also tried to use “hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true” but, it is not helping me at all.
With regards
**********************************************
Ishan Nath Sharma
Technical Computing Solutions Unit
Fujitsu Limited
E-mail: sharma.ishan(a)jp.fujitsu.com<mailto:sharma.ishan@jp.fujitsu.com>
http://www.fujitsu.com
**********************************************
3 years, 5 months
Fwd: Can't remove snapshot
by Roman Bednar
Ok, sounds good. Forgot to include the mailing list, doing it now.
---------- Forwarded message ---------
From: David Johnson <djohnson(a)maxistechnology.com>
Date: Thu, Jun 3, 2021 at 11:17 AM
Subject: Re: [ovirt-users] Can't remove snapshot
To: Roman Bednar <rbednar(a)redhat.com>
Thanks, I'll check it out.
Since my business is replatforming and transforming databases, digging
around the DB is something I will be very comfortable with.
I won't be able to do anything until Friday. I'll let you know how it goes.
David Johnson
On Thu, Jun 3, 2021, 2:40 AM Roman Bednar <rbednar(a)redhat.com> wrote:
> Digging a bit further I found this is a known issue. A discrepancy can
> occur between vdsm and engine db when removing a snapshot.
>
> It's been already discussed [1] and a bug is filed [2]. In the discussion
> you can find a workaround which is manual removal of the snapshot.
>
> Don't forget to backup the engine database by running 'engine-backup' tool
> on the engine node before doing any changes.
> Restore requires a bit more options and can be done like this:
>
> # engine-backup
> --file=/var/lib/ovirt-engine-backup/ovirt-engine-backup-20210602055605.backup
> --mode=restore --provision-all-databases
>
> To check if the discrepancy occurred you can check the db and compare that
> to what vdsm sees (which is a source of truth).
>
> The example below shows a consistent setup from my env with one snapshot,
> if there is anything extra in your env in the
> db it should be removed and the parent id changed accordingly [3].
>
> image_group_id (db) == image (vdsm)
> image_guid (db) == logical volume on host (vdsm)
>
> Engine node:
>
> # su - postgres
> # psql
> postgres=# \c engine
> engine=# select image_guid, image_group_id, parentid from images where
> image_group_id = 'e75318bf-c563-4d66-99e4-63645736a418';
> image_guid | image_group_id
> | parentid
>
> --------------------------------------+--------------------------------------+--------------------------------------
> 1955f6de-658a-43c3-969b-79db9b4bf14c |
> e75318bf-c563-4d66-99e4-63645736a418 | 00000000-0000-0000-0000-000000000000
> d6662661-eb87-4c01-a204-477919e65221 |
> e75318bf-c563-4d66-99e4-63645736a418 | 1955f6de-658a-43c3-969b-79db9b4bf14c
>
>
> Host node:
>
> # vdsm-tool dump-volume-chains <STORAGE_DOMAIN_ID>
>
> Images volume chains (base volume first)
>
> image: e75318bf-c563-4d66-99e4-63645736a418
>
> - 1955f6de-658a-43c3-969b-79db9b4bf14c
> status: OK, voltype: INTERNAL, format: RAW, legality:
> LEGAL, type: PREALLOCATED, capacity: 5368709120, truesize: 5368709120
>
> - d6662661-eb87-4c01-a204-477919e65221
> status: OK, voltype: LEAF, format: COW, legality: LEGAL,
> type: SPARSE, capacity: 5368709120, truesize: 3221225472
> ...
>
>
> I hope this helps a bit and if you need further assistance let us know,
> it's not very convenient to change the db
> manually like this but a fix should be on the way :)
>
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1948599
> [2]
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/7ZU7NWHBW3B2...
> [3]
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D2HKS2RFMNK...
>
> On Tue, Jun 1, 2021 at 8:19 PM David Johnson <djohnson(a)maxistechnology.com>
> wrote:
>
>> Yes, I have the same error on the second try.
>>
>> You can see it happening in the engine log starting at 2021-05-31 07:49.
>>
>>
>> *David Johnson*
>> *Director of Development, Maxis Technology*
>> 844.696.2947 ext 702 (o) | 479.531.3590 (c)
>> <https://www.linkedin.com/in/pojoguy/>
>> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson...>
>> <https://maxistechnology.com/>
>>
>> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>
>>
>>
>> On Tue, Jun 1, 2021 at 7:48 AM Roman Bednar <rbednar(a)redhat.com> wrote:
>>
>>> Hi David,
>>>
>>> awesome, thanks for the reply. Looking at the logs there does not seem
>>> anything suspicious on vdsm side and as you said the snapshots are really
>>> gone when looking from vdsm. I tried to reproduce without much success but
>>> it looks like a problem on the engine side.
>>>
>>> Did you get the same error saying that the disks are illegal on the
>>> second try? There should be more in the engine log so try checking it as
>>> well to see if this is really on the engine side.
>>>
>>> It would be great to have a reproducer for this and file the bug so we
>>> can track this and provide a fix.
>>>
>>>
>>> -Roman
>>>
>>>
>>>
>>> On Mon, May 31, 2021 at 3:20 PM David Johnson <
>>> djohnson(a)maxistechnology.com> wrote:
>>>
>>>> Hi Roman,
>>>>
>>>> Thank you for your assistance.
>>>>
>>>> I found another snapshot that needed collapsing, and deleted that.
>>>> These logs include that execution.
>>>>
>>>> Prior to the execution, the vdsm-dump listed snapshot volumes.
>>>> Post-execution, the snapshot volumes were absent. That suggests to me that
>>>> the snapshot was actually removed, but Ovirt is confused.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *David Johnson*
>>>> *Director of Development, Maxis Technology*
>>>> 844.696.2947 ext 702 (o) | 479.531.3590 (c)
>>>> <https://www.linkedin.com/in/pojoguy/>
>>>> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson...>
>>>> <https://maxistechnology.com/>
>>>>
>>>> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>
>>>>
>>>>
>>>> On Mon, May 31, 2021 at 5:54 AM Roman Bednar <rbednar(a)redhat.com>
>>>> wrote:
>>>>
>>>>> Hello David,
>>>>>
>>>>> there's quite a few reasons a volume could be marked as illegal, e.g.
>>>>> failed operation that left the volume in this state. This is done in vdsm
>>>>> so please provide a vdsm log on the host running the VM so we can check
>>>>> exactly what went wrong. Also the state of the storage domain could be
>>>>> helpful to see what volumes are present and marked illegal, you can get the
>>>>> information by running:
>>>>>
>>>>> # vdsm-client StorageDomain dump sd_id=<SD_ID>
>>>>>
>>>>>
>>>>>
>>>>> -Roman
>>>>>
>>>>> On Fri, May 28, 2021 at 6:10 PM David Johnson <
>>>>> djohnson(a)maxistechnology.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I patched one of my Windows VM's yesterday. I started by
>>>>>> snapshotting the VM, then applied the Windows update. Now that the patch
>>>>>> has been tested, I want to remove the snapshot. I get this message:
>>>>>>
>>>>>> Error while executing action:
>>>>>>
>>>>>> win-sql-2019:
>>>>>>
>>>>>> - Cannot remove Snapshot. The following attached disks are in
>>>>>> ILLEGAL status: win-2019-tmpl_Disk1 - please remove them and try again.
>>>>>>
>>>>>>
>>>>>> Does anyone have any thoughts how to recover from this? I really
>>>>>> don't want to keep this snapshot hanging around.
>>>>>>
>>>>>> Thanks in advance,
>>>>>>
>>>>>> *David Johnson*
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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/PJODGOB2MI6...
>>>>>>
>>>>>
3 years, 5 months
how to start fedora coreos
by matthias.waldrey＠mail.de
Hello,
i try to use fedora coreos 34 from glance-repo.
i import template, choose as type redhat coreos and start with only user + key ingnition.
errormessage: Failed to run VM fcos34 (User: admin@internal-authz).
with other templates (centos8) i have no problems.
is there anything more todo before starting vm?
3 years, 5 months
Re: Creating Snapshots failed
by Strahil Nikolov
I thought that I sent it to all, but I was wrong
What is the output of ls -l /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/images/ad23c0db-1838-4f1f-811b-2b213d3a11cd/15259a3b-1065-4fb7-bc3c-04c5f4e14479 ?
Best Regards,Strahil Nikolov
On Tue, Jun 1, 2021 at 9:49, Liran Rotenberg<lrotenbe(a)redhat.com> wrote: On Mon, May 31, 2021 at 7:08 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote:
>
> This stale file handle can happen when there is a gfid mismatch between bricks causing a some kind of splitbrain.
>
>
> ls -l /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/images/ad23c0db-1838-4f1f-811b-2b213d3a11cd/15259a3b-1065-4fb7-bc3c-04c5f4e14479 could show the file status.
Hi Strahil,
Can you respond to the thread? Luckily for me, I don't deal with
glusterFS so much :)
>
> Best Regards,
> Strahil Nikolov
>
> On Mon, May 31, 2021 at 10:46, Liran Rotenberg
> <lrotenbe(a)redhat.com> wrote:
> _______________________________________________
> 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/4UV524PGGZE...
3 years, 5 months
Cannot add new host to Ovirt
by pablo＠miami.edu
I have an Ovirt installation with a hosted engine and three hosts. Using Gluster as the storage for the VMs.
Ovirt: 4.4.6.7
Hosts: CentOS Stream release 8 (updated to latest)
So far so good.
I am trying to add a new host to the cluster with the same OS and hardware as the others and I cannot get it to install, it gives me all kind of errors and it will not install.
I reinstalled the OS and I am getting the same results.
DNS is configured properly and working ok for all hosts.
I can see this error in this log file ansible-runner-service.log:
2021-05-30 15:46:38,319 - runner_service.services.hosts - ERROR - SSH - NOAUTH:SSH auth error - passwordless ssh not configured for 'ovirt4'
(sshd is configured exactly the same as all other hosts and I can login to this host without a password from the ovirt hosted engine)
I see these errors in the log engine.log:
2021-05-30 16:22:35,166Z ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2021-05-30 16:22:35,175Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt4.net.miami.edu command Get Host Capabilities failed: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2021-05-30 16:22:35,175Z ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2021-05-30 16:22:35,597Z ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-23) [] Error while refreshing server data for cluster 'Default' from database: null
I tried reinstalling, rebooting, put it in maintenance, enroll the certificate, check for Upgrades, rebooted multiple times both the hosts and the ovirt engine:
nothing works.
What am I doing wrong?
Thank you in advance for your help.
3 years, 5 months
(no subject)
by david
hi
i have a 4.4 ovirt cluster with a sigle server in it
the emulated chipset in this cluster is q35
i need to change emulated chipset from q35 to i440fx to add a new host that
don't support the q35 chipset type
how it will affect on vm's that are running on ovirt 4.4 cluster ?
what does this change process look like, how can i do it correctly?
3 years, 5 months
