trove dashboard does not deploy with centos packages

Bug #1647837 reported by Chris Liles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

The run script expects trove dashboard files it be present in ${SITE_PACKAGES}/trove_dashboard/enabled/ and then copies them over to ${SITE_PACKAGES}/openstack_dashboard/local/enabled

The current delorean openstack-trove-ui does not have files in ${SITE_PACKAGES}/trove_dashboard/enabled

Revision history for this message
Chris Liles (christopherliles) wrote :

I should note if it's not clear by the delorean reference, that this is for centos-7 binary builds. Not sure if there is a change in the package standard that needs to be addressed or a defect in the package.

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

in RDO, the enable file is moved to openstack_dashboard folder. and not exist in trove folder. it is hard for kolla to identify which files should be removed.

$ rpm -ql openstack-trove-ui.noarch
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1710_database_panel_group.py
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1710_database_panel_group.pyc
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1710_database_panel_group.pyo
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1720_project_databases_panel.py
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1720_project_databases_panel.pyc
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1720_project_databases_panel.pyo
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1730_project_database_backups_panel.py
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1730_project_database_backups_panel.pyc
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1730_project_database_backups_panel.pyo
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1731_project_database_backups_panel.py
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1731_project_database_backups_panel.pyc
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1731_project_database_backups_panel.pyo
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1740_project_database_clusters_panel.py
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1740_project_database_clusters_panel.pyc
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1740_project_database_clusters_panel.pyo
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1760_project_database_configurations_panel.py
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1760_project_database_configurations_panel.pyc
/usr/share/openstack-dashboard/openstack_dashboard/local/enabled/_1760_project_database_configurations_panel.pyo

Changed in kolla:
status: New → Triaged
importance: Undecided → Critical
importance: Critical → High
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Changed in kolla:
milestone: pike-rc1 → queens-1
Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Changed in kolla:
milestone: queens-rc1 → queens-rc2
Changed in kolla:
milestone: queens-rc2 → rocky-1
Changed in kolla:
milestone: rocky-2 → rocky-3
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: High → Undecided
status: Triaged → Expired
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.