CirrOS

bad request syntax in metadata server

Bug #1148165 reported by Joe Gordon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CirrOS
Fix Released
Medium
Unassigned
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

When spinning up a VM in latest Devstack (G3 timeframe), with debug logging turned off I get several 'Bad request syntax' error messages.

This may actually be a problem in cloud-init.

2013-03-06 00:58:21.176 6742 INFO nova.metadata.wsgi.server [-] (6742) accepted ('10.0.0.2', 53364)

10.0.0.2 - - [06/Mar/2013 00:58:21] code 400, message Bad request syntax ('GET /2009-04-04/meta-data// <head>/openssh-key HTTP/1.1')
10.0.0.2 - - [06/Mar/2013 00:58:21] "GET /2009-04-04/meta-data// <head>/openssh-key HTTP/1.1" 400 -
2013-03-06 00:58:21.369 6742 INFO nova.metadata.wsgi.server [-] (6742) accepted ('10.0.0.2', 53365)

10.0.0.2 - - [06/Mar/2013 00:58:21] code 400, message Bad request syntax ('GET /2009-04-04/meta-data// <title>404 Not Found</title>/openssh-key HTTP/1.1')
10.0.0.2 - - [06/Mar/2013 00:58:21] "GET /2009-04-04/meta-data// <title>404 Not Found</title>/openssh-key HTTP/1.1" 400 -
2013-03-06 00:58:21.574 6742 INFO nova.metadata.wsgi.server [-] (6742) accepted ('10.0.0.2', 53366)

10.0.0.2 - - [06/Mar/2013 00:58:21] code 400, message Bad request syntax ('GET /2009-04-04/meta-data// </head>/openssh-key HTTP/1.1')
10.0.0.2 - - [06/Mar/2013 00:58:21] "GET /2009-04-04/meta-data// </head>/openssh-key HTTP/1.1" 400 -
2013-03-06 00:58:21.790 6742 INFO nova.metadata.wsgi.server [-] (6742) accepted ('10.0.0.2', 53367)

10.0.0.2 - - [06/Mar/2013 00:58:21] code 400, message Bad request syntax ('GET /2009-04-04/meta-data// <body>/openssh-key HTTP/1.1')
10.0.0.2 - - [06/Mar/2013 00:58:21] "GET /2009-04-04/meta-data// <body>/openssh-key HTTP/1.1" 400 -
2013-03-06 00:58:34.748 6742 INFO nova.metadata.wsgi.server [-] (6742) accepted ('10.0.0.2', 53368)

Related branches

lp:~smoser/cirros/trunk
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

Do you see errors on the other side? presumably cloud-init? we are returning 400 probably because we don't like the "//" int th GET request. Need to figure out who is calling this and why they end up with "/2009-04-04/meta-data//" and what happens when they get back 400 from us.

Changed in nova:
status: New → Incomplete
Revision history for this message
Joe Gordon (jogo) wrote :

This bug can be seen in the devstack tempest job: http://logs.openstack.org/23496/4/check/gate-tempest-devstack-vm-full/7690/logs/screen-n-api.txt.gz

As for what is happening on the cloud-init side, I don't know yet

Scott Moser (smoser)
no longer affects: cloud-init
Revision history for this message
Scott Moser (smoser) wrote :

fixed in revno 251.

Changed in cirros:
status: New → Fix Committed
Joe Gordon (jogo)
Changed in nova:
status: Incomplete → Invalid
Scott Moser (smoser)
Changed in cirros:
importance: Undecided → Medium
Revision history for this message
Scott Moser (smoser) wrote :

fix released in 0.3.2

Changed in cirros:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.