[ovirt-users] Can't add host - Failed to read hardware information

2019-05-15 Thread David Pinkerton 
 {}
jsonrpc.Executor/4::ERROR::2016-10-07
20:45:32,673::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
jsonrpc.Executor/4::INFO::2016-10-07
20:45:32,680::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC
call Host.getHardwareInfo failed (error 57) in 0.11 seconds
jsonrpc.Executor/6::DEBUG::2016-10-07
20:45:33,783::__init__::530::jsonrpc.JsonRpcServer::(_handle_request)
Calling 'Host.getCapabilities' in bridge with {}
MainThread::DEBUG::2016-10-07 20:45:36,211::vdsm::73::vds::(sigtermHandler)
Received signal 15





I'm also seeing segfaults in supervdsm on the host's console.


-- 

David Pinkerton
+61-488-904-232
 <http://apac.redhat.com/>

--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PUJY6V4FTPQB2U7PHYTREPR6DT3WZ5Y6/

[ovirt-users] Fwd: Invalid status on Data Center XXX. Setting status to non responsive.

2017-03-28 Thread David Pinkerton 
Thread-63::DEBUG::2017-03-28 22:06:10,868::resourceManager:
:628::Storage.ResourceManager::(releaseResource) Trying to release resource
'Storage.a1428935-1f17-4652-bff9-abc65b3115d3'
Thread-63::DEBUG::2017-03-28 22:06:10,868::resourceManager:
:647::Storage.ResourceManager::(releaseResource) Released resource
'Storage.a1428935-1f17-4652-bff9-abc65b3115d3' (0 active users)
Thread-63::DEBUG::2017-03-28 22:06:10,868::resourceManager:
:653::Storage.ResourceManager::(releaseResource) Resource
'Storage.a1428935-1f17-4652-bff9-abc65b3115d3' is free, finding out if
anyone is waiting for it.
Thread-63::DEBUG::2017-03-28 22:06:10,868::resourceManager:
:661::Storage.ResourceManager::(releaseResource) No one is waiting for
resource 'Storage.a1428935-1f17-4652-bff9-abc65b3115d3', Clearing records.
Thread-63::DEBUG::2017-03-28 22:06:10,869::resourceManager:
:628::Storage.ResourceManager::(releaseResource) Trying to release resource
'Storage.upgrade_28111e03-5618-4d97-a7e4-5eee8db14c18'
Thread-63::DEBUG::2017-03-28 22:06:10,869::resourceManager:
:647::Storage.ResourceManager::(releaseResource) Released resource
'Storage.upgrade_28111e03-5618-4d97-a7e4-5eee8db14c18' (0 active users)
Thread-63::DEBUG::2017-03-28 22:06:10,869::resourceManager:
:653::Storage.ResourceManager::(releaseResource) Resource
'Storage.upgrade_28111e03-5618-4d97-a7e4-5eee8db14c18' is free, finding out
if anyone is waiting for it.
Thread-63::DEBUG::2017-03-28 22:06:10,869::resourceManager:
:661::Storage.ResourceManager::(releaseResource) No one is waiting for
resource 'Storage.upgrade_28111e03-5618-4d97-a7e4-5eee8db14c18', Clearing
records.
Thread-63::ERROR::2017-03-28
22:06:10,869::utils::375::Storage.StoragePool::(wrapper)
Unhandled exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 372, in
wrapper
return f(*a, **kw)
  File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 177, in
run
return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
78, in wrapper
return method(self, *args, **kwargs)
  File "/usr/share/vdsm/storage/sp.py", line 207, in _upgradePoolDomain
self._finalizePoolUpgradeIfNeeded()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
76, in wrapper
raise SecureError("Secured object is not in safe state")
SecureError: Secured object is not in safe state




-- 

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 <+61%20488%20904%20232>
Email: david.pinker...@redhat.com
Web: http://apac.redhat.com/ <http://apac.redhat.com/>




-- 

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/ <http://apac.redhat.com/>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Help

2017-03-28 Thread David Pinkerton 
Had a power outage last night and my UPS died..


All screens flick (Cluster, Hosts, Storage, Virtual Machine) and then go
blank hen I click on the tabs in the manager

Error message: Invalid status on Data Center XXX. Setting status to non
responsive.


Storage is ISCSI - all hosts are logged in and I can see LUNS via blkid






-- 

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/ <http://apac.redhat.com/>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

2016-10-13 Thread David Pinkerton 
Good News.

I installed the fedora 24 version of python-dmidecode and was able to
successfully add the host to my cluster...

Thanks you to everyone who looked at this.  I owe you a beer or at least
some reward points   :-)



On Thu, Oct 13, 2016 at 7:28 PM, Martin Polednik 
wrote:

> On 13/10/16 09:01 +0300, Dan Kenigsberg wrote:
>
>> On Thu, Oct 13, 2016 at 11:52:17AM +1100, David Pinkerton wrote:
>>
>>> Nir,
>>>
>>> Looks like its crashing on the dmidecode system call.
>>>
>>> I've attached the output from gbd as well as a dmidecode text dump,
>>> dmidecode binary dump and each keywords run individually.
>>>
>>> >From the keywords it look like my dmi info is corrupted.  I have
>>> download a
>>> AMI dmi editor but this only allows access to limited fields.  Do you
>>> know
>>> another tools to rewrite the dmi info?
>>>
>>
>> I don't. But whatever is inside your dmi, dmidecode must not crash.
>> Which version of python-dmidecode do you have installed?
>> Would you open a bug against it?
>>
>
> This is really unfortunate - I've reproduced the issue with the
> attached dump and it's python-dmidecode that crashes. The issue is
> actually fixed upstream, but the version at least in RHEL does not
> contain the fix.
>
> RHEL version:
> python-dmidecode-3.10.13-11.el7.x86_64
>
> works with (actual upstream):
> python-dmidecode-3.12.2-1.el7.x86_64
> (actually it's ~6 line change in dmioem.c)
>
> VDSM output:
> # vdsClient 0 getVdsHardwareInfo
>systemFamily = 'To Be Filled By O.E.M.'
>systemManufacturer = 'Supermicro'
>systemProductName = 'H8DM8-2'
>systemSerialNumber = '1234567890'
>systemUUID = '00020003-0004-0005-0006-000700080009'
>systemVersion = '1234567890'
>
> Although the upstream version of python-dmidecode is able to deal with
> improper DMI tables, I can't say what else will/will not behave correctly.
>
> mpolednik
>
>
> I believe that its maintainers would appriace a simple reproducer, that
>> does not involve ovirt or Vdsm. See if you can simplify the code in
>>
>> def __leafDict(d):
>>ret = {}
>>for k, v in d.iteritems():
>>if isinstance(v, dict):
>>ret.update(__leafDict(v))
>>else:
>>ret[k] = v
>>return ret
>>
>>
>> def getAllDmidecodeInfo():
>>import dmidecode
>>
>>myLeafDict = {}
>>for k in ('system', 'bios', 'cache', 'processor', 'chassis', 'memory'):
>>myLeafDict[k] = __leafDict(getattr(dmidecode, k)())
>>return myLeafDict
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>


-- 

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/ <http://apac.redhat.com/>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

2016-10-13 Thread David Pinkerton 
python-dmidecode-3.10.13-11.el7.x86_64

I cut and pasted your python code into a file and ran python file  no
workie

I did find the attached dmidump.py on github.  It segfaults after printing
bios on line 64.

Also attached is a dump from the AMIDEDOS utility.

Happy to do whatever is required to fix this issue..  I have a couple of
months of nights and weekends invested so far...  what's a couple more.  :)






On Thu, Oct 13, 2016 at 5:01 PM, Dan Kenigsberg  wrote:

> On Thu, Oct 13, 2016 at 11:52:17AM +1100, David Pinkerton wrote:
> > Nir,
> >
> > Looks like its crashing on the dmidecode system call.
> >
> > I've attached the output from gbd as well as a dmidecode text dump,
> > dmidecode binary dump and each keywords run individually.
> >
> > >From the keywords it look like my dmi info is corrupted.  I have
> download a
> > AMI dmi editor but this only allows access to limited fields.  Do you
> know
> > another tools to rewrite the dmi info?
>
> I don't. But whatever is inside your dmi, dmidecode must not crash.
> Which version of python-dmidecode do you have installed?
> Would you open a bug against it?
>
> I believe that its maintainers would appriace a simple reproducer, that
> does not involve ovirt or Vdsm. See if you can simplify the code in
>
> def __leafDict(d):
> ret = {}
> for k, v in d.iteritems():
> if isinstance(v, dict):
> ret.update(__leafDict(v))
> else:
> ret[k] = v
> return ret
>
>
> def getAllDmidecodeInfo():
> import dmidecode
>
> myLeafDict = {}
> for k in ('system', 'bios', 'cache', 'processor', 'chassis', 'memory'):
> myLeafDict[k] = __leafDict(getattr(dmidecode, k)())
> return myLeafDict
>



-- 

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/ <http://apac.redhat.com/>
[SMBIOS Header]
===
Name  : SMBIOS SignatureStyle : 4 BYTEs
Data  : _SM_

Name  : SMBIOS Checksum Style : BYTE
Data  : 7Fh

Name  : SMBIOS Table Length Style : BYTE
Data  : 31 bytes

Name  : SMBIOS Version  Style : WORD
Data  : 2.4

Name  : SMBIOS Max. Struc. Size Style : WORD
Data  : 254 bytes

Name  : SMBIOS Point Revision   Style : BYTE
Data  : 00h

Name  : SMBIOS Formatted Area   Style : 5 BYTEs
Data  : 00 00 00 00 00h

Name  : DMI Signature   Style : 5 BYTEs
Data  : _DMI_

Name  : DMI ChecksumStyle : BYTE
Data  : 49h

Name  : DMI Table LengthStyle : WORD
Data  : 2911 bytes

Name  : DMI Table Address   Style : DWORD
Data  : 000FC5B0h

Name  : Number of SMBIOS Stuctures  Style : WORD
Data  : 49

Name  : DMI Revisiion   Style : BYTE
Data  : 0.0

[Type 000] -- BIOS Information
===
Name  : Struc. Length   Style : BYTE
Data  : 18h

Name  : Struc. Handle   Style : WORD
Data  : h

Name  : BIOS Vendor Style : STRING
Data  : "American Megatrends Inc."

Name  : BIOS VersionStyle : STRING
Data  : "080014"

Name  : BIOS Starting Add. Seg. Style : WORD
Data  : F000h

Name  : BIOS Release Date   Style : STRING
Data  : "10/22/2009"

Name  : BIOS ROM Size   Style : BYTE
Data  : 0Fh
-- 1024 KB

Name  : BIOS CharacteristicsStyle : QWORD
Data  :  0001 7F8B DE90h
-- Bit.04:ISA is supported
-- Bit.07:PCI is Reserved
-- Bit.09:Plug and Play is supported
-- Bit.10:APM is supported
-- Bit.11:BIOS is Upgradeable(Flash)
-- Bit.12:BIOS shadowing is allowed
-- Bit.14:ESCD support is available
-- Bit.15:Boot from CD is supported
-- Bit.16:Selectable Boot is supported
-- Bit.17:BIOS ROM is socketed
-- Bit.19:EDD(Enhanced Disk Drive) Specification is supported
-- Bit.23:Int 13h - 5.25" / 1.2MB Floppy Services are supported

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

2016-10-12 Thread David Pinkerton 
Nir,

Looks like its crashing on the dmidecode system call.

I've attached the output from gbd as well as a dmidecode text dump,
dmidecode binary dump and each keywords run individually.

>From the keywords it look like my dmi info is corrupted.  I have download a
AMI dmi editor but this only allows access to limited fields.  Do you know
another tools to rewrite the dmi info?


Thanks so much for your help.

Cheers,


On Thu, Oct 13, 2016 at 5:34 AM, Nir Soffer  wrote:

> On Tue, Oct 11, 2016 at 11:59 PM, David Pinkerton 
> wrote:
> > Logs attached
>
> According vdsm.log and supervdsm.log, each time vdsm try to call
> getHardwareInfo,
> supervdsm show the start of the call and then it show no logs for 10
> seconds,
> and than we see the startup message.
>
> So it seems that supervdsm is crashing each time it try to invoke dmidecode
> code.
>
> To dig deeper, I suggest you try to run the relevant code from the
> shell. If this
> code crash, we will see the details in the shell, and we can also run the
> python
> shell in gdb to debug this.
>
> Try this:
>
> 1. Open a python shell as root
>
> $ sudo python
>
> 2. In the shell, type this
>
> >>> from vdsm import dmidecodeUtil
> >>> dmidecodeUtil.getHardwareInfoStructure()
>
> If at this point the the python shell crash, please try:
>
> 1. Install python debug-info packages:
>
> $ sudo debuginfo-install -y python
>
> 2. Start python in gdb
>
> $ sudo gdb python
>
> 3. In the gdb shell, run python
>
> (gdb) run
>
> Python shell will show, type the code above again.
>
> If this crash in gdb, please type this in the gdb shell:
>
> (gdb) thread apply all bt full
>
>
> Nir
>
> >
> > On Mon, Oct 10, 2016 at 4:59 PM, Nir Soffer  wrote:
> >>
> >> 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-
> 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,

[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/ <http://apac.redhat.com/>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Can't add host - Failed to read hardware information

2016-10-07 Thread David Pinkerton 
 {}
jsonrpc.Executor/4::ERROR::2016-10-07
20:45:32,673::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
jsonrpc.Executor/4::INFO::2016-10-07
20:45:32,680::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC
call Host.getHardwareInfo failed (error 57) in 0.11 seconds
jsonrpc.Executor/6::DEBUG::2016-10-07
20:45:33,783::__init__::530::jsonrpc.JsonRpcServer::(_handle_request)
Calling 'Host.getCapabilities' in bridge with {}
MainThread::DEBUG::2016-10-07 20:45:36,211::vdsm::73::vds::(sigtermHandler)
Received signal 15





I'm also seeing segfaults in supervdsm on the host's console.


-- 

David Pinkerton
+61-488-904-232
 <http://apac.redhat.com/>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users