Mirantis OpenStack

Instance Name column is empty in Overview page in horizon after MOS Update

Bug #1713886 reported by Josue Palmerin on 2017-08-30

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Mirantis OpenStack	Fix Released	High	Alexey Stupnikov	Mirantis OpenStack 8.0-mu-6
	9.x	Invalid	High	Alexey Stupnikov	Mirantis OpenStack 9.x-updates

Bug Description

Detailed bug description:

The "Instance Name" column under "Overview" page in Horizon is empty after the application of Maintenance Update 5 for MOS 8.0

Steps to reproduce:

Apply Maintenance Update 5 for MOS 8.0. Then try to list instance in Overview page for Horizon

Go to the following link <OPENSTACK_ENV>/horizon/project/

Expected results:

List of Instances and resources consumed by the cloud for a given project.

Actual result:

List of resources and details, however Instance Name field is empty.

Reproducibility:

100%

Impact:

Unable to identify instance for which resources are being consumed.

[root@fuel ~]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "570"
  build_id: "570"
  fuel-nailgun_sha: "558ca91a854cf29e395940c232911ffb851899c1"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "c2a335b5b725f1b994f78d4c78723d29fa44685a"
  fuel-ostf_sha: "3bc76a63a9e7d195ff34eadc29552f4235fa6c52"
  fuel-mirror_sha: "fb45b80d7bee5899d931f926e5c9512e2b442749"
  fuelmenu_sha: "78ffc73065a9674b707c081d128cb7eea611474f"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "d605bcbabf315382d56d0ce8143458be67c53434"

Tags:

Revision history for this message

Josue Palmerin (jpalmerin) wrote on 2017-08-30:

Screen Shot 2017-08-29 at 8.40.00 PM.png Edit (141.5 KiB, image/png)

Denis Meltsaykin (dmeltsaykin) on 2017-08-31

Changed in mos:
importance:	Undecided → High
status:	New → Confirmed
assignee:	nobody → MOS Maintenance (mos-maintenance)

Alexey Stupnikov (astupnikov) on 2017-08-31

Changed in mos:
assignee:	MOS Maintenance (mos-maintenance) → Alexey Stupnikov (astupnikov)

Revision history for this message

Alexey Stupnikov (astupnikov) wrote on 2017-08-31:

Reproduced in our lab. Issue is CONFIRMED.

Revision history for this message

Fuel Devops McRobotson (fuel-devops-robot) wrote on 2017-08-31: Fix proposed to openstack/horizon (openstack-ci/fuel-8.0/liberty)

Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/36377

Changed in mos:
status:	Confirmed → In Progress

Revision history for this message

Alexey Stupnikov (astupnikov) wrote on 2017-08-31:

Will try to revert the patch https://review.fuel-infra.org/#/c/36377/ and check the outcome.

Revision history for this message

Alexey Stupnikov (astupnikov) wrote on 2017-08-31:

Reverted patch actually fixes the issue. I will try to fix it with a minor change and will proceed with revert in case of failure.

Revision history for this message

Fuel Devops McRobotson (fuel-devops-robot) wrote on 2017-09-01:

Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/36388

Revision history for this message

Fuel Devops McRobotson (fuel-devops-robot) wrote on 2017-09-01: Change abandoned on openstack/horizon (openstack-ci/fuel-8.0/liberty)

Change abandoned by Alexey Stupnikov <email address hidden> on branch: openstack-ci/fuel-8.0/liberty
Review: https://review.fuel-infra.org/36377
Reason: I have a better fix I99cb7cc2e14157e40e4b4de83bbf51d6e5c881c6

Denis Meltsaykin (dmeltsaykin) on 2017-09-05

Changed in mos:
milestone:	8.0-updates → 8.0-mu-6

Revision history for this message

Fuel Devops McRobotson (fuel-devops-robot) wrote on 2017-09-05: Fix merged to openstack/horizon (openstack-ci/fuel-8.0/liberty)

Reviewed: https://review.fuel-infra.org/36388
Submitter: Pkgs Jenkins <email address hidden>
Branch: openstack-ci/fuel-8.0/liberty

Commit: 4e31a582603ebdb6e123f91d3669b5ea4ee47256
Author: Alexey Stupnikov <email address hidden>
Date: Fri Sep 1 14:23:42 2017

Fix project overview page

Change I4d805e4a65e838242af38677cbb9efefc498a96f broke
project/overview page. This patch fixes VMs usage table
and brings back instance names into the table.

Change-Id: I99cb7cc2e14157e40e4b4de83bbf51d6e5c881c6
Closes-bug: #1713886

Changed in mos:
status:	In Progress → Fix Committed

Denis Meltsaykin (dmeltsaykin) on 2017-09-05

no longer affects:

mos/8.0.x

Revision history for this message

Alexey Stupnikov (astupnikov) wrote on 2017-09-05:

I was unable to reproduce this issue in stable/mitaka. For some reason, this bug came up in pretty much any version except 9.0.

Revision history for this message

Alexey Stupnikov (astupnikov) wrote on 2017-09-06:

#10

I was unable to reproduce this issue for 9.0/mitaka, mcp/newton and mcp/ocata branches. I have doublechecked the possible reasons and found the changes made to fix bug #1572153 that effectively fix this issue in those branches. It looks like devcloud should be updated and this bug should be effectively closed as invalid for those products.

https://review.fuel-infra.org/#/q/topic:bug/1572153

Revision history for this message

Josue Palmerin (jpalmerin) wrote on 2017-09-08:

#11

Alexey we have one more problem. Seems the issue also affected Stack resources View in Horizon.

I added the same parameter to the following files in the customer environment and it fixed the issue.

/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/stacks/tables.py
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/stacks/mappings.py

Lets also include the fix in both those files.

Revision history for this message

Alexey Stupnikov (astupnikov) wrote on 2017-09-08:

#12

@jpalmerin: thanks for posting update. It is seem to be a general issue and IMO it is better to propose general solution. I will nominate bug #1572153 for MOS8 and will fix the problem you reported there.

Revision history for this message

Vladimir Jigulin (vjigulin) wrote on 2017-12-08:

#13

Verified on 8+mu6updates