Re: [ovirt-users] Failed to read hardware information

2016-10-09 Thread Nir Soffer 
On Mon, Oct 10, 2016 at 5:05 AM, Charles Kozler 
wrote:

> Possibly stupid question but are you doing this on a base empty
> centos/rhel 7?
>
> On Oct 9, 2016 9:48 PM, "David Pinkerton"  wrote:
>
>>
>> I've spent the weekend trying to get to the bottom of this issue.
>>
>> Adding a Host fails:
>>
>> From RHVM
>>
>>
>> VDSM rhv1 command failed: Connection reset by peer
>> Could not get hardware information for host rhv1
>> VDSM rhv1 command failed: Failed to read hardware information
>> Host rhv1 installed
>> Network changes were saved on host rhv1
>> Installing Host rhv1. Stage: Termination.
>> Installing Host rhv1. Retrieving installation logs to:
>> '/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-2016101
>> 0115606-192.168.21.71-24d39274.log'.
>> Installing Host rhv1. Stage: Pre-termination.
>> Installing Host rhv1. Starting ovirt-vmconsole-host-sshd.
>> Installing Host rhv1. Starting vdsm.
>> Installing Host rhv1. Stopping libvirtd.
>> Installing Host rhv1. Stage: Closing up.
>> Installing Host rhv1. Setting kernel arguments.
>> Installing Host rhv1. Stage: Transaction commit.
>> Installing Host rhv1. Enrolling serial console certificate.
>> Installing Host rhv1. Enrolling certificate.
>> Installing Host rhv1. Stage: Misc configuration.
>>
>>
>>
>> This was in the /var/log/vdsm/vdsm.log on the host trying to be added:
>>
>> jsonrpc.Executor/2::ERROR::2016-10-10 
>> 11:57:10,276::API::1340::vds::(getHardwareInfo)
>> failed to retrieve hardware info
>> Traceback (most recent call last):
>>   File "/usr/share/vdsm/API.py", line 1337, in getHardwareInfo
>> hw = supervdsm.getProxy().getHardwareInfo()
>>   File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
>> __call__
>> return callMethod()
>>   File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
>> 
>> **kwargs)
>>   File "", line 2, in getHardwareInfo
>>   File "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in
>> _callmethod
>> kind, result = conn.recv()
>> EOFError
>>
>
If a request to supervdsm fails with EOFError, something bad happened
supervdsm and we would see the exception in the supervdsm log.

Can you share supervdsm.log?

Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Failed to read hardware information

2016-10-09 Thread Charles Kozler 
Possibly stupid question but are you doing this on a base empty centos/rhel
7?

On Oct 9, 2016 9:48 PM, "David Pinkerton"  wrote:

>
> I've spent the weekend trying to get to the bottom of this issue.
>
> Adding a Host fails:
>
> From RHVM
>
>
> VDSM rhv1 command failed: Connection reset by peer
> Could not get hardware information for host rhv1
> VDSM rhv1 command failed: Failed to read hardware information
> Host rhv1 installed
> Network changes were saved on host rhv1
> Installing Host rhv1. Stage: Termination.
> Installing Host rhv1. Retrieving installation logs to:
> '/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-
> 20161010115606-192.168.21.71-24d39274.log'.
> Installing Host rhv1. Stage: Pre-termination.
> Installing Host rhv1. Starting ovirt-vmconsole-host-sshd.
> Installing Host rhv1. Starting vdsm.
> Installing Host rhv1. Stopping libvirtd.
> Installing Host rhv1. Stage: Closing up.
> Installing Host rhv1. Setting kernel arguments.
> Installing Host rhv1. Stage: Transaction commit.
> Installing Host rhv1. Enrolling serial console certificate.
> Installing Host rhv1. Enrolling certificate.
> Installing Host rhv1. Stage: Misc configuration.
>
>
>
> This was in the /var/log/vdsm/vdsm.log on the host trying to be added:
>
> jsonrpc.Executor/2::ERROR::2016-10-10 
> 11:57:10,276::API::1340::vds::(getHardwareInfo)
> failed to retrieve hardware info
> Traceback (most recent call last):
>   File "/usr/share/vdsm/API.py", line 1337, in getHardwareInfo
> hw = supervdsm.getProxy().getHardwareInfo()
>   File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
> __call__
> return callMethod()
>   File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
> 
> **kwargs)
>   File "", line 2, in getHardwareInfo
>   File "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in
> _callmethod
> kind, result = conn.recv()
> EOFError
>
>
> and then VDSM fails to start.
>
>
>
> Looking at the source code...
>
> def getHardwareInfoStructure():
> dmiInfo = getAllDmidecodeInfo()
> sysStruct = {}
> for k1, k2 in (('system', 'Manufacturer'),
>('system', 'Product Name'),
>('system', 'Version'),
>('system', 'Serial Number'),
>('system', 'UUID'),
>('system', 'Family')):
> val = dmiInfo.get(k1, {}).get(k2, None)
> if val not in [None, 'Not Specified']:
> sysStruct[(k1 + k2).replace(' ', '')] = val
>
> return sysStruct
>
>
>
> Running dmidecode from command line I get..
>
> System Information
> Manufacturer: Supermicro
> Product Name: H8DM8-2
> Version: 1234567890
> Serial Number: 1234567890
> UUID: 00020003-0004-0005-0006-000700080009
> Wake-up Type: Power Switch
> SKU Number: To Be Filled By O.E.M.
> Family: To Be Filled By O.E.M.
>
>
> Q: Is the string in Family the source of my problems??
>
> Q: Any work arounds??
>
>
>
>
>
>
>
>
> --
>
> David Pinkerton
> Consultant
> Red Hat Asia Pacific Pty. Ltd.
> Level 11, Canberra House
> 40 Marcus Clarke Street
> Canberra 2600 ACT
>
> Mobile: +61-488-904-232
> Email: david.pinker...@redhat.com
> Web: http://apac.redhat.com/ 
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Failed to read hardware information

2016-10-09 Thread David Pinkerton 
I've spent the weekend trying to get to the bottom of this issue.

Adding a Host fails:

>From RHVM


VDSM rhv1 command failed: Connection reset by peer
Could not get hardware information for host rhv1
VDSM rhv1 command failed: Failed to read hardware information
Host rhv1 installed
Network changes were saved on host rhv1
Installing Host rhv1. Stage: Termination.
Installing Host rhv1. Retrieving installation logs to:
'/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20161010115606-192.168.21.71-24d39274.log'.
Installing Host rhv1. Stage: Pre-termination.
Installing Host rhv1. Starting ovirt-vmconsole-host-sshd.
Installing Host rhv1. Starting vdsm.
Installing Host rhv1. Stopping libvirtd.
Installing Host rhv1. Stage: Closing up.
Installing Host rhv1. Setting kernel arguments.
Installing Host rhv1. Stage: Transaction commit.
Installing Host rhv1. Enrolling serial console certificate.
Installing Host rhv1. Enrolling certificate.
Installing Host rhv1. Stage: Misc configuration.



This was in the /var/log/vdsm/vdsm.log on the host trying to be added:

jsonrpc.Executor/2::ERROR::2016-10-10
11:57:10,276::API::1340::vds::(getHardwareInfo) failed to retrieve hardware
info
Traceback (most recent call last):
  File "/usr/share/vdsm/API.py", line 1337, in getHardwareInfo
hw = supervdsm.getProxy().getHardwareInfo()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
__call__
return callMethod()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in

**kwargs)
  File "", line 2, in getHardwareInfo
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in
_callmethod
kind, result = conn.recv()
EOFError


and then VDSM fails to start.



Looking at the source code...

def getHardwareInfoStructure():
dmiInfo = getAllDmidecodeInfo()
sysStruct = {}
for k1, k2 in (('system', 'Manufacturer'),
   ('system', 'Product Name'),
   ('system', 'Version'),
   ('system', 'Serial Number'),
   ('system', 'UUID'),
   ('system', 'Family')):
val = dmiInfo.get(k1, {}).get(k2, None)
if val not in [None, 'Not Specified']:
sysStruct[(k1 + k2).replace(' ', '')] = val

return sysStruct



Running dmidecode from command line I get..

System Information
Manufacturer: Supermicro
Product Name: H8DM8-2
Version: 1234567890
Serial Number: 1234567890
UUID: 00020003-0004-0005-0006-000700080009
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: To Be Filled By O.E.M.


Q: Is the string in Family the source of my problems??

Q: Any work arounds??








-- 

David Pinkerton
Consultant
Red Hat Asia Pacific Pty. Ltd.
Level 11, Canberra House
40 Marcus Clarke Street
Canberra 2600 ACT

Mobile: +61-488-904-232
Email: david.pinker...@redhat.com
Web: http://apac.redhat.com/ 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cleanup illegal snapshot

2016-10-09 Thread Markus Stockhausen 
Bug with logs attached:

https://bugzilla.redhat.com/show_bug.cgi?id=1383084

Best regards.

Markus



Von: Nir Soffer [nsof...@redhat.com]
Gesendet: Sonntag, 9. Oktober 2016 20:37
An: Markus Stockhausen
Cc: Ala Hino; Ovirt Users
Betreff: Re: [ovirt-users] Cleanup illegal snapshot

On Sun, Oct 9, 2016 at 8:33 PM, Markus Stockhausen
 wrote:
> Hi Ala,
>
> that did not help. VDSM log tells me that the delta qcow2 file is missing:
>
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 873, in _run
> return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 49, in wrapper
> res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 3162, in getVolumeInfo
> volUUID=volUUID).getInfo()
>   File "/usr/share/vdsm/storage/sd.py", line 457, in produceVolume
> volUUID)
>   File "/usr/share/vdsm/storage/fileVolume.py", line 58, in __init__
> volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
>   File "/usr/share/vdsm/storage/volume.py", line 181, in __init__
> self.validate()
>   File "/usr/share/vdsm/storage/volume.py", line 194, in validate
> self.validateVolumePath()
>   File "/usr/share/vdsm/storage/fileVolume.py", line 540, in
> validateVolumePath
> raise se.VolumeDoesNotExist(self.volUUID)
> VolumeDoesNotExist: Volume does not exist:
> (u'c277351d-e2b1-4057-aafb-55d4b607ebae',)
> ...
> Thread-196::ERROR::2016-10-09 19:31:07,037::utils::739::root::(wrapper)
> Unhandled exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in
> wrapper
> return f(*a, **kw)
>   File "/usr/share/vdsm/virt/vm.py", line 5264, in run
> self.update_base_size()
>   File "/usr/share/vdsm/virt/vm.py", line 5257, in update_base_size
> self.drive.imageID, topVolUUID)
>   File "/usr/share/vdsm/virt/vm.py", line 5191, in _getVolumeInfo
> (domainID, volumeID))
> StorageUnavailableError: Unable to get volume info for domain
> 47202573-6e83-42fd-a274-d11f05eca2dd volume
> c277351d-e2b1-4057-aafb-55d4b607ebae

Hi Markus,

I'm sorry for this confusing log,  Vdsm is treating a missing volume
as a horrible
error is a bug, this is expected condition when you query volume info.

We also log 2 exceptions instead of one.

Would file a vdsm storage bug for these issues?

Thanks,
Nir

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

Über das Internet versandte E-Mails können unter fremden Namen erstellt oder
manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine
rechtsverbindliche Willenserklärung.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 Köln

Vorstand:
Kadir Akin
Dr. Michael Höhnerbach

Vorsitzender des Aufsichtsrates:
Hans Kristian Langva

Registergericht: Amtsgericht Köln
Registernummer: HRB 52 497

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

e-mails sent over the internet may have been written under a wrong name or
been manipulated. That is why this message sent as an e-mail is not a
legally binding declaration of intention.

Collogia
Unternehmensberatung AG
Ubierring 11
D-50678 Köln

executive board:
Kadir Akin
Dr. Michael Höhnerbach

President of the supervisory board:
Hans Kristian Langva

Registry office: district court Cologne
Register number: HRB 52 497


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cleanup illegal snapshot

2016-10-09 Thread Nir Soffer 
On Sun, Oct 9, 2016 at 8:33 PM, Markus Stockhausen
 wrote:
> Hi Ala,
>
> that did not help. VDSM log tells me that the delta qcow2 file is missing:
>
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 873, in _run
> return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 49, in wrapper
> res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 3162, in getVolumeInfo
> volUUID=volUUID).getInfo()
>   File "/usr/share/vdsm/storage/sd.py", line 457, in produceVolume
> volUUID)
>   File "/usr/share/vdsm/storage/fileVolume.py", line 58, in __init__
> volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
>   File "/usr/share/vdsm/storage/volume.py", line 181, in __init__
> self.validate()
>   File "/usr/share/vdsm/storage/volume.py", line 194, in validate
> self.validateVolumePath()
>   File "/usr/share/vdsm/storage/fileVolume.py", line 540, in
> validateVolumePath
> raise se.VolumeDoesNotExist(self.volUUID)
> VolumeDoesNotExist: Volume does not exist:
> (u'c277351d-e2b1-4057-aafb-55d4b607ebae',)
> ...
> Thread-196::ERROR::2016-10-09 19:31:07,037::utils::739::root::(wrapper)
> Unhandled exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in
> wrapper
> return f(*a, **kw)
>   File "/usr/share/vdsm/virt/vm.py", line 5264, in run
> self.update_base_size()
>   File "/usr/share/vdsm/virt/vm.py", line 5257, in update_base_size
> self.drive.imageID, topVolUUID)
>   File "/usr/share/vdsm/virt/vm.py", line 5191, in _getVolumeInfo
> (domainID, volumeID))
> StorageUnavailableError: Unable to get volume info for domain
> 47202573-6e83-42fd-a274-d11f05eca2dd volume
> c277351d-e2b1-4057-aafb-55d4b607ebae

Hi Markus,

I'm sorry for this confusing log,  Vdsm is treating a missing volume
as a horrible
error is a bug, this is expected condition when you query volume info.

We also log 2 exceptions instead of one.

Would file a vdsm storage bug for these issues?

Thanks,
Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cleanup illegal snapshot

2016-10-09 Thread Ala Hino 
Hi Markus,

Few errors are expected. Do you still see the snapshot in the GUI?
Can you please send engine logs as well.

Thanks,
Ala

On Sun, Oct 9, 2016 at 8:33 PM, Markus Stockhausen 
wrote:

> Hi Ala,
>
> that did not help. VDSM log tells me that the delta qcow2 file is missing:
>
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 873, in _run
> return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 49, in wrapper
> res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 3162, in getVolumeInfo
> volUUID=volUUID).getInfo()
>   File "/usr/share/vdsm/storage/sd.py", line 457, in produceVolume
> volUUID)
>   File "/usr/share/vdsm/storage/fileVolume.py", line 58, in __init__
> volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
>   File "/usr/share/vdsm/storage/volume.py", line 181, in __init__
> self.validate()
>   File "/usr/share/vdsm/storage/volume.py", line 194, in validate
> self.validateVolumePath()
>   File "/usr/share/vdsm/storage/fileVolume.py", line 540, in
> validateVolumePath
> raise se.VolumeDoesNotExist(self.volUUID)
> VolumeDoesNotExist: Volume does not exist: (u'c277351d-e2b1-4057-aafb-
> 55d4b607ebae',)
> ...
> Thread-196::ERROR::2016-10-09 19:31:07,037::utils::739::root::(wrapper)
> Unhandled exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in
> wrapper
> return f(*a, **kw)
>   File "/usr/share/vdsm/virt/vm.py", line 5264, in run
> self.update_base_size()
>   File "/usr/share/vdsm/virt/vm.py", line 5257, in update_base_size
> self.drive.imageID, topVolUUID)
>   File "/usr/share/vdsm/virt/vm.py", line 5191, in _getVolumeInfo
> (domainID, volumeID))
> StorageUnavailableError: Unable to get volume info for domain
> 47202573-6e83-42fd-a274-d11f05eca2dd volume c277351d-e2b1-4057-aafb-
> 55d4b607ebae
>
> Do you have any idea?
>
> Markus
> 
>
> *Von:* Ala Hino [ah...@redhat.com]
> *Gesendet:* Donnerstag, 6. Oktober 2016 12:29
> *An:* Markus Stockhausen
>
> *Betreff:* Re: [ovirt-users] Cleanup illegal snapshot
>
> Indeed, retry live merge. There is no harm in retrying live merge. As
> mentioned, if the image deleted at storage side, retrying live merge should
> clean the engine side.
>
> On Thu, Oct 6, 2016 at 1:06 PM, Markus Stockhausen <
> stockhau...@collogia.de> wrote:
>
>> Hi,
>>
>> we are on OVirt 4.0.4. As explained the situation is as follows:
>>
>> - On Disk we have the base image and the delata qcow2 file
>> - Qemu runs only on the base image
>> - The snapshot in Qemu is tagged as illegal
>>
>> So you say: "Just retry a live merge and everything will cleanup."
>> Did I get it right?
>>
>> Markus
>>
>> ---
>>
>> *Von:* Ala Hino [ah...@redhat.com]
>> *Gesendet:* Donnerstag, 6. Oktober 2016 11:21
>> *An:* Markus Stockhausen
>> *Cc:* Ovirt Users; Nir Soffer; Adam Litke
>>
>> *Betreff:* Re: [ovirt-users] Cleanup illegal snapshot
>>
>> Hi Markus,
>>
>> What's the version that you are using?
>> In oVirt 3.6.6, illegal snapshots could be removed by retrying to live
>> merge them again. Assuming the previous live merge of the snapshot
>> successfully completed but the engine failed to get the result, the second
>> live merge should do the necessary cleanups at the engine side. See
>> https://bugzilla.redhat.com/1323629
>>
>> Hope this helps,
>> Ala
>>
>> On Thu, Oct 6, 2016 at 11:53 AM, Markus Stockhausen <
>> stockhau...@collogia.de> wrote:
>>
>>> Hi Ala,
>>>
>>> > Von: Adam Litke [ali...@redhat.com]
>>> > Gesendet: Freitag, 30. September 2016 15:54
>>> > An: Markus Stockhausen
>>> > Cc: Ovirt Users; Ala Hino; Nir Soffer
>>> > Betreff: Re: [ovirt-users] Cleanup illegal snapshot
>>> >
>>> > On 30/09/16 05:47 +, Markus Stockhausen wrote:
>>> > >Hi,
>>> > >
>>> > >if a OVirt snapshot is illegal we might have 2 situations.
>>> > >
>>> > >1) qemu is still using it - lsof shows qemu access to the base raw
>>> and the
>>> > >delta qcow2 file. -> E.g. a previous live merge failed. In the past we
>>> > >successfully solved that situation by setting the status of the delta
>>> image
>>> > >in the database to OK.
>>> > >
>>> > >2) qemu is no longer using it. lsof shows qemu access only to the the
>>> base
>>> > >raw file -> E.g. a previous live merge succeded in qemu but Ovirt did
>>> not
>>> > >recognize.
>>> > >
>>> > >How to clean up the 2nd situation?
>>> >
>>> > It seems that you will have to first clean up the engine database to
>>> > remove references to the snapshot that no longer exists.  Then you
>>> > will need to remove the unused qcow2 volume.
>>> >
>>> > Unfortunately I cannot provide safe instructions for modifying the
>>> > database but maybe Ala Hino (added to CC:) will be able to help with
>>> > that.
>>>
>>> Do you have some tip for me?
>>>
>>> >
>>> > One you have fixed the DB you should be able to delete the volume
>>> > u

Re: [ovirt-users] Stalled disk migration

2016-10-09 Thread Nicolás 

Just to update:

I used: PGPASSWORD=dbpass 
/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -v -u engine -d 
engine -t disk 


This indeed got the disks back to the OK state, however, the task 
remained in the 'Events' tab so even with the unlocked disks I couldn't 
do anything, as oVirt complained about the disks being "moved", so I 
couldn't do anything of copying the disks, starting the VMs, moving the 
disks, etc.


"Miraculously" I checked the day after and both tasks disappeared from 
the Events tab, so I tried moving one disk again, with the same result: 
it stalled. I managed to copy the other disk to the destination 
datastore and attach it to the machine. This worked, but now I have one 
of the VMs still stalled even after running the "unlock_entity" script, 
as this time the task wasn't removed from the Events tab.


Regards.

El 06/10/16 a las 19:45, Nicolás escribió:

Hi,

We've done a major datastore migration recently between 2 iSCSI-based 
datastores. We've successfully migrated 35 machines, however, 5 of 
them seem to have stalled. All we can see in the events tab tab is:


  Moving Disk bla_Disk1 from iscsi01 to iscsi02

Disks are small enough (25-27Gb) to assume this won't progress since 
it's been more than 30 hs. since the migration began, other VMs took 
approximately 1-1.5 hours to fully migrate a disk, so this seems to be 
stalled.


The bad thing is that I can't find a way to "unstall" it. Disks are in 
a perpetual "migrating" status and there's no way to stop the 
migration (at least from the webadmin). I don't actually care if 
stopping the migration breaks those 5 machines since they are 
disposable, I just need to stop that event. I already tried restarting 
the ovirt-engine and it didn't work.


Log doesn't seem to provide nothing relevant.

Is there a way to do that? I wouldn't mind if I need to modify some 
record directly into the DB.


Thanks!

Nicolás
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cleanup illegal snapshot

2016-10-09 Thread Markus Stockhausen 
Hi Ala,

that did not help. VDSM log tells me that the delta qcow2 file is missing:

Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 873, in _run
return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 49, in wrapper
res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 3162, in getVolumeInfo
volUUID=volUUID).getInfo()
  File "/usr/share/vdsm/storage/sd.py", line 457, in produceVolume
volUUID)
  File "/usr/share/vdsm/storage/fileVolume.py", line 58, in __init__
volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/volume.py", line 181, in __init__
self.validate()
  File "/usr/share/vdsm/storage/volume.py", line 194, in validate
self.validateVolumePath()
  File "/usr/share/vdsm/storage/fileVolume.py", line 540, in validateVolumePath
raise se.VolumeDoesNotExist(self.volUUID)
VolumeDoesNotExist: Volume does not exist: 
(u'c277351d-e2b1-4057-aafb-55d4b607ebae',)
...
Thread-196::ERROR::2016-10-09 19:31:07,037::utils::739::root::(wrapper) 
Unhandled exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in wrapper
return f(*a, **kw)
  File "/usr/share/vdsm/virt/vm.py", line 5264, in run
self.update_base_size()
  File "/usr/share/vdsm/virt/vm.py", line 5257, in update_base_size
self.drive.imageID, topVolUUID)
  File "/usr/share/vdsm/virt/vm.py", line 5191, in _getVolumeInfo
(domainID, volumeID))
StorageUnavailableError: Unable to get volume info for domain 
47202573-6e83-42fd-a274-d11f05eca2dd volume c277351d-e2b1-4057-aafb-55d4b607ebae

Do you have any idea?

Markus


Von: Ala Hino [ah...@redhat.com]
Gesendet: Donnerstag, 6. Oktober 2016 12:29
An: Markus Stockhausen
Betreff: Re: [ovirt-users] Cleanup illegal snapshot

Indeed, retry live merge. There is no harm in retrying live merge. As 
mentioned, if the image deleted at storage side, retrying live merge should 
clean the engine side.

On Thu, Oct 6, 2016 at 1:06 PM, Markus Stockhausen 
mailto:stockhau...@collogia.de>> wrote:
Hi,

we are on OVirt 4.0.4. As explained the situation is as follows:

- On Disk we have the base image and the delata qcow2 file
- Qemu runs only on the base image
- The snapshot in Qemu is tagged as illegal

So you say: "Just retry a live merge and everything will cleanup."
Did I get it right?

Markus

---

Von: Ala Hino [ah...@redhat.com]
Gesendet: Donnerstag, 6. Oktober 2016 11:21
An: Markus Stockhausen
Cc: Ovirt Users; Nir Soffer; Adam Litke

Betreff: Re: [ovirt-users] Cleanup illegal snapshot

Hi Markus,

What's the version that you are using?
In oVirt 3.6.6, illegal snapshots could be removed by retrying to live merge 
them again. Assuming the previous live merge of the snapshot successfully 
completed but the engine failed to get the result, the second live merge should 
do the necessary cleanups at the engine side. See 
https://bugzilla.redhat.com/1323629

Hope this helps,
Ala

On Thu, Oct 6, 2016 at 11:53 AM, Markus Stockhausen 
mailto:stockhau...@collogia.de>> wrote:
Hi Ala,

> Von: Adam Litke [ali...@redhat.com]
> Gesendet: Freitag, 30. September 2016 15:54
> An: Markus Stockhausen
> Cc: Ovirt Users; Ala Hino; Nir Soffer
> Betreff: Re: [ovirt-users] Cleanup illegal snapshot
>
> On 30/09/16 05:47 +, Markus Stockhausen wrote:
> >Hi,
> >
> >if a OVirt snapshot is illegal we might have 2 situations.
> >
> >1) qemu is still using it - lsof shows qemu access to the base raw and the
> >delta qcow2 file. -> E.g. a previous live merge failed. In the past we
> >successfully solved that situation by setting the status of the delta image
> >in the database to OK.
> >
> >2) qemu is no longer using it. lsof shows qemu access only to the the base
> >raw file -> E.g. a previous live merge succeded in qemu but Ovirt did not
> >recognize.
> >
> >How to clean up the 2nd situation?
>
> It seems that you will have to first clean up the engine database to
> remove references to the snapshot that no longer exists.  Then you
> will need to remove the unused qcow2 volume.
>
> Unfortunately I cannot provide safe instructions for modifying the
> database but maybe Ala Hino (added to CC:) will be able to help with
> that.

Do you have some tip for me?

>
> One you have fixed the DB you should be able to delete the volume
> using a vdsm verb on the SPM host:
>
> # vdsClient -s 0 deleteVolume



Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

Über das Internet versandte E

Re: [ovirt-users] Unable to get HE up after update

2016-10-09 Thread Susinthiran Sithamparanathan 
Sure, here it is: https://my.owndrive.com/index.php/s/MFoFyKJVLjzezey

On Sun, Oct 9, 2016 at 3:19 PM, Doron Fediuck  wrote:

> Can you please provide the HA agent logs?
>
> On Sun, Oct 9, 2016 at 1:57 PM, Susinthiran Sithamparanathan <
> chesu...@gmail.com> wrote:
>
>> Hi,
>> i've been discussing this issue over at IRC (#ovirt on irc.oftc.net))
>> and was suggested to send an email with logs the ML.
>>
>> The problem i have is that the HE is a loop getting up and down ( ( i
>> assume it's the HA trying to get it up) after upgrade to oVirt 4. I have a
>> couple of VMs i use daily with SPICE and remoteviewer and i hope to get
>> them up and running again. Due to this, i've put it in global maintenance
>> mode.
>> I'm attaching the server log in the hope of getting some help and can
>> provide more details if needed to debug the issue further.
>>
>> The log is too big for fpaste so it's to be found here:
>> https://my.owndrive.com/index.php/s/Gk4De1jy9fWmFa8 as well as attached
>> here.
>>
>>
>> Thanks!
>>
>>
>> --
>>
>> Susinthiran Sithamparanathan
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>


-- 

Susinthiran Sithamparanathan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to get HE up after update

2016-10-09 Thread Doron Fediuck 
Can you please provide the HA agent logs?

On Sun, Oct 9, 2016 at 1:57 PM, Susinthiran Sithamparanathan <
chesu...@gmail.com> wrote:

> Hi,
> i've been discussing this issue over at IRC (#ovirt on irc.oftc.net)) and
> was suggested to send an email with logs the ML.
>
> The problem i have is that the HE is a loop getting up and down ( ( i
> assume it's the HA trying to get it up) after upgrade to oVirt 4. I have a
> couple of VMs i use daily with SPICE and remoteviewer and i hope to get
> them up and running again. Due to this, i've put it in global maintenance
> mode.
> I'm attaching the server log in the hope of getting some help and can
> provide more details if needed to debug the issue further.
>
> The log is too big for fpaste so it's to be found here:
> https://my.owndrive.com/index.php/s/Gk4De1jy9fWmFa8 as well as attached
> here.
>
>
> Thanks!
>
>
> --
>
> Susinthiran Sithamparanathan
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Decommissioning etherpad and old wiki

2016-10-09 Thread Dan Kenigsberg 
On Thu, Oct 06, 2016 at 01:13:47PM +0300, Dan Kenigsberg wrote:
> On Thu, Oct 06, 2016 at 05:53:54PM +0900, Marc Dequènes (Duck) wrote:
> > Quack,
> > 
> > The wiki content was already converted into the website, and remaining
> > broken links & co were fixed (thanks Garrett). It was merely kept in
> > case some content was forgotten (read-only).
> > 
> > The Etherpad was barely used and a pain to upgrade/maintain, so the
> > infra team with the last remaining user decided to close it.
> > 
> > They are to be removed soon. In fact we already stopped them to track
> > the remaining users, and no one complained. It can be restarted on
> > demand before the removal date.
> > 
> > On 2016-10-26 the resources will be purged. Backup has been made, so
> > nothing is lost but unless there is a good reason it won't be used.
> > 
> > Btw, the wiki@ mailing-list was unused and is now read-only.
> 
> How much resources did old.ovirt.org take? I many occasions, the
> migration to the new git-based site rendered pages almost unreadable. In
> such occasions, I loved going back to old.ovirt.org, to see how a
> feature page was meant to look like.

As a recent example, we got
[Bug 1383047] New: No wiki pages on Important Vdsm wiki pages
opened. I might be able to guess what this link used to look like, but
seeing is much better.

> 
> Can we keep old.ovirt.org for another year? I see that it is currently
> down.

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance 
downtime or capacity problems. Please try again later.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] documentation change suggestion / question

2016-10-09 Thread Yedidyah Bar David 
On Sun, Oct 9, 2016 at 11:26 AM, Karli Sjöberg  wrote:
>
> Den 8 okt. 2016 19:15 skrev Charles Kozler :
>>
>> Googling "ovirt windows agent" this is the first link that pops up:
>> http://www.ovirt.org/documentation/internal/guest-agent/guest-agent-for-windows/

Patches are welcome :-)

>>
>> This doc seems non-intuitive and over complicated
>>
>> Specifically, the RedHat documentation that is 4 links below is simple as
>> "install this package and mount the iso":
>> https://community.redhat.com/blog/2015/05/how-to-install-and-use-ovirts-windows-guest-tools/

That's true for oVirt as well, since 3.5. Please check this:

https://www.ovirt.org/develop/release-management/features/engine/windows-guest-tools/

>>
>> The former was updated as early as June of this year
>>
>> 1.) The RedHat document worked for me so I dont think oVirt 4.x cant use
>> the same
>> 2.) Why have separate areas of documentation that are so different from
>> each other? This has caused me issues in the past whereby I found RH docs
>> that were much more clear and concise

I guess one of the main reasons is that this particular part, the windows
tools iso, is one of the biggest differences between oVirt and RHV.

RHV uses InstallShield to create the installer, and RHV uses NSIS.

The installers are completely unrelated.

Other than that, the iso content is similar (drivers, agents etc).

>
> That's because all oVirt documentation is community driven. This specific
> page was written by a guy I happen to know quite well (I wrote it):)

Thanks! :-)

>
> This was written back when there was no easy to install package, where you
> had to do that by hand, and if you want to, you still can, the method still
> works. But I agree that if there's an easier way today, I think we should go
> with that first and keep this compiling method as the fallback.
>
>> 3.) Is there anyone who might want to merge RH docs with oVirt docs where
>> the RH docs are better than oVirt?
>
> Hoping someone @RH can answer this, because I don't know if I'm allowed to
> do that?
>
> /K
>
>>
>> Thanks so much for providing such a great product! I just feel sometimes
>> the docs are a little more developer-centric whereas the RedHat docs are
>> more easily readable
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] documentation change suggestion / question

2016-10-09 Thread Karli Sjöberg 

Den 8 okt. 2016 19:15 skrev Charles Kozler :
>
> Googling "ovirt windows agent" this is the first link that pops up: 
> http://www.ovirt.org/documentation/internal/guest-agent/guest-agent-for-windows/
>
> This doc seems non-intuitive and over complicated
>
> Specifically, the RedHat documentation that is 4 links below is simple as 
> "install this package and mount the iso": 
> https://community.redhat.com/blog/2015/05/how-to-install-and-use-ovirts-windows-guest-tools/
>
> The former was updated as early as June of this year
>
> 1.) The RedHat document worked for me so I dont think oVirt 4.x cant use the 
> same
> 2.) Why have separate areas of documentation that are so different from each 
> other? This has caused me issues in the past whereby I found RH docs that 
> were much more clear and concise

That's because all oVirt documentation is community driven. This specific page 
was written by a guy I happen to know quite well (I wrote it):)

This was written back when there was no easy to install package, where you had 
to do that by hand, and if you want to, you still can, the method still works. 
But I agree that if there's an easier way today, I think we should go with that 
first and keep this compiling method as the fallback.

> 3.) Is there anyone who might want to merge RH docs with oVirt docs where the 
> RH docs are better than oVirt?

Hoping someone @RH can answer this, because I don't know if I'm allowed to do 
that?

/K

>
> Thanks so much for providing such a great product! I just feel sometimes the 
> docs are a little more developer-centric whereas the RedHat docs are more 
> easily readable
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm ssl errors

2016-10-09 Thread Oved Ourfali 
Fixed in "Bug 1371515 - Exception on GetUserProfileQuery (unknown cause) :
"The column name user_portal_vm_auto_login was not found in this ResultSet".
Please upgrade to latest 4.0.

On Sun, Oct 9, 2016 at 10:47 AM, Piotr Kliczewski <
piotr.kliczew...@gmail.com> wrote:

> Gianluca,
>
> In the log provided I only see plenty of:
>
> 2016-10-07 23:24:43,159 ERROR
> [org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
> Query 'GetUserProfileQuery' failed: PreparedStatementCallback; bad SQL
> grammar [select * from  getuserprofilebyuserid(?)]; nested exception
> is org.postgresql.util.PSQLException: The column name
> user_portal_vm_auto_login was not found in this ResultSet.
> 2016-10-07 23:24:43,159 ERROR
> [org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
> Exception: org.springframework.jdbc.BadSqlGrammarException:
> PreparedStatementCallback; bad SQL grammar [select * from
> getuserprofilebyuserid(?)]; nested exception is
> org.postgresql.util.PSQLException: The column name
> user_portal_vm_auto_login was not found in this ResultSet.
>
> This could be not related but I do not see any other exception in there.
>
> @Eli can you please take a look?
>
> Thanks,
> Piotr
>
> On Fri, Oct 7, 2016 at 11:28 PM, Gianluca Cecchi
>  wrote:
> >
> > On Fri, Oct 7, 2016 at 10:14 PM, Piotr Kliczewski 
> > wrote:
> >>
> >> Gianluca,
> >>
> >> Please share the engine log. We shoukd find more info about the issue
> >> there.
> >>
> >> Thanks,
> >> Piotr
> >>
> >>
> >
> > here it is
> > https://drive.google.com/file/d/0BwoPbcrMv8mvQlVwVDlGTVEtR00/
> view?usp=sharing
> >
> > Gianluca
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsm ssl errors

2016-10-09 Thread Piotr Kliczewski 
Gianluca,

In the log provided I only see plenty of:

2016-10-07 23:24:43,159 ERROR
[org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
Query 'GetUserProfileQuery' failed: PreparedStatementCallback; bad SQL
grammar [select * from  getuserprofilebyuserid(?)]; nested exception
is org.postgresql.util.PSQLException: The column name
user_portal_vm_auto_login was not found in this ResultSet.
2016-10-07 23:24:43,159 ERROR
[org.ovirt.engine.core.bll.GetUserProfileQuery] (default task-2) []
Exception: org.springframework.jdbc.BadSqlGrammarException:
PreparedStatementCallback; bad SQL grammar [select * from
getuserprofilebyuserid(?)]; nested exception is
org.postgresql.util.PSQLException: The column name
user_portal_vm_auto_login was not found in this ResultSet.

This could be not related but I do not see any other exception in there.

@Eli can you please take a look?

Thanks,
Piotr

On Fri, Oct 7, 2016 at 11:28 PM, Gianluca Cecchi
 wrote:
>
> On Fri, Oct 7, 2016 at 10:14 PM, Piotr Kliczewski 
> wrote:
>>
>> Gianluca,
>>
>> Please share the engine log. We shoukd find more info about the issue
>> there.
>>
>> Thanks,
>> Piotr
>>
>>
>
> here it is
> https://drive.google.com/file/d/0BwoPbcrMv8mvQlVwVDlGTVEtR00/view?usp=sharing
>
> Gianluca
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users