awestin1's profile - activity

It turns out that there were actually a few issues. 1) Apparently, Gnocchi doesn't like you having admin creds loaded f

I am trying to set up Ceilometer with Gnocchi. Gnocchi has been installed and configured. However, after starting the Gnocchi api and metricd, I keep getting an error when attempting to test Gnicchi. When I run gnocchi metric list, I get the following error:

[~]# gnocchi metric list
{"message": "The server is currently unavailable. Please try again at a later time.<br /><br />\n\n\n", "code": "503 Service Unavailable", "title": "Service Unavailable"} (HTTP 503)

At the same time, I get the following error from /etc/var/log/gnocchi/gnocchi.log:

2017-10-27 00:32:27.241 3231 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}
2017-10-27 00:32:27.242 3231 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data

I also get the following from stderr on gnocchi-api:

[~]# gnocchi-api -p 8041 -b 0.0.0.0
Option "verbose" from group "DEFAULT" is deprecated for removal.  Its value may be silently ignored in the future.
********************************************************************************
STARTING test server gnocchi.rest.app.build_wsgi_app
Available at http://gcp-openstack:8041/
DANGER! For testing only, do not use in production
********************************************************************************
10.9.47.55 - - [26/Oct/2017 23:32:21] "GET /v1/metric HTTP/1.1" 503 170

The [keystone_authtoken] section in my /etc/gnocchi/gnocchi.conf is as follows:

[keystone_authtoken]
auth_type = password
auth_url = http://controller:5000/v3
project_domain_name = Default
user_domain_name = Default
project_name = service
username = gnocchi
password = P@ssw0rd
interface = internalURL
region_name = RegionOne

Does anyone have any suggestions for troubleshooting this issue? I have already sourced admin-openrc before running the Gnocchi client. So, I am not sure why I am receiving this message. My admin-openrc is as follows:

[~]# cat admin-openrc 
export OS_PROJECT_DOMAIN_NAME=Default
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=admin_P@ssw0rd
export OS_AUTH_URL=http://controller:35357/v3
export OS_IDENTITY_API_VERSION=3
export OS_IMAGE_API_VERSION=2
export OS_AUTH_TYPE=password

Are there any other environment variables I am supposed to be setting?

Edit: I am running Ocata RDO on RHEL 7.

It turns out that there were actually a few issues. 1) Apparently, Gnocchi doesn't like you having admin creds loaded f

Gnocchi - Keystone Unable to Validate Token I am trying to set up Ceilometer with Gnocchi. Gnocchi has been installed an

Gnocchi - Keystone Unable to Validate Token I am trying to set up Ceilometer with Gnocchi. Gnocchi has been installed an

Gnocchi - Keystone Unable to Validate Token I am trying to set up Ceilometer with Gnocchi. Gnocchi has been installed an

What port is your placement endpoint listen on? openstack endpoint list I know there is a typo in the OpenStack RD

What port is your placement endpoint listen on? openstack endpoint list I know there is a typo in the OpenStack RD

I have installed OpenStack Hyper-V Compute Ocata msi installer from Cloudbase and have successfully attached the compute node to the OpenStack controller and I am using the hypervneutronagent on the target compute node.

When I attempt to launch an instance OpenStack begins building the VM on my compute node but then the build fails with the following error in Horizon:

Error: Failed to perform requested operation on instance "testinstance-vfjdiow84392", the instance has an error status: Please try again later [Error: Binding failed for port b28593fa-646d-409d-98ca-ebde69cacb04, please check neutron logs for more information.].

Looking through the neutron logs on the controller, I am seeing the following error:

No ports have port_id starting with Network Adapter

I'm not sure I understand what this means. Any ideas?

UPDATE:

I'm also seeing the following on the hypervneutronagent log when the agent starts:

2017-05-22 16:18:13.388 2160 INFO hyperv.neutron.l2_agent [req-1c98cd35-de4a-4c89-976e-230668df5e4c - - - - -] Agent initialized successfully, now running... 
2017-05-22 16:19:57.907 2160 INFO hyperv.neutron.hyperv_neutron_agent [-] Hyper-V VM vNIC added: Network Adapter
2017-05-22 16:19:59.688 2160 INFO hyperv.neutron.hyperv_neutron_agent [req-1c98cd35-de4a-4c89-976e-230668df5e4c - - - - -] Adding port Network Adapter

I didn't notice this before as this only logs during agent start and I thought Network Adapter was just a generic term, not a specific name that the agent was looking for. I never gave the config a string "Network Adapter" as far as I know. So, I'm not sure where the agent is getting "Network Adapter" from...

When stopping the hypervneutronagent, I see the following:

2017-05-22 15:11:36.931 704 INFO hyperv.neutron.hyperv_neutron_agent [-] Hyper-V VM vNIC removed: Network Adapter
2017-05-22 15:11:36.931 704 INFO hyperv.neutron.hyperv_neutron_agent [-] Hyper-V VM vNIC removed: None
2017-05-22 15:11:36.931 704 INFO hyperv.neutron.hyperv_neutron_agent [-] Hyper-V VM vNIC removed: None
2017-05-22 15:11:36.931 704 INFO hyperv.neutron.hyperv_neutron_agent [-] Hyper-V VM vNIC removed: None
2017-05-22 15:11:36.931 704 INFO hyperv.neutron.hyperv_neutron_agent [-] Hyper-V VM vNIC removed: None
2017-05-22 15:11:37.799 704 INFO neutron.agent.securitygroups_rpc [-] Remove device filter for [u'Network Adapter']
2017-05-22 15:11:37.799 704 INFO neutron.agent.securitygroups_rpc [-] Remove device filter for [None]

Anyone know where this "Network Adapter" string is comping from? I double-checked the nova.conf and neutronhypervagent.conf on the compute node and I'm seeing no string "Network Adapter." None of my Hyper-V VMswitches are named "Network Adapter" and none of my physical interfaces are names "Network Adapter"...

As Claudiu mentioned in the comments "Neutron Ocata doesn't fail to start if a configured mechanism_driver is not instal

As Claudiu mentioned in the comments "Neutron Ocata doesn't fail to start if a configured mechanism_driver is not instal

As Claudiu mentioned in the comments "Neutron Ocata doesn't fail to start if a configured mechanism_driver is not instal

@Claudiu: That did it! Had to "pip install networking-hyperv==4.0.0"

@Claudiu: Thanks! I'm not seeing networking-hyperv in my list of installed Python packages! I'll go ahead and install an

Updated the post with fresh logs that might be more helpful.

False alarm. Disabled all mech_agent types except hyperv in my /etc/neutron/plugin.ini. This stopped some of the DEBUG l

HyperV-Agent Error: PortBindingFailed I am attempting to configure OpenStack to launch instances on a specific VLAN on o

Looks as though, for some reason, the neutron server is only trying to use Linux Bridge and OpenVSwitch agents on the ta

HyperV-Agent Error: PortBindingFailed I am attempting to configure OpenStack to launch instances on a specific VLAN on o

HyperV-Agent Error: PortBindingFailed I am attempting to configure OpenStack to launch instances on a specific VLAN on o

I am seeing the following warning in the neutron-hyperv-agent log on the node when starting the neutron agent svc 2017-0

Also, yes. I have confirmed that the Hyper-V ML2 mechanism driver is enabled in my config (/etc/neutron/plugin.ini): [m

Also, yes. I have confirmed that the Hyper-V ML2 mechanism driver is enabled in my config (/etc/neutron/plugin.ini): [m

Also, yes. I have confirmed that the Hyper-V ML2 mechanism driver is enabled in my config (/etc/neutron/plugin.ini): [m

Also, yes. I have confirmed that the Hyper-V ML2 mechanism driver is enabled in my config (/etc/neutron/plugin.ini): [ml

Turned off DHCP for the subnet. This does not appear to have helped: openstack subnet set --no-dhcp subnetnamehere

Thanks for the input! I ran "neutron dhcp-agent-list-hosting-net [networkidhere]" and confirmed "adminstateup" is True a

I am pretty sure the instance being created will not have network access to the DHCP agent. Will this keep the instance

Thanks for the input! I ran "neutron dhcp-agent-list-hosting-net [networkidhere]" and confirmed "adminstateup" is True a

Thanks for the input! I ran neutron dhcp-agent-list-hosting-net [network_id_here] and confirmed admin_state_up is True a

I keep seeing the same logs over and over again in my /var/log/neutron/linuxbridge-agent.log. Does anyone know why or have any suggestions where I should look to dig into this further? I am not using OVS on my nodes. I'm just using the neutron hyper-v agent. Do I have something enabled somewhere in my config that should be disabled?

2017-07-20 17:16:52.349 61252 INFO neutron.common.config [-] Logging enabled!
2017-07-20 17:16:52.349 61252 INFO neutron.common.config [-] /usr/bin/neutron-linuxbridge-agent version 10.0.0
2017-07-20 17:16:52.349 61252 INFO neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Interface mappings: {'provider': 'provider'}
2017-07-20 17:16:52.350 61252 INFO neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Bridge mappings: {}
2017-07-20 17:16:52.355 61252 ERROR neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Interface provider for physical network provider does not exist. Agent terminated!

2017-07-20 17:16:55.570 61276 INFO neutron.common.config [-] Logging enabled!
2017-07-20 17:16:55.570 61276 INFO neutron.common.config [-] /usr/bin/neutron-linuxbridge-agent version 10.0.0
2017-07-20 17:16:55.571 61276 INFO neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Interface mappings: {'provider': 'provider'}
2017-07-20 17:16:55.571 61276 INFO neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Bridge mappings: {}
2017-07-20 17:16:55.577 61276 ERROR neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Interface provider for physical network provider does not exist. Agent terminated!

And this: https://ask.cloudbase.it/question/2226/hyperv-agent-error-portbindingfailed/