Horizon link is broken on Fuel dashboard

Bug #1435886 reported by Evgeny Sboychakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Library (Deprecated)
6.1.x
Confirmed
High
Fuel Library (Deprecated)

Bug Description

After successful development Fuel dashboard has broken link to Horizon: 172.16.53.66 when in fact it is available at 172.16.53.68

Fuel 6.1
Build: 217

Steps to reproduce:
- create environment: Ubuntu, multi-node, Neutron GRE
- add nodes: 1 controller, 3 compute
- make 10G interfaces bonding on all computes with 802.2 LACP option

Files on Controller node containing record "172.16.53.66":
/etc/hiera/globals.yaml
/etc/primary-controller.yaml
/etc/nova/nova.conf
/etc/heat/heat.conf
/etc/haproxy/conf.d/160-heat-api.cfg
/etc/haproxy/conf.d/070-cinder-api.cfg
/etc/haproxy/conf.d/050-nova-api-2.cfg
/etc/haproxy/conf.d/161-heat-api-cfn.cfg
/etc/haproxy/conf.d/020-keystone-1.cfg
/etc/haproxy/conf.d/080-glance-api.cfg
/etc/haproxy/conf.d/085-neutron.cfg
/etc/haproxy/conf.d/015-horizon.cfg
/etc/haproxy/conf.d/040-nova-api-1.cfg
/etc/haproxy/conf.d/162-heat-api-cloudwatch.cfg
/etc/haproxy/conf.d/120-swift.cfg
/etc/haproxy/conf.d/170-nova-novncproxy.cfg

Files on Controller node containing record "172.16.53.68":
/etc/hiera/nodes.yaml
/etc/hiera/globals.yaml
/etc/primary-controller.yaml
/etc/network/interfaces.d/ifcfg-br-ex
/etc/iptables/rules.v4

Revision history for this message
Evgeny Sboychakov (ysboychakov) wrote :
Changed in fuel:
importance: Undecided → Medium
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

172.16.53.66 is your public_vip where Haproxy provides frontend for Horizon
172.16.53.68 is node-8 (primary-controller) IP

Fuel provides link to Horizon using public_vip, so it gave you correct link. According to haproxy log Horizon backend was up and running:

2015-03-23T18:03:33.859527+00:00 notice: Server horizon/node-8 is UP, reason: Layer7 check passed, code: 200, info: "OK", check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.

So Horizon should be available via http://172.16.53.66/ on your env. Please double-check and if still no luck please provide more detailed problem desciption including exact error message you're getting while accessing Horizon link.

Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
Revision history for this message
Evgeny Sboychakov (ysboychakov) wrote :

The bug reproduced in Fuel 6.1 build 277

No ping from outside to 172.16.53.66, only 172.16.53.68 is accessible both by icmp and through http.
172.16.53.66 only accessible from Controller node itself.

Particularly in Nova configuration both 172.16.53.66 and 172.16.53.68 are not accessible.

Revision history for this message
Evgeny Sboychakov (ysboychakov) wrote :
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Evgeny, could you please provide correct versioning information including fuel commit SHA. You can find it getting http://<master_ip>/api/version

According to our build system Build # 277 was marked as failed, so I suggest that you try another green build and tell us if the bug is gone - I am marking it Incomplete for a while.

Revision history for this message
Evgeny Sboychakov (ysboychakov) wrote :

The correct buil No is 266 not 277

Here are below all the info you've asked for:

{"build_id": "2015-04-02_11-31-45", "ostf_sha": "f857d25eb062af03538f9c0ccf154b4d1d1b0aee", "build_number": "266", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-04-02_11-31-45", "ostf_sha": "f857d25eb062af03538f9c0ccf154b4d1d1b0aee", "build_number": "266", "api": "1.0", "nailgun_sha": "325e8a5b3ec1056149ef3b4dd5ddcb6991d118a5", "production": "docker", "python-fuelclient_sha": "9b0b6ab2f09ff75445550b7210104e21df5d8cd6", "astute_sha": "06b8dd1a4ba24b013d696ff4b73deea07cc90128", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "0531641add9670e94e467954dbdc1a7f1870f591", "fuellib_sha": "091748533839079ea854890ad793ee56898857d2"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "325e8a5b3ec1056149ef3b4dd5ddcb6991d118a5", "production": "docker", "python-fuelclient_sha": "9b0b6ab2f09ff75445550b7210104e21df5d8cd6", "astute_sha": "06b8dd1a4ba24b013d696ff4b73deea07cc90128", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "0531641add9670e94e467954dbdc1a7f1870f591", "fuellib_sha": "091748533839079ea854890ad793ee56898857d2"}

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Evgeniy, can you give a try to another build - it's been more than 2 weeks since build #266 - lots of bugs were fixed and our code was stabilized. If the bug is not reproduced, please close it as invalid or provide more information, e.g. the error code which you get while trying to access Horizon/Nova along with results of pinging particular IP addresses

Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Guys,

The fix for this was merged the day after current build was created. Closing as duplicate.

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.