OpenStack Compute (nova)

failed to launch an instance,error Unrecognized Content-Type provided in request

Asked by antiError

i installed nova,glance,keystone,horizon successfully.And all services are installed in one machines.
when i launched an instance,there is an error in nova-api.log

Unrecognized Content-Type provided in request from (pid=32473) get_body /usr/local/lib/python2.7/dist-packages/nova-2012.2-py2.7.egg/nova/api/openstack/wsgi.py:697

where is wrong with me ??
This is my nova.conf.

[DEFAULT]
verbose=True
auth_strategy=keystone
allow_resize_to_same_host=True
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/loca/bin/nova-dhcpbridge
fixed_range=10.0.3.0/24
s3_host=192.168.78.101
network_manager=nova.network.manager.FlatDHCPManager
volume_group=nova-volumes
volume_name_template=volume-%08x
iscsi_helper=tgtadm
osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
my_ip=192.168.78.101
public_interface=br100
vlan_interface=eth0
flat_network_bridge=br100
flat_interface=eth0
sql_connection=mysql://nova:nova@192.168.78.101/nova
libvirt_type=kvm
instance_name_template=instance-%08x
novncproxy_base_url=http:// 192.168.78.101:6080/vnc_auto.html
xvpvncproxy_base_url=http:// 192.168.78.101:6081/console
vncserver_listen=127.0.0.1
vncserver_proxyclient_address=127.0.0.1
api_paste_config=/etc/nova/api-paste.ini
image_service=nova.image.glance.GlanceImageService
ec2_dmz_host=192.168.78.101
rabbit_host=192.168.78.101
rabbit_password=guest
glance_api_servers=192.168.78.101:9292
force_dhcp_release=True
connection_type=libvirt
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
logdir=/var/log/nova

Question information

Language:
English Edit question
Status:
Expired
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Msekni (msekni) said : 		#1

Hi,
I had the same problem and i fixed it :-)
check your Nova-compute endpoint with keystone endpoint-list, it should follow this format: [tenant_id is crucial]

--publicurl 'http://157.159.100.240:8774/v1.1/$(tenant_id)s' --adminurl 'http://157.159.100.240:8774/v1.1/$(tenant_id)s' --internalurl 'http://157.159.100.240:8774/v1.1/$(tenant_id)s'

if not, delete your endpoint and re create it !
If this solves your problem, don't be too happy coz you will be having another one soon :D

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Mark McLoughlin (markmc) said : 		#3

See FAQ about Content-Type message
FAQ #2003: “Unrecognized Content-Type provided in request”.