Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Jonathan Sherman 
Bug 1315435 Submitted.  Let me know if there's anything else I can do to
help.

On Mon, Mar 7, 2016 at 12:04 PM, Dan Kenigsberg  wrote:

> On Mon, Mar 07, 2016 at 11:45:27AM -0500, Jonathan Sherman wrote:
> > The SMBIOS settings were indeed indeed the issue that was blocking me.  I
> > investigated how to configure the SMBIOS settings and now restore-nets
> > works, and I'm getting past where I was failing on the hosted-engine
> > --deploy.
> >
> > FYI, I had to download the "Intel Integrator Toolkit" (which is now EOL)
> > and create a custom BIOS to add those settings in for my system, which is
> > an Intel NUC DN2820FYKH.
> >
> > I am happy to back this out and test any changes if you'd like, but this
> > has gotten me to where I can continue oVirt testing for now.  I'll likely
> > be reinstalling a few times along the way to polish my documentation, so
> > let me know if you want me to revert my BIOS and test anything.
> >
> > Thanks all!
> > -js
> >
> > On Mon, Mar 7, 2016 at 11:22 AM, Martin Polednik 
> > wrote:
> >
> > > On 07/03/16 11:09 -0500, Jonathan Sherman wrote:
> > >
> > >> Thanks for your time on this Dan!
> > >>
> > >> The output from the hostdev looks like it may be unparseable, so I'm
> > >> hoping
> > >> this is the issue (and that it can be easily remedied).
> > >>
> > >> I've also create a log of the other items you asked for, available at:
> > >> https://www.dropbox.com/s/qh0yw1ptpivpatm/typescript?dl=0
> > >>
> > >> [root@ovirt01 vdsm]# vdsm-tool restore-nets
> > >> 
> > >>  computer
> > >>  
> > >>�
> > >>
> > >>  �
> > >>  �
> > >>  �
> > >>  d6a3e3c1-c5cb-42e9-a54c-ff8d0df91722
> > >>
> > >>
> > >>  Intel Corp.
> > >>  FYBYT10H.86A.0052.2015.0923.1845
> > >>  09/23/2015
> > >>
> > >>  
> > >> 
> > >>
> > >
> > > That seems to be the issue. Even bigger issue is that we can
> > > not skip this device easily, as it is the root of device tree and must
> > > be present in database.
> > >
> > > I can think of logging the exception but letting the call go through
> > > and create a hook to fake a (minimal) device tree. Dan, what do you
> think?
>
>
> But why isn't this a valid xml, Martin? I suspect that we need to
> utf-8-decode nodedev-xml before using them in Vdsm, similar to what we
> do with domain-xml? (consider Klingon characters in the 
> element).
>
> In any case, this issue merits a bug - could you open it, Jonathan, and
> attach relevant data to it?
>
> Regards,
> Dan.
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Dan Kenigsberg 
On Mon, Mar 07, 2016 at 11:45:27AM -0500, Jonathan Sherman wrote:
> The SMBIOS settings were indeed indeed the issue that was blocking me.  I
> investigated how to configure the SMBIOS settings and now restore-nets
> works, and I'm getting past where I was failing on the hosted-engine
> --deploy.
> 
> FYI, I had to download the "Intel Integrator Toolkit" (which is now EOL)
> and create a custom BIOS to add those settings in for my system, which is
> an Intel NUC DN2820FYKH.
> 
> I am happy to back this out and test any changes if you'd like, but this
> has gotten me to where I can continue oVirt testing for now.  I'll likely
> be reinstalling a few times along the way to polish my documentation, so
> let me know if you want me to revert my BIOS and test anything.
> 
> Thanks all!
> -js
> 
> On Mon, Mar 7, 2016 at 11:22 AM, Martin Polednik 
> wrote:
> 
> > On 07/03/16 11:09 -0500, Jonathan Sherman wrote:
> >
> >> Thanks for your time on this Dan!
> >>
> >> The output from the hostdev looks like it may be unparseable, so I'm
> >> hoping
> >> this is the issue (and that it can be easily remedied).
> >>
> >> I've also create a log of the other items you asked for, available at:
> >> https://www.dropbox.com/s/qh0yw1ptpivpatm/typescript?dl=0
> >>
> >> [root@ovirt01 vdsm]# vdsm-tool restore-nets
> >> 
> >>  computer
> >>  
> >>�
> >>
> >>  �
> >>  �
> >>  �
> >>  d6a3e3c1-c5cb-42e9-a54c-ff8d0df91722
> >>
> >>
> >>  Intel Corp.
> >>  FYBYT10H.86A.0052.2015.0923.1845
> >>  09/23/2015
> >>
> >>  
> >> 
> >>
> >
> > That seems to be the issue. Even bigger issue is that we can
> > not skip this device easily, as it is the root of device tree and must
> > be present in database.
> >
> > I can think of logging the exception but letting the call go through
> > and create a hook to fake a (minimal) device tree. Dan, what do you think?


But why isn't this a valid xml, Martin? I suspect that we need to
utf-8-decode nodedev-xml before using them in Vdsm, similar to what we
do with domain-xml? (consider Klingon characters in the 
element).

In any case, this issue merits a bug - could you open it, Jonathan, and
attach relevant data to it?

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

Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Jonathan Sherman 
The SMBIOS settings were indeed indeed the issue that was blocking me.  I
investigated how to configure the SMBIOS settings and now restore-nets
works, and I'm getting past where I was failing on the hosted-engine
--deploy.

FYI, I had to download the "Intel Integrator Toolkit" (which is now EOL)
and create a custom BIOS to add those settings in for my system, which is
an Intel NUC DN2820FYKH.

I am happy to back this out and test any changes if you'd like, but this
has gotten me to where I can continue oVirt testing for now.  I'll likely
be reinstalling a few times along the way to polish my documentation, so
let me know if you want me to revert my BIOS and test anything.

Thanks all!
-js

On Mon, Mar 7, 2016 at 11:22 AM, Martin Polednik 
wrote:

> On 07/03/16 11:09 -0500, Jonathan Sherman wrote:
>
>> Thanks for your time on this Dan!
>>
>> The output from the hostdev looks like it may be unparseable, so I'm
>> hoping
>> this is the issue (and that it can be easily remedied).
>>
>> I've also create a log of the other items you asked for, available at:
>> https://www.dropbox.com/s/qh0yw1ptpivpatm/typescript?dl=0
>>
>> [root@ovirt01 vdsm]# vdsm-tool restore-nets
>> 
>>  computer
>>  
>>�
>>
>>  �
>>  �
>>  �
>>  d6a3e3c1-c5cb-42e9-a54c-ff8d0df91722
>>
>>
>>  Intel Corp.
>>  FYBYT10H.86A.0052.2015.0923.1845
>>  09/23/2015
>>
>>  
>> 
>>
>
> That seems to be the issue. Even bigger issue is that we can
> not skip this device easily, as it is the root of device tree and must
> be present in database.
>
> I can think of logging the exception but letting the call go through
> and create a hook to fake a (minimal) device tree. Dan, what do you think?
>
> mpolednik
>
>
> Traceback (most recent call last):
>>  File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in 
>>restore(args)
>>  File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in restore
>>_restore_sriov_numvfs()
>>  File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
>> _restore_sriov_numvfs
>>sriov_devices = _get_sriov_devices()
>>  File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
>> _get_sriov_devices
>>devices = hostdev.list_by_caps()
>>  File "/usr/share/vdsm/hostdev.py", line 177, in list_by_caps
>>libvirt_devices = _get_devices_from_libvirt()
>>  File "/usr/share/vdsm/hostdev.py", line 162, in _get_devices_from_libvirt
>>for device in libvirtconnection.get().listAllDevices(0))
>>  File "/usr/share/vdsm/hostdev.py", line 162, in 
>>for device in libvirtconnection.get().listAllDevices(0))
>>  File "/usr/share/vdsm/hostdev.py", line 109, in _parse_device_params
>>devXML = etree.fromstring(device_xml)
>>  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
>>parser.feed(text)
>>  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
>>self._raiseerror(v)
>>  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
>> _raiseerror
>>raise err
>> xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 4,
>> column 13
>> Traceback (most recent call last):
>>  File "/bin/vdsm-tool", line 219, in main
>>return tool_command[cmd]["command"](*args)
>>  File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
>> 41, in restore_command
>>exec_restore(cmd)
>>  File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
>> 54, in exec_restore
>>raise EnvironmentError('Failed to restore the persisted networks')
>> EnvironmentError: Failed to restore the persisted networks
>>
>> On Mon, Mar 7, 2016 at 10:37 AM, Dan Kenigsberg 
>> wrote:
>>
>> On Mon, Mar 07, 2016 at 03:16:06PM +0200, Yedidyah Bar David wrote:
>>> > On Mon, Mar 7, 2016 at 3:01 PM, Jonathan Sherman 
>>> wrote:
>>> > > Didi -
>>> > >
>>> > > The vdsmd service error is what led me to the vdsm-tool restore-nets
>>> > > concern.  See the chain of errors below (along with the other details
>>> you
>>> > > requested.)
>>> >
>>> > Thanks.
>>> >
>>> > Changing subject and adding Dan.
>>>
>>> > >
>>> > > [root@ovirt01 log]# vdsm-tool restore-nets
>>> > > Traceback (most recent call last):
>>> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in
>>> 
>>> > > restore(args)
>>> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in
>>> restore
>>> > > _restore_sriov_numvfs()
>>> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
>>> > > _restore_sriov_numvfs
>>> > > sriov_devices = _get_sriov_devices()
>>> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
>>> > > _get_sriov_devices
>>> > > devices = hostdev.list_by_caps()
>>> > >   File "/usr/share/vdsm/hostdev.py", line 175, in list_by_caps
>>> > > libvirt_devices =

Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Martin Polednik 

On 07/03/16 11:09 -0500, Jonathan Sherman wrote:

Thanks for your time on this Dan!

The output from the hostdev looks like it may be unparseable, so I'm hoping
this is the issue (and that it can be easily remedied).

I've also create a log of the other items you asked for, available at:
https://www.dropbox.com/s/qh0yw1ptpivpatm/typescript?dl=0

[root@ovirt01 vdsm]# vdsm-tool restore-nets

 computer
 
   �
   
 �
 �
 �
 d6a3e3c1-c5cb-42e9-a54c-ff8d0df91722
   
   
 Intel Corp.
 FYBYT10H.86A.0052.2015.0923.1845
 09/23/2015
   
 



That seems to be the issue. Even bigger issue is that we can
not skip this device easily, as it is the root of device tree and must
be present in database.

I can think of logging the exception but letting the call go through
and create a hook to fake a (minimal) device tree. Dan, what do you think?

mpolednik


Traceback (most recent call last):
 File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in 
   restore(args)
 File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in restore
   _restore_sriov_numvfs()
 File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
_restore_sriov_numvfs
   sriov_devices = _get_sriov_devices()
 File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
_get_sriov_devices
   devices = hostdev.list_by_caps()
 File "/usr/share/vdsm/hostdev.py", line 177, in list_by_caps
   libvirt_devices = _get_devices_from_libvirt()
 File "/usr/share/vdsm/hostdev.py", line 162, in _get_devices_from_libvirt
   for device in libvirtconnection.get().listAllDevices(0))
 File "/usr/share/vdsm/hostdev.py", line 162, in 
   for device in libvirtconnection.get().listAllDevices(0))
 File "/usr/share/vdsm/hostdev.py", line 109, in _parse_device_params
   devXML = etree.fromstring(device_xml)
 File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
   parser.feed(text)
 File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
   self._raiseerror(v)
 File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
_raiseerror
   raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 4,
column 13
Traceback (most recent call last):
 File "/bin/vdsm-tool", line 219, in main
   return tool_command[cmd]["command"](*args)
 File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
41, in restore_command
   exec_restore(cmd)
 File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
54, in exec_restore
   raise EnvironmentError('Failed to restore the persisted networks')
EnvironmentError: Failed to restore the persisted networks

On Mon, Mar 7, 2016 at 10:37 AM, Dan Kenigsberg  wrote:


On Mon, Mar 07, 2016 at 03:16:06PM +0200, Yedidyah Bar David wrote:
> On Mon, Mar 7, 2016 at 3:01 PM, Jonathan Sherman 
wrote:
> > Didi -
> >
> > The vdsmd service error is what led me to the vdsm-tool restore-nets
> > concern.  See the chain of errors below (along with the other details
you
> > requested.)
>
> Thanks.
>
> Changing subject and adding Dan.

> >
> > [root@ovirt01 log]# vdsm-tool restore-nets
> > Traceback (most recent call last):
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in 
> > restore(args)
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in restore
> > _restore_sriov_numvfs()
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
> > _restore_sriov_numvfs
> > sriov_devices = _get_sriov_devices()
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
> > _get_sriov_devices
> > devices = hostdev.list_by_caps()
> >   File "/usr/share/vdsm/hostdev.py", line 175, in list_by_caps
> > libvirt_devices = _get_devices_from_libvirt()
> >   File "/usr/share/vdsm/hostdev.py", line 160, in
_get_devices_from_libvirt
> > for device in libvirtconnection.get().listAllDevices(0))
> >   File "/usr/share/vdsm/hostdev.py", line 160, in 
> > for device in libvirtconnection.get().listAllDevices(0))
> >   File "/usr/share/vdsm/hostdev.py", line 107, in _parse_device_params
> > devXML = etree.fromstring(device_xml)
> >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in
XML
> > parser.feed(text)
> >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in
feed
> > self._raiseerror(v)
> >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
> > _raiseerror
> > raise err
> > xml.etree.ElementTree.ParseError: not well-formed (invalid token):
line 4,
> > column 13
> > Traceback (most recent call last):
> >   File "/bin/vdsm-tool", line 219, in main
> > return tool_command[cmd]["command"](*args)
> >   File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py",
line
> > 41, in restore_command
> > exec_restore(cmd)
> >   File

Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Jonathan Sherman 
Thanks for your time on this Dan!

The output from the hostdev looks like it may be unparseable, so I'm hoping
this is the issue (and that it can be easily remedied).

I've also create a log of the other items you asked for, available at:
https://www.dropbox.com/s/qh0yw1ptpivpatm/typescript?dl=0

[root@ovirt01 vdsm]# vdsm-tool restore-nets

  computer
  
�

  �
  �
  �
  d6a3e3c1-c5cb-42e9-a54c-ff8d0df91722


  Intel Corp.
  FYBYT10H.86A.0052.2015.0923.1845
  09/23/2015

  


Traceback (most recent call last):
  File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in 
restore(args)
  File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in restore
_restore_sriov_numvfs()
  File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
_restore_sriov_numvfs
sriov_devices = _get_sriov_devices()
  File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
_get_sriov_devices
devices = hostdev.list_by_caps()
  File "/usr/share/vdsm/hostdev.py", line 177, in list_by_caps
libvirt_devices = _get_devices_from_libvirt()
  File "/usr/share/vdsm/hostdev.py", line 162, in _get_devices_from_libvirt
for device in libvirtconnection.get().listAllDevices(0))
  File "/usr/share/vdsm/hostdev.py", line 162, in 
for device in libvirtconnection.get().listAllDevices(0))
  File "/usr/share/vdsm/hostdev.py", line 109, in _parse_device_params
devXML = etree.fromstring(device_xml)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
parser.feed(text)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
_raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 4,
column 13
Traceback (most recent call last):
  File "/bin/vdsm-tool", line 219, in main
return tool_command[cmd]["command"](*args)
  File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
41, in restore_command
exec_restore(cmd)
  File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
54, in exec_restore
raise EnvironmentError('Failed to restore the persisted networks')
EnvironmentError: Failed to restore the persisted networks

On Mon, Mar 7, 2016 at 10:37 AM, Dan Kenigsberg  wrote:

> On Mon, Mar 07, 2016 at 03:16:06PM +0200, Yedidyah Bar David wrote:
> > On Mon, Mar 7, 2016 at 3:01 PM, Jonathan Sherman 
> wrote:
> > > Didi -
> > >
> > > The vdsmd service error is what led me to the vdsm-tool restore-nets
> > > concern.  See the chain of errors below (along with the other details
> you
> > > requested.)
> >
> > Thanks.
> >
> > Changing subject and adding Dan.
>
> > >
> > > [root@ovirt01 log]# vdsm-tool restore-nets
> > > Traceback (most recent call last):
> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in 
> > > restore(args)
> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in restore
> > > _restore_sriov_numvfs()
> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
> > > _restore_sriov_numvfs
> > > sriov_devices = _get_sriov_devices()
> > >   File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
> > > _get_sriov_devices
> > > devices = hostdev.list_by_caps()
> > >   File "/usr/share/vdsm/hostdev.py", line 175, in list_by_caps
> > > libvirt_devices = _get_devices_from_libvirt()
> > >   File "/usr/share/vdsm/hostdev.py", line 160, in
> _get_devices_from_libvirt
> > > for device in libvirtconnection.get().listAllDevices(0))
> > >   File "/usr/share/vdsm/hostdev.py", line 160, in 
> > > for device in libvirtconnection.get().listAllDevices(0))
> > >   File "/usr/share/vdsm/hostdev.py", line 107, in _parse_device_params
> > > devXML = etree.fromstring(device_xml)
> > >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in
> XML
> > > parser.feed(text)
> > >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in
> feed
> > > self._raiseerror(v)
> > >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
> > > _raiseerror
> > > raise err
> > > xml.etree.ElementTree.ParseError: not well-formed (invalid token):
> line 4,
> > > column 13
> > > Traceback (most recent call last):
> > >   File "/bin/vdsm-tool", line 219, in main
> > > return tool_command[cmd]["command"](*args)
> > >   File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py",
> line
> > > 41, in restore_command
> > > exec_restore(cmd)
> > >   File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py",
> line
> > > 54, in exec_restore
> > > raise EnvironmentError('Failed to restore the persisted networks')
> > > EnvironmentError: Failed to restore the persisted networks
>
>

Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Dan Kenigsberg 
On Mon, Mar 07, 2016 at 03:16:06PM +0200, Yedidyah Bar David wrote:
> On Mon, Mar 7, 2016 at 3:01 PM, Jonathan Sherman  wrote:
> > Didi -
> >
> > The vdsmd service error is what led me to the vdsm-tool restore-nets
> > concern.  See the chain of errors below (along with the other details you
> > requested.)
> 
> Thanks.
> 
> Changing subject and adding Dan.

> >
> > [root@ovirt01 log]# vdsm-tool restore-nets
> > Traceback (most recent call last):
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 429, in 
> > restore(args)
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 387, in restore
> > _restore_sriov_numvfs()
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 82, in
> > _restore_sriov_numvfs
> > sriov_devices = _get_sriov_devices()
> >   File "/usr/share/vdsm/vdsm-restore-net-config", line 54, in
> > _get_sriov_devices
> > devices = hostdev.list_by_caps()
> >   File "/usr/share/vdsm/hostdev.py", line 175, in list_by_caps
> > libvirt_devices = _get_devices_from_libvirt()
> >   File "/usr/share/vdsm/hostdev.py", line 160, in _get_devices_from_libvirt
> > for device in libvirtconnection.get().listAllDevices(0))
> >   File "/usr/share/vdsm/hostdev.py", line 160, in 
> > for device in libvirtconnection.get().listAllDevices(0))
> >   File "/usr/share/vdsm/hostdev.py", line 107, in _parse_device_params
> > devXML = etree.fromstring(device_xml)
> >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
> > parser.feed(text)
> >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
> > self._raiseerror(v)
> >   File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
> > _raiseerror
> > raise err
> > xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 4,
> > column 13
> > Traceback (most recent call last):
> >   File "/bin/vdsm-tool", line 219, in main
> > return tool_command[cmd]["command"](*args)
> >   File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
> > 41, in restore_command
> > exec_restore(cmd)
> >   File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line
> > 54, in exec_restore
> > raise EnvironmentError('Failed to restore the persisted networks')
> > EnvironmentError: Failed to restore the persisted networks

Jonathan, thanks for this disturbing report. For some reason, Vdsm fails
to parse libvirt's output.

Could you share your libvirt version as well the output of
for d in `virsh -r nodedev-list`; do echo $d; virsh -r 
nodedev-dumpxml $d; done

if all seems like valid xml, can you add the following print() and run
`restore-net` again?

diff --git a/lib/vdsm/hostdev.py b/lib/vdsm/hostdev.py
index 6ba3189..9d22e9e 100644
--- a/lib/vdsm/hostdev.py
+++ b/lib/vdsm/hostdev.py
@@ -113,6 +113,7 @@ def _parse_device_params(device_xml):
 Process device_xml and return dict of found known parameters,
 also doing sysfs lookups for sr-iov related information
 """
+print(device_xml)
 address_parser = {'pci': _parse_pci_address,
   'scsi': _parse_scsi_address,
   'usb_device': _parse_usb_address}

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

Re: [ovirt-users] restore-nets failing (was: Fresh install failing (Hosted Engine))

2016-03-07 Thread Yedidyah Bar David 
On Mon, Mar 7, 2016 at 3:01 PM, Jonathan Sherman  wrote:
> Didi -
>
> The vdsmd service error is what led me to the vdsm-tool restore-nets
> concern.  See the chain of errors below (along with the other details you
> requested.)

Thanks.

Changing subject and adding Dan.

>
> Thanks!
> -js
>
> --
>
> [jsherman@ovirt01 vdsm]$ ls -la /var/log/vdsm
> total 48
> drwxr-xr-x.  3 vdsm kvm   4096 Mar  5 18:50 .
> drwxr-xr-x. 13 root root  4096 Mar  6 03:08 ..
> drwxr-xr-x.  2 vdsm kvm  6 Mar  1 09:18 backup
> -rw-r--r--.  1 vdsm kvm  0 Mar  5 17:53 connectivity.log
> -rw-r--r--.  1 vdsm kvm  0 Mar  5 17:53 mom.log
> -rw-r--r--.  1 root root 34437 Mar  6 22:18 supervdsm.log
> -rw-r--r--.  1 root root  1875 Mar  5 17:59 upgrade.log
> -rw-r--r--.  1 vdsm kvm  0 Mar  5 17:53 vdsm.log
>
> --
>
> [root@ovirt01 log]# sestatus
> SELinux status: enabled
> SELinuxfs mount:/sys/fs/selinux
> SELinux root directory: /etc/selinux
> Loaded policy name: targeted
> Current mode:   permissive
> Mode from config file:  enforcing
> Policy MLS status:  enabled
> Policy deny_unknown status: allowed
> Max kernel policy version:  28
>
> --
>
> [root@ovirt01 audit]# tail -20 audit.log
> type=USER_AUTH msg=audit(1457355177.617:519): pid=20733 uid=1000 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:authentication grantors=pam_unix acct="jsherman"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_ACCT msg=audit(1457355177.623:520): pid=20733 uid=1000 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="jsherman"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_CMD msg=audit(1457355177.625:521): pid=20733 uid=1000 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='cwd="/var/log/vdsm" cmd=73797374656D63746C207374617274207664736D64
> terminal=pts/0 res=success'
> type=CRED_ACQ msg=audit(1457355177.626:522): pid=20733 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/sudo"
> hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_START msg=audit(1457355177.628:523): pid=20733 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:session_open grantors=pam_keyinit,pam_limits acct="root"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_END msg=audit(1457355179.095:524): pid=20733 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:session_close grantors=pam_keyinit,pam_limits acct="root"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=CRED_DISP msg=audit(1457355179.095:525): pid=20733 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/sudo"
> hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=SERVICE_START msg=audit(1457355179.099:526): pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=vdsm-network comm="systemd" exe="/usr/lib/systemd/systemd"
> hostname=? addr=? terminal=? res=failed'
> type=USER_CMD msg=audit(1457355237.531:527): pid=20768 uid=1000 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='cwd="/var/log" cmd=6C73202D616C206175646974 terminal=pts/0 res=success'
> type=CRED_ACQ msg=audit(1457355237.533:528): pid=20768 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_START msg=audit(1457355237.535:529): pid=20768 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:session_open grantors=pam_keyinit,pam_limits acct="root"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_END msg=audit(1457355237.554:530): pid=20768 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:session_close grantors=pam_keyinit,pam_limits acct="root"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=CRED_DISP msg=audit(1457355237.555:531): pid=20768 uid=0 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root"
> exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
> type=USER_CMD msg=audit(1457355242.882:532): pid=20770 uid=1000 auid=1000
> ses=19 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> msg='cwd="/var/log" cmd=7375202D