Mismatch url while requesting a question

Bug #1486678 reported by Alberto Martín
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Community Project
Confirmed
High
Evgeny Fadeev

Bug Description

Hi,

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:

https://ask.openstack.org/en/api/v1/questions/12070

It returns a JSON with a wrong URL:

{
tags: [
"instance",
"not",
"obtain",
"ip"
],
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 192.168.3.253 netmask 255.255.255.0 #For Exposing OpenStack API over the internet #auto eth0 #iface eth0 inet manual #up ifconfig $IFACE 0.0.0.0 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 10.141.127.253 netmask 255.255.255.0 network 10.141.127.0 broadcast 10.141.127.255 gateway 10.141.127.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 10.72.255.100 dns-search china auto eth5 iface eth5 inet manual up ifconfig $IFACE 0.0.0.0 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 10.0.0.253 netmask 255.255.255.0 </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:

https://ask.openstack.org/en/question/12070/my-instance-can-not-obtain-ip/

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.

Tags: askproject
Revision history for this message
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
Revision history for this message
Alberto Martín (alberto-martin-s) wrote :

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:

https://ask.openstack.org/zh/question/12070/my-instance-can-not-obtain-ip/
https://ask.openstack.org/zh/question/4143/openstack-with-vmware-esxi-as-hypervisor/
https://ask.openstack.org/zh/question/25877/when-the-public-endpoint-will-be-used/
https://ask.openstack.org/zh/question/5396/helpvolume-attach-to-instance-not-success/
https://ask.openstack.org/zh/question/9307/openstack-network-settinghow-to-set-flat_interface-and-public_interface-in-this-situation/
https://ask.openstack.org/zh/question/9548/installation-nova-computer-kvm-problems-encountered-for-grizzly/
https://ask.openstack.org/zh/question/5088/how-many-instance-could-openstack-create/
https://ask.openstack.org/zh/question/6196/programmingerror-programmingerror-1146-table-novaservices-doesnt-exist/
https://ask.openstack.org/zh/question/5858/set-admin-password-is-not-implemented-by-this-driver-or-guest-instance/
https://ask.openstack.org/zh/question/5284/can-the-openstack-nova-computing-node-be-directly-installed-on-the-exsi/
https://ask.openstack.org/zh/question/5089/an-instance-couldnt-release-its-resourcevcpu-rom-etc-only-if-it-is-terminated-and-whats-the-reason-could-somebody-tell-me/
https://ask.openstack.org/zh/question/4544/openstack-instance-status-error/
https://ask.openstack.org/zh/question/4138/is-grizzly-compatible-with-mysql-cluster/
https://ask.openstack.org/zh/question/4050/instance-cannot-be-boot-after-power-maintenance-of-openstack-server-farm/
https://ask.openstack.org/zh/question/3744/the-proxy-node-in-swift/

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.

Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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