networking-midonet

wrong instance metadata for fip64

Bug #1652075 reported by YAMAMOTO Takashi on 2016-12-22

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	networking-midonet	New	Low	Unassigned

Bug Description

eg. http://logs.openstack.org/83/414083/1/check/gate-tempest-dsvm-networking-midonet-ml2-ubuntu-xenial/e404124/logs/testr_results.html.gz

2016.12.22 13:06:30.162 DEBUG [qtp608203751-133] metadata - Request from instance:407a6e8b-a308-4643-bf4e-c1e0aaa8fcab
to http://10.16.245.46:8775/2009-04-04/meta-data/public-ipv4
2016.12.22 13:06:30.164 DEBUG [qtp608203751-133] metadata - Response for instance:407a6e8b-a308-4643-bf4e-c1e0aaa8fcab status:200 length:11 media-type:text/plain; charset=UTF-8 data:2001:db8::f

YAMAMOTO Takashi (yamamoto) on 2016-12-26

summary:

- wrong metadata for fip64
+ wrong instance metadata for fip64

YAMAMOTO Takashi (yamamoto) on 2017-02-06

Changed in networking-midonet:
importance:	Undecided → Low

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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