[ovirt-users] Fail to upload image file after Replace oVirt Engine SSL/TLS Certificate
I replaced my Certificate follow
https://myhomelab.gr/linux/2020/01/20/replacing_ovirt_ssl.html
Then I cant upload image files
THE LOGS BELOW
2020-08-03 13:37:42,276+08 INFO
[org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand]
(default task-28) [272b83fa-1d1a-473e-b72a-19886433801e] Running command:
TransferImageStatusCommand internal: false. Entities affected : ID:
aaa0----123456789aaa Type: SystemAction group CREATE_DISK with
role type USER
2020-08-03 13:37:43,679+08 INFO
[org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-27) [] User
yuanq...@ft.com 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
2020-08-03 13:37:43,773+08 INFO
[org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-27)
[1e6c5da4] Running command: CreateUserSessionCommand internal: false.
2020-08-03 13:37:43,814+08 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default
task-27) [1e6c5da4] EVENT_ID: USER_VDC_LOGIN(30), User yuanq...@ft.com@ft.com
connecting from '192.168.16.199' using session
'AkdaHSmXHYlF3v53VoJRWVCIp0VYjFJPcR/vbRs0tfT20Qq9zylnacmSQKJJ8kwkWmj392Lq8j6EFcz22BKdTg=='
logged in.
2020-08-03 13:37:44,428+08 INFO
[org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] Command 'AddDisk' id:
'0f22fdf1-6016-40f3-9768-b436b5c83972' child commands
'[abaa6f3d-82a1-4317-857e-0c32e3ffeca1]' executions were completed, status
'SUCCEEDED'
2020-08-03 13:37:44,428+08 INFO
[org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] Command 'AddDisk' id:
'0f22fdf1-6016-40f3-9768-b436b5c83972' Updating status to 'SUCCEEDED', The
command end method logic will be executed by one of its parent commands.
2020-08-03 13:37:44,488+08 INFO
[org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] Successfully added Upload disk
'vyos-1.1.8-amd64.iso' (disk id: '2720658b-c1cb-4021-810c-8333e80858eb', image
id: '6a61dee5-fc07-4afb-af81-3672b9077a3a') for image transfer command
'900b725e-d409-4192-bb52-c52cb29b37ee'
2020-08-03 13:37:44,524+08 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] START, PrepareImageVDSCommand(HostName =
192.168.4.23,
PrepareImageVDSCommandParameters:{hostId='b6142941-cc9e-4da3-b66d-5132f359edb5'}),
log id: 4bfe1a2c
2020-08-03 13:37:44,640+08 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] FINISH, PrepareImageVDSCommand, return:
PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 4bfe1a2c
2020-08-03 13:37:44,641+08 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeLegalityVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] START, SetVolumeLegalityVDSCommand(
SetVolumeLegalityVDSCommandParameters:{storagePoolId='17fae97b-4a94-4de5-88c0-0743ab2b9ab8',
ignoreFailoverLimit='false',
storageDomainId='0d707e2b-42ed-48d4-9675-2021a3840f40',
imageGroupId='2720658b-c1cb-4021-810c-8333e80858eb',
imageId='6a61dee5-fc07-4afb-af81-3672b9077a3a'}), log id: 31d7b9fe
2020-08-03 13:37:44,658+08 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeLegalityVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] FINISH, SetVolumeLegalityVDSCommand,
return: , log id: 31d7b9fe
2020-08-03 13:37:44,659+08 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.AddImageTicketVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] START, AddImageTicketVDSCommand(HostName
= 192.168.4.23,
AddImageTicketVDSCommandParameters:{hostId='b6142941-cc9e-4da3-b66d-5132f359edb5',
ticketId='de8fa245-78ca-4d0a-b0b3-b7897aec7af6', timeout='300',
operations='[write]', size='241172480',
url='file:///rhev/data-center/mnt/_vmdata/0d707e2b-42ed-48d4-9675-2021a3840f40/images/2720658b-c1cb-4021-810c-8333e80858eb/6a61dee5-fc07-4afb-af81-3672b9077a3a',
filename='null', sparse='true',
transferId='900b725e-d409-4192-bb52-c52cb29b37ee'}), log id: 1687202b
2020-08-03 13:37:44,668+08 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.AddImageTicketVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-35)
[2a5567e7-25bc-4d58-ab31-8f88f5a4a5fa] FINISH,
[ovirt-users] error importing from VMware, and workaround
more details in my saga of problem imports from VMware/vsphere to ovirt (4.4.1
node)
I had done a couple successfully, but my next one kept failing. Couldnt figure
out why.
The only things resembling an error in the import logs, were this:
(trimmed a bit)
"rpm -e vmware-tools-nox vmware-tools-common"
{ "message": "libguestfs error: command: error: Failed
dependencies:\n\tvmware-tools-nox = 8.3.19 is needed by (installed)
vmware-tools-8.3.19-1310361.el6.x86_64", "timestamp":
"2020-08-02T21:28:08.797433658+00:00", "type": "error" }
I thought to myself.. nah, that couldnt be it. import failed.. because you
couldnt REMOVE a package??? that would be dumb.
but that was the problem.
I started up the old vm, did a
yum remove 'vmware-*'
reexported from VMware, and then imported...
and this time, the import worked.
Please fix that behaviour.
--
Philip Brown| Sr. Linux System Administrator | Medata, Inc.
5 Peters Canyon Rd Suite 250
Irvine CA 92606
Office 714.918.1310| Fax 714.918.1325
pbr...@medata.com| www.medata.com
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJUNBJ7YYIRMWQ6GPA272IO4ILRAY7PM/
[ovirt-users] Re: Snapshot and disk size allocation
You may also refer to https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/technical_reference/chap-virtual_machine_snapshots On Sun, Aug 2, 2020 at 10:35 AM Strahil Nikolov via Users wrote: > It's quite simple. > > For example , you got vm1 with 10GB OS disk that is fully preallocated > (actual size is really 10GB). > Now imagine that you create a snapshot of this vm1 and you download 1GB > file from another place. > You will see 2 disk files on the storage domain: > - The original one that was made read-only during the snapshot process > - A new 1GB file that represents the delta (changes between snapshot and > current state) > > The second file is read-write and if left as is - it will grow up to 10GB > (the actual disk of the vm1). When the Virtualization is looking for some > data it has to search into 2 places which will reduce performance a > little bit.If you decide to create another snapshot, the second disk will > be made read-only and another one will be created and so on and so on. > > When you delete a snapshot, the disks will be merged in such way so newer > snapshot disks remain, while the rest are merged into a single file. > > Restoring a snapshot is simplest - everything after that snapshot is > deleted and the vm1 will use the snapshot disk till you delete (which will > merge base disk with snapshot disk) that snapshot. > > > Best Regards, > Strahil Nikolov > > На 2 август 2020 г. 3:53:11 GMT+03:00, jorgevisent...@gmail.com написа: > >Hello everyone. > > > >I would like to know how disk size and snapshot allocation works, > >because every time I create a new snapshot, it increases 1 GB in the > >VM's disk size, and when I remove the snap, that space is not returned > >to Domain Storage. > > > >I'm using the oVirt 4.3.10 > > > >How do I reprovision the VM disk? > > > >Thank you all. > >___ > >Users mailing list -- users@ovirt.org > >To unsubscribe send an email to users-le...@ovirt.org > >Privacy Statement: https://www.ovirt.org/privacy-policy.html > >oVirt Code of Conduct: > >https://www.ovirt.org/community/about/community-guidelines/ > >List Archives: > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3TG24XR77PISMBRZ5S5L4P7DV56SUDON/ > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/7AEVC7U4JUFWPAGQRJDN7WIZ37CZK474/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TV52OBEVPWCXYIHX7CMD66E7HFRWEA4Y/
[ovirt-users] Re: Snapshot and disk size allocation
It's quite simple. For example , you got vm1 with 10GB OS disk that is fully preallocated (actual size is really 10GB). Now imagine that you create a snapshot of this vm1 and you download 1GB file from another place. You will see 2 disk files on the storage domain: - The original one that was made read-only during the snapshot process - A new 1GB file that represents the delta (changes between snapshot and current state) The second file is read-write and if left as is - it will grow up to 10GB (the actual disk of the vm1). When the Virtualization is looking for some data it has to search into 2 places which will reduce performance a little bit.If you decide to create another snapshot, the second disk will be made read-only and another one will be created and so on and so on. When you delete a snapshot, the disks will be merged in such way so newer snapshot disks remain, while the rest are merged into a single file. Restoring a snapshot is simplest - everything after that snapshot is deleted and the vm1 will use the snapshot disk till you delete (which will merge base disk with snapshot disk) that snapshot. Best Regards, Strahil Nikolov На 2 август 2020 г. 3:53:11 GMT+03:00, jorgevisent...@gmail.com написа: >Hello everyone. > >I would like to know how disk size and snapshot allocation works, >because every time I create a new snapshot, it increases 1 GB in the >VM's disk size, and when I remove the snap, that space is not returned >to Domain Storage. > >I'm using the oVirt 4.3.10 > >How do I reprovision the VM disk? > >Thank you all. >___ >Users mailing list -- users@ovirt.org >To unsubscribe send an email to users-le...@ovirt.org >Privacy Statement: https://www.ovirt.org/privacy-policy.html >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/ >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/3TG24XR77PISMBRZ5S5L4P7DV56SUDON/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7AEVC7U4JUFWPAGQRJDN7WIZ37CZK474/
