Mismatch url while requesting a question

Bug #1486678 reported by Alberto Martín on 2015-08-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Community Project
Evgeny Fadeev

Bug Description


Consuming the Askbot API, I've found that there is a question which URL is wrong.

The thing is, when I do the request to the question with id:'12070' using the API, the url parsed in the JSON does not exist.

So doing:


It returns a JSON with a wrong URL:

tags: [
answer_count: 0,
accepted_answer_id: null,
answer_ids: [ ],
id: 12070,
last_activity_by: {
username: "fifieldt",
id: 64
view_count: 112,
last_activity_at: "1398966921",
title: "my instance can not obtain ip.",
url: "https://ask.openstack.org/zh/question/12070/my-instance-can-not-obtain-ip/",
author: {
username: "Jason",
id: 3248
added_at: "1392462895",
summary: "<p>hi,there I use the vlan mode to deploy my openstack on three node ,controller node,computer node and network node .</p> <p>my instance can not obain ip.</p> <p>anyone knows why?</p> <p>more info as fllows:</p> <pre><code>root@controller:/etc/init.d# neutron agent-list +--------------------------------------+--------------------+----------+-------+----------------+ | id | agent_type | host | alive | admin_state_up | +--------------------------------------+--------------------+----------+-------+----------------+ | 32f55741-08b2-4eae-a6e9-f94d80d66bca | L3 agent | neutron | :-) | True | | 3df95764-4c4f-45f6-99b5-5a3f15597575 | DHCP agent | neutron | :-) | True | | 5685a009-3718-4395-ada5-ee70825ed98b | Open vSwitch agent | node-253 | :-) | True | | 7f55b2f5-42c2-45c1-a417-e1a0fcfa1f09 | Open vSwitch agent | neutron | :-) | True | root@controller:/etc/init.d# nova-manage service list Binary Host Zone Status State Updated_At nova-cert controller internal enabled :-) 2014-02-15 11:27:07 nova-conductor controller internal enabled :-) 2014-02-15 11:27:15 nova-consoleauth controller internal enabled :-) 2014-02-15 11:27:08 nova-scheduler controller internal enabled :-) 2014-02-15 11:27:08 nova-compute node-253 nova enabled :-) 2014-02-15 11:27:11 </code></pre> <p>computer-node /etc/network/interface:</p> <pre><code># The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth1 iface eth1 inet static address netmask #For Exposing OpenStack API over the internet #auto eth0 #iface eth0 inet manual #up ifconfig $IFACE up #up ip link set $IFACE promisc on #down ip link set $IFACE promisc off #down ifconfig $IFACE down auto eth0 iface eth0 inet static address netmask network broadcast gateway # dns-* options are implemented by the resolvconf package, if installed dns-nameservers dns-search china auto eth5 iface eth5 inet manual up ifconfig $IFACE up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto br-data iface br-data inet static address netmask </code></pre> <p>Thanks Jason</p> ",
score: 0

As you can see, the URL is https://ask.openstack.org/zh/question/12070/my-instance-can-not-obtain-ip/

Meanwhile the good one is:


As I'm iterating over the whole questions, this is a problem for me because I get the error ERR_TOO_MANY_REDIRECTS so my process got stucked there.

Stefano Maffulli (smaffulli) wrote :

does this happen only on this question or do you see the issue somewhere else, too?

Changed in openstack-community:
assignee: nobody → Evgeny Fadeev (evgeny-fadeev)
status: New → Confirmed

So nice you asked Stefano. I've made a search through all the pages of the API with the pattern '/zh/' in the URL, and I've found is not an isolated issue. Here's the list I've retrieved:


All of them matches the same behavior, the API question has the URL with the chinese path which seems to be wrong.

Replacing it with the /en/, the issue works.

Stefano Maffulli (smaffulli) wrote :

this could be an upstream issue. Evgeny: can you please shed some light on it?

Changed in openstack-community:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers