Error creating local storage domain: Internal Engine Error.
by christian_barr＠hotmail.com
Hello.
I'm new to ovirt and trying to set up a sandbox on an old Dell workstation I have. Any help greatly appreciated.
I have created a 4.2 Compatible DC and Cluster. I'm able to add the host and that checks in OK.
Its an older system hence going with 4.2 for processor support.
When I try to a local storage domain, it fails.
The error returned to the screen is : Error while executing action New Local Storage Domain: Internal Engine Error
The process gets as far as creating some files and directories in the directory I'm trying to configure as a local storage domain.
I notice in the UI, the format of the domain is specified as v4. (This option is greyed out and I cannot modify it).
This is an excerpt of the engine.log, with the error the first line of which seems to be indicating its trying to use a v5 format .....
019-08-07 23:21:24,618+01 WARN [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Validation of action 'AttachStorageDomainToPool' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_FORMAT_ILLEGAL,$storageFormat V5
2019-08-07 23:21:24,620+01 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Lock freed to object 'EngineLock:{exclusiveLocks='[f2858a80-4730-40f8-b417-50d65503dcae=STORAGE]', sharedLocks=''}'
2019-08-07 23:21:24,623+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating DELETED_OR_UPDATED_ENTITY of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: id=f2858a80-4730-40f8-b417-50d65503dcae.
2019-08-07 23:21:24,626+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.profiles.DiskProfile; snapshot: 94c8fb2e-e17a-46dd-a859-f3e18d9b3de7.
2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae.
2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainStatic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae.
2019-08-07 23:21:24,635+01 ERROR [org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand] (default task-56) [67e87701] Transaction rolled-back for command 'org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand'.
2019-08-07 23:21:24,639+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-56) [67e87701] EVENT_ID: USER_ADD_STORAGE_DOMAIN_FAILED(957), Failed to add Storage Domain STG01. (User: admin@internal-authz)
Thanks all.
Barman.
4 years, 8 months
ovirt-web-ui-1.5.3: immediate logout in VM portal
by Matthias Leopold
Hi,
after upgrading to oVirt 4.3.5 yesterday (which also brought
ovirt-web-ui-1.5.3) users are immediately logged out after login to the
"VM Portal" with "You have been logged out due to inactivity" displayed
in the browser. The "Administration Portal" works as expected.
This happens
- for existing UserRole users/new UserRole users/Administrator users
- with different browsers (Chrome/Firefox/IE)
- also when creating new browser profiles
Logs in engine.log are unsuspicious IMHO (see below for Administrator
user login).
/var/log/ovirt-engine/ui.log is completely quiet.
Downgrade to 1.5.2 resolves the situation.
Reading about "Added check for inactivity during session and logout
after expiration" in 1.5.3 changelog suggests that something might have
gone wrong.
Has anybody seen this?
Shall I file a bug report?
thx
matthias
2019-08-07 12:51:45,556+02 INFO
[org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-8)
[] User admin@internal successfully logged in with scopes:
ovirt-app-admin ovirt-app-api ovirt-app-portal
ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all
ovirt-ext=token-info:authz-search
ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate
ovirt-ext=token:password-access
2019-08-07 12:51:45,728+02 INFO
[org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default
task-8) [2cb53d8d] Running command: CreateUserSessionCommand internal:
false.
2019-08-07 12:51:45,768+02 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-8) [2cb53d8d] EVENT_ID: USER_VDC_LOGIN(30), User
admin@internal-authz connecting from 'xxx.yyy.zzz.63' using session
'+DY5GdQK35zrApbt971Df0nACY2o5qpT0ebX7zFnYj/SNnJACyH7nKKd5iJSshJZZo0TgkJUoSixB7StGq10VA=='
logged in.
2019-08-07 12:51:48,385+02 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetFileStatsVDSCommand]
(default task-11) [92c5e178-324e-4407-a844-7d1cb67e71b0] START,
GetFileStatsVDSCommand(
GetFileStatsParameters:{storagePoolId='1285d24b-53d1-4b4d-bba4-4aa6264f0c4a',
ignoreFailoverLimit='false'}), log id: cd6a0e4
2019-08-07 12:51:48,394+02 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetFileStatsVDSCommand]
(default task-11) [92c5e178-324e-4407-a844-7d1cb67e71b0] FINISH,
GetFileStatsVDSCommand, return: {grml64-full_2018.12.iso={status=0,
ctime=1553615947.0, size=704905216},
CentOS-7-x86_64-Minimal-1810.iso={status=0, ctime=1555410499.0,
size=962592768}}, log id: cd6a0e4
2019-08-07 12:51:48,419+02 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-11) [92c5e178-324e-4407-a844-7d1cb67e71b0] EVENT_ID:
REFRESH_REPOSITORY_IMAGE_LIST_SUCCEEDED(998), Refresh image list
succeeded for domain(s): ISOstar-DEV (All file type)
2019-08-07 12:51:49,478+02 INFO
[org.ovirt.engine.core.bll.aaa.LogoutSessionCommand] (default task-8)
[4f195583] Running command: LogoutSessionCommand internal: false.
2019-08-07 12:51:49,524+02 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-8) [4f195583] EVENT_ID: USER_VDC_LOGOUT(31), User
admin@internal-authz connected from 'xxx.yyy.zzz.63' using session
'+DY5GdQK35zrApbt971Df0nACY2o5qpT0ebX7zFnYj/SNnJACyH7nKKd5iJSshJZZo0TgkJUoSixB7StGq10VA=='
logged out.
2019-08-07 12:51:49,581+02 INFO
[org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default
task-14) [] User admin@internal successfully logged out
2019-08-07 12:51:49,675+02 INFO
[org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand]
(default task-11) [37daeccc] Running command:
TerminateSessionsForTokenCommand internal: true.
4 years, 8 months
Re: Error creating local storage domain: Internal Engine Error.
by christian barr
________________________________
Hi.
I have attached logs and screens
Thanks.
Barman.
________________________________
From: Shani Leviim <sleviim(a)redhat.com>
Sent: 08 August 2019 12:36
To: christian_barr(a)hotmail.com <christian_barr(a)hotmail.com>
Cc: users <users(a)ovirt.org>
Subject: Re: [ovirt-users] Error creating local storage domain: Internal Engine Error.
Hi Barman,
Can you please attach a full engine log?
Also attaching a screenshot would be great.
Regards,
Shani Leviim
On Thu, Aug 8, 2019 at 2:44 PM <christian_barr(a)hotmail.com<mailto:christian_barr@hotmail.com>> wrote:
Hello.
I'm new to ovirt and trying to set up a sandbox on an old Dell workstation I have. Any help greatly appreciated.
I have created a 4.2 Compatible DC and Cluster. I'm able to add the host and that checks in OK.
Its an older system hence going with 4.2 for processor support.
When I try to a local storage domain, it fails.
The error returned to the screen is : Error while executing action New Local Storage Domain: Internal Engine Error
The process gets as far as creating some files and directories in the directory I'm trying to configure as a local storage domain.
I notice in the UI, the format of the domain is specified as v4. (This option is greyed out and I cannot modify it).
This is an excerpt of the engine.log, with the error the first line of which seems to be indicating its trying to use a v5 format .....
019-08-07 23:21:24,618+01 WARN [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Validation of action 'AttachStorageDomainToPool' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_FORMAT_ILLEGAL,$storageFormat V5
2019-08-07 23:21:24,620+01 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Lock freed to object 'EngineLock:{exclusiveLocks='[f2858a80-4730-40f8-b417-50d65503dcae=STORAGE]', sharedLocks=''}'
2019-08-07 23:21:24,623+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating DELETED_OR_UPDATED_ENTITY of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: id=f2858a80-4730-40f8-b417-50d65503dcae.
2019-08-07 23:21:24,626+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.profiles.DiskProfile; snapshot: 94c8fb2e-e17a-46dd-a859-f3e18d9b3de7.
2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae.
2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainStatic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae.
2019-08-07 23:21:24,635+01 ERROR [org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand] (default task-56) [67e87701] Transaction rolled-back for command 'org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand'.
2019-08-07 23:21:24,639+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-56) [67e87701] EVENT_ID: USER_ADD_STORAGE_DOMAIN_FAILED(957), Failed to add Storage Domain STG01. (User: admin@internal-authz)
Thanks all.
Barman.
_______________________________________________
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/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EMNQLWPQ2BV...
4 years, 8 months
Re: Agentless backup solutions
by Strahil
I had corruption of the Hosted Engine due to a power failiure of all hosts (Gluster).
My lab has no UPS.
You can create a snapshot via API , backup the snapshot and then delete it via the API while the VM is working (no downtime).
Still, this approach won't work for Databases as you can create the snapahot in the middle of a transaction.
Best Regards,
Strahil NikolovOn Aug 7, 2019 20:33, Douglas Duckworth <dod2014(a)med.cornell.edu> wrote:
>
> Hi
>
>
> We are running oVirt 4.2.8.2-1.el7. Should probably upgrade but it works.
>
>
> We are backing up the engine every day with dump going to external NFS file system then onto the cloud. For VMs we are doing backups within Linux itself using a program called Restic which then sends data to cloud S3 service. That runs daily as well.
>
>
> We also save all configuration data, for applications running on our VMs such as Apache, etc, within Ansible. So we can quickly recreate the VM using Ansible, along with any applications, then restore any data, not saved in Ansible, such as private PKI keys or PostgreSQL dump, for example, from Restic. Dockerized applications even easier. There would be some downtime to redeploy a new VM but this is acceptable given the constrains of our environment.
>
>
> I am wondering under what situations has anyone experienced VM corruption? This would help me determine if more effort should be invested in snapshotting VMs and possibly exporting their disks. Though as I recall removing snapshots from my storage domain would require shutting down the VM, right?
>
>
> --
> Thanks,
>
> Douglas Duckworth, MSc, LFCS
> HPC System Administrator
> Scientific Computing Unithttps://github.com/restic/restic
4 years, 8 months
Ovirt 4.3.5.4-1.el7 noVNC keeps disconnecting with 1006
by Strahil Nikolov
Hello Community,
did anyone experience disconnects after a minute or 2 (seems random ,but I will check it out) with error code 1006 ?Can someone with noVNC reproduce that behaviour ?
As I manage to connect, it seems strange to me to loose connection like that. The VM was not migrated - so it should be something else.
Best Regards,Strahil Nikolov
4 years, 8 months
[ANN] oVirt 4.3.6 Second Release Candidate is now available for testing
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.3.6 Second Release Candidate for testing, as of August 8th, 2019.
This update is a release candidate of the sixth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only)
See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.
Notes:
- oVirt Appliance is already available
- oVirt Node is not yet available, pending CentOS 7.7 release to be
available
Additional Resources:
* Read more about the oVirt 4.3.6 release highlights:
http://www.ovirt.org/release/4.3.6/
* 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.3.6/
--
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.*
4 years, 8 months
RFE: Add the ability to the engine to serve as a fencing proxy
by Sandro E
Hi,
i hope that this hits the right people i found an RFE (Bug 1373957) which would be a realy nice feature for my company as we have to request firewall rules for every new host and this ends up in a lot of mess and work. Is there any change that this RFE gets implemented ?
Thanks for any help or tips
BR,
Sandro
4 years, 8 months
Removing VDSM dependency on multipath driver.
by amit1.kumar＠intel.com
Hi All,
I observed that for FCP storage domain only mpath enabled drives are getting listed, for e.g. if we have local nvme drives attached to the VDSM host, only mpath enabled nvme drives are getting listed in the ovirt engine for FCP storage domain.
Actually I am creating a RAID (using mdadm tool, software raid) on two local nvme drives and wanted to expose it to the Ovirt engine through FCP storage domain, is it possible? or can we bypass multipath in FCP storage domain so that all the block device can be listed in the ovirt engine for FCP storage domain?
Thanks,
Amit
4 years, 8 months
oVirt 4.3.5.1 failed to configure management network on the host
by Mitja Pirih
Hi,
I am trying to deploy hosted engine on Ovirt Node 4.3.5.1 and I am
getting: ovirt failed to configure management network on the host. I am
pretty sure the problem lies in my network config that is actually
working quite nice.
My current network config is:
team0:
- Switch1: bond0 (LACP): eno1,eno3
- Switch2: bond1 (LACP): eno2,eno4
Switch1 and switch2 are interconnected by a different LAG group.
Current network config was tested against all kinds of failures, nic
port failure, switch failure...etc...and it works. Although I am open to
suggestions how to implement high availability with high throughput.
By default on hosted engine deployment team0 is selected as bridge
interface.
Br,
Mitja
Logs:
=== supervdsm.log: https://pastebin.com/raw/bijW7uhi
=== vdsm.log part1: https://pastebin.com/raw/BYGsieCw
=== vdsm.log part2: https://pastebin.com/raw/rgzQCDjw
4 years, 8 months
