[Openstack] SR-IOV error libvirtError: Node device not found: no node device with matching name

2018-09-28 Thread Satish Patel 
Folks,


I am configuring SR-IOV and encounter that error, does anyone know
what is that error related, I am using Queens

I found this but it didn't help me
http://lists.openstack.org/pipermail/openstack/2018-January/045982.html

I have restarted libvert and whole compute node also but i can't see
"net_enp3s1f4_00_00_00_00_00_00" device in virsh nodedev-list


2018-09-28 16:06:16.396 28663 WARNING nova.compute.monitors
[req-6d056524-d0ed-48b8-b2cb-50a1fdc91dd1 - - - - -] Excluding
nova.compute.monitors.cpu monitor virt_driver. Not in the list of
enabled monitors (CONF.compute_monitors).
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
[req-6d056524-d0ed-48b8-b2cb-50a1fdc91dd1 - - - - -] Error updating
resources for node ostack-compute-63.v1v0x.net.: libvirtError: Node
device not found: no node device with matching name
'net_enp3s1f4_00_00_00_00_00_00'
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager Traceback
(most recent call last):
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/compute/manager.py",
line 7275, in update_available_resource_for_node
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
rt.update_available_resource(context, nodename)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/compute/resource_tracker.py",
line 673, in update_available_resource
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager resources
= self.driver.get_available_resource(nodename)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 6442, in get_available_resource
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
self._get_pci_passthrough_devices()
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 5938, in _get_pci_passthrough_devices
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
pci_info.append(self._get_pcidev_info(name))
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 5899, in _get_pcidev_info
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
device.update(_get_device_capabilities(device, address))
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 5870, in _get_device_capabilities
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
pcinet_info = self._get_pcinet_info(address)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 5813, in _get_pcinet_info
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager virtdev =
self._host.device_lookup_by_name(devname)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/nova/virt/libvirt/host.py",
line 838, in device_lookup_by_name
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager return
self.get_connection().nodeDeviceLookupByName(name)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/eventlet/tpool.py",
line 186, in doit
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager result =
proxy_call(self._autowrap, f, *args, **kwargs)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/eventlet/tpool.py",
line 144, in proxy_call
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager rv =
execute(f, *args, **kwargs)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/eventlet/tpool.py",
line 125, in execute
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager
six.reraise(c, e, tb)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/eventlet/tpool.py",
line 83, in tworker
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager rv =
meth(*args, **kwargs)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager   File
"/openstack/venvs/nova-17.0.8/lib/python2.7/site-packages/libvirt.py",
line 4232, in nodeDeviceLookupByName
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager if ret is
None:raise libvirtError('virNodeDeviceLookupByName() failed',
conn=self)
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager libvirtError:
Node device not found: no node device with matching name
'net_enp3s1f4_00_00_00_00_00_00'
2018-09-28 16:06:16.500 28663 ERROR nova.compute.manager

___
Mailing list: http://lists.openstack.

Re: [Openstack] [Horizon][Keystone] Migration to keystone v3

2018-09-28 Thread Erik McCormick 
Add yourself as an admin of the domain. I think it uses a domain scored
token for that tab. In V2 you would have only been admin of a project.

-Erik

On Fri, Sep 28, 2018, 11:47 AM Davide Panarese  wrote:

> It’s not nova-compute that report the issue but keystone authentication on
> computing tab.
> As I said before, openstack cli working properly with all services, nova
> included.
>
>
>
> *Davide Panarese*
> Cloud & Solution Architect
>
> *Enter  |  The open network and cloud provider*
>
> Via privata Stefanardo da Vimercate, 28
> 20128 Milano
> enter.eu
>
> Mobile: +39 3386369591
> Phone: +39 02 25514 837
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
>
> On 28 Sep 2018, at 14:52, Eugen Block  wrote:
>
> Since nova-compute reports that failure, what is your auth_url in
> /etc/nova/nova.conf in the [placement] section?
>
>
>
> Zitat von Davide Panarese :
>
> @Paul
> Yes keystone:5000 is my endpoint.
>
> @Eugen
> OPENSTACK_KEYSTONE_URL = "http://%s/v3 " % OPENSTACK_HOST
>
> Still not working.
>
>
> Davide Panarese
>
>
> On 28 Sep 2018, at 13:50, Eugen Block  wrote:
>
> Hi,
>
> what is your current horizon configuration?
>
> control:~ # grep KEYSTONE_URL
> /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py
> OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3"; % OPENSTACK_HOST
>
> Maybe this still configured to v2?
>
> Regards,
> Eugen
>
>
> Zitat von Davide Panarese :
>
> Goodmorning every one,
> i'm finally approaching migration to keystone v3 but i want to maintain
> keystone v2 compatibility for all users that have custom scripts for
> authentication to our openstack.
> Migration seems to be pretty simple, change endpoint direct into database
> changing http://keystone:5000/v2.0 to http://keystone:5000 <
> http://keystone:5000/>; Openstack client have the capability to add /v2.0
> or /v3 at the end of url retrieved from catalog.
> But i'm stuck with horizon dashboard, login works but compute information
> are not available and error log show:
> “ Forbidden: You are not authorized to perform the requested action:
> rescope a scoped token. (HTTP 403)"
> All other tabs works properly.
> I think that is a keystone issue but i don't understand why with openstack
> client works perfectly and with horizon not.
> Anyone can explain what i missed in migration?
>
> Thanks a lot,
> Davide Panarese
>
>
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non
> infetto.
> Seguire il link qui sotto per segnalarlo come spam:
> http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=D389145856.A899A
>
>
>
>
>
>
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non
> infetto.
> Seguire il link qui sotto per segnalarlo come spam:
> http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=9946B46CDF.A2B74
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Horizon][Keystone] Migration to keystone v3

2018-09-28 Thread Davide Panarese 
It’s not nova-compute that report the issue but keystone authentication on 
computing tab.
As I said before, openstack cli working properly with all services, nova 
included.



Davide Panarese
Cloud & Solution Architect

Enter  |  The open network and cloud provider

Via privata Stefanardo da Vimercate, 28 
20128 Milano
enter.eu

Mobile: +39 3386369591
Phone: +39 02 25514 837

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.

> On 28 Sep 2018, at 14:52, Eugen Block  wrote:
> 
> Since nova-compute reports that failure, what is your auth_url in 
> /etc/nova/nova.conf in the [placement] section?
> 
> 
> 
> Zitat von Davide Panarese :
> 
>> @Paul
>> Yes keystone:5000 is my endpoint.
>> 
>> @Eugen
>> OPENSTACK_KEYSTONE_URL = "http://%s/v3 " % OPENSTACK_HOST
>> 
>> Still not working.
>> 
>> 
>> Davide Panarese
>> 
>> 
>>> On 28 Sep 2018, at 13:50, Eugen Block  wrote:
>>> 
>>> Hi,
>>> 
>>> what is your current horizon configuration?
>>> 
>>> control:~ # grep KEYSTONE_URL 
>>> /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py
>>> OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3"; % OPENSTACK_HOST
>>> 
>>> Maybe this still configured to v2?
>>> 
>>> Regards,
>>> Eugen
>>> 
>>> 
>>> Zitat von Davide Panarese :
>>> 
 Goodmorning every one,
 i'm finally approaching migration to keystone v3 but i want to maintain 
 keystone v2 compatibility for all users that have custom scripts for 
 authentication to our openstack.
 Migration seems to be pretty simple, change endpoint direct into database 
 changing http://keystone:5000/v2.0 to http://keystone:5000 
 ; Openstack client have the capability to add /v2.0 
 or /v3 at the end of url retrieved from catalog.
 But i'm stuck with horizon dashboard, login works but compute information 
 are not available and error log show:
 “ Forbidden: You are not authorized to perform the requested action: 
 rescope a scoped token. (HTTP 403)"
 All other tabs works properly.
 I think that is a keystone issue but i don't understand why with openstack 
 client works perfectly and with horizon not.
 Anyone can explain what i missed in migration?
 
 Thanks a lot,
 Davide Panarese
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> 
>>> --
>>> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non 
>>> infetto.
>>> Seguire il link qui sotto per segnalarlo come 
>>> spam:http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=D389145856.A899A
>>> 
>>> 
> 
> 
> 
> 
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non 
> infetto.
> Seguire il link qui sotto per segnalarlo come 
> spam:http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=9946B46CDF.A2B74
> 
> 

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Horizon][Keystone] Migration to keystone v3

2018-09-28 Thread Davide Panarese 
@Paul
Yes keystone:5000 is my endpoint.

@Eugen
OPENSTACK_KEYSTONE_URL = "http://%s/v3 " % OPENSTACK_HOST

Still not working. 


Davide Panarese


> On 28 Sep 2018, at 13:50, Eugen Block  wrote:
> 
> Hi,
> 
> what is your current horizon configuration?
> 
> control:~ # grep KEYSTONE_URL 
> /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py
> OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3"; % OPENSTACK_HOST
> 
> Maybe this still configured to v2?
> 
> Regards,
> Eugen
> 
> 
> Zitat von Davide Panarese :
> 
>> Goodmorning every one,
>> i'm finally approaching migration to keystone v3 but i want to maintain 
>> keystone v2 compatibility for all users that have custom scripts for 
>> authentication to our openstack.
>> Migration seems to be pretty simple, change endpoint direct into database 
>> changing http://keystone:5000/v2.0 to http://keystone:5000 
>> ; Openstack client have the capability to add /v2.0 
>> or /v3 at the end of url retrieved from catalog.
>> But i'm stuck with horizon dashboard, login works but compute information 
>> are not available and error log show:
>> “ Forbidden: You are not authorized to perform the requested action: rescope 
>> a scoped token. (HTTP 403)"
>> All other tabs works properly.
>> I think that is a keystone issue but i don't understand why with openstack 
>> client works perfectly and with horizon not.
>> Anyone can explain what i missed in migration?
>> 
>> Thanks a lot,
>> Davide Panarese
> 
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non 
> infetto.
> Seguire il link qui sotto per segnalarlo come 
> spam:http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=D389145856.A899A
> 
> 

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Horizon][Keystone] Migration to keystone v3

2018-09-28 Thread Eugen Block 
Since nova-compute reports that failure, what is your auth_url in  
/etc/nova/nova.conf in the [placement] section?




Zitat von Davide Panarese :


@Paul
Yes keystone:5000 is my endpoint.

@Eugen
OPENSTACK_KEYSTONE_URL = "http://%s/v3 " % OPENSTACK_HOST

Still not working.


Davide Panarese



On 28 Sep 2018, at 13:50, Eugen Block  wrote:

Hi,

what is your current horizon configuration?

control:~ # grep KEYSTONE_URL  
/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py

OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3"; % OPENSTACK_HOST

Maybe this still configured to v2?

Regards,
Eugen


Zitat von Davide Panarese :


Goodmorning every one,
i'm finally approaching migration to keystone v3 but i want to  
maintain keystone v2 compatibility for all users that have custom  
scripts for authentication to our openstack.
Migration seems to be pretty simple, change endpoint direct into  
database changing http://keystone:5000/v2.0 to  
http://keystone:5000 ; Openstack client  
have the capability to add /v2.0 or /v3 at the end of url  
retrieved from catalog.
But i'm stuck with horizon dashboard, login works but compute  
information are not available and error log show:
“ Forbidden: You are not authorized to perform the requested  
action: rescope a scoped token. (HTTP 403)"

All other tabs works properly.
I think that is a keystone issue but i don't understand why with  
openstack client works perfectly and with horizon not.

Anyone can explain what i missed in migration?

Thanks a lot,
Davide Panarese





___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato  
non infetto.
Seguire il link qui sotto per segnalarlo come  
spam:http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=D389145856.A899A








___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Horizon][Keystone] Migration to keystone v3

2018-09-28 Thread Eugen Block 

Hi,

what is your current horizon configuration?

control:~ # grep KEYSTONE_URL  
/srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py

OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3"; % OPENSTACK_HOST

Maybe this still configured to v2?

Regards,
Eugen


Zitat von Davide Panarese :


Goodmorning every one,
i'm finally approaching migration to keystone v3 but i want to  
maintain keystone v2 compatibility for all users that have custom  
scripts for authentication to our openstack.
Migration seems to be pretty simple, change endpoint direct into  
database changing http://keystone:5000/v2.0 to http://keystone:5000  
; Openstack client have the capability to add  
/v2.0 or /v3 at the end of url retrieved from catalog.
But i'm stuck with horizon dashboard, login works but compute  
information are not available and error log show:
“ Forbidden: You are not authorized to perform the requested action:  
rescope a scoped token. (HTTP 403)"

All other tabs works properly.
I think that is a keystone issue but i don't understand why with  
openstack client works perfectly and with horizon not.

Anyone can explain what i missed in migration?

Thanks a lot,
Davide Panarese





___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Horizon][Keystone] Migration to keystone v3

2018-09-28 Thread Davide Panarese 
Goodmorning every one,
i'm finally approaching migration to keystone v3 but i want to maintain 
keystone v2 compatibility for all users that have custom scripts for 
authentication to our openstack.
Migration seems to be pretty simple, change endpoint direct into database 
changing http://keystone:5000/v2.0 to http://keystone:5000 
; Openstack client have the capability to add /v2.0 or 
/v3 at the end of url retrieved from catalog.
But i'm stuck with horizon dashboard, login works but compute information are 
not available and error log show:
“ Forbidden: You are not authorized to perform the requested action: rescope a 
scoped token. (HTTP 403)"
All other tabs works properly.
I think that is a keystone issue but i don't understand why with openstack 
client works perfectly and with horizon not.
Anyone can explain what i missed in migration?

Thanks a lot,
Davide Panarese
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack