missing files on jammy install: _launch_instances_network_help.html and update_networks.html

[Corey Bryant]

[Impact]

Gabriel Safira reports:

It seems that the trove-dashboard package in Jammy is missing 2 template files without which there is no way to launch a database instance from the dashboard:

_update_networks.html

_launch_instances_network_help.html

They seem to be there in the source package, but it's missing from the installed package.

I downloaded the source package:

apt-get source python3-trove-dashboard cd trove-dashboard-18.0.0/ cp ./trove_dashboard/content/databases/templates/databases/_launch_instances_network_help.html /usr/lib/python3/dist-packages/trove_dashboard/content/databases/templates/databases/_launch_instances_network_help.html cp ./trove_dashboard/content/databases/templates/databases/_update_networks.html /usr/lib/python3/dist-packages/trove_dashboard/content/databases/templates/databases/_update_networks.html

And I can now click on "Launch instance" in the dashboard and no longer get an error message.

[Test Case]

Ensure jammy package build includes the missing files. e.g.
https://launchpadlibrarian.net/594248928/buildlog_ubuntu-jammy-amd64.trove-dashboard_18.0.0-0ubuntu1_BUILDING.txt.gz

Deploy openstack with trove-dashboard and ensure "Launch instance" works.

[Regression Potential]
The patch has been available in the upstream stable/yoga branch since Apr 21, 2022 (https://review.opendev.org/c/openstack/trove-dashboard/+/838700). The dashboard isn't functional without this fix.

[Discussion]
We've had a version of this patch in the package since the release of jammy, but for some reason the new files aren't being installed. The MANIFEST.in looks correct. Update: Adding the files to the egg sources fixes this.

[Corey Bryant (corey.bryant)]

The fixed package version has been uploaded to the jammy unapproved queue: https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=trove-dashboard

[Timo Aaltonen (tjaalton)]

Hello Corey, or anyone else affected,

Accepted trove-dashboard into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/trove-dashboard/18.0.0-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Gabriel Samfira (gabriel-samfira)]

I have tested the updated package in our environment and it seems to work as expected. Thanks for the fix!

[Launchpad Janitor (janitor)]

This bug was fixed in the package trove-dashboard - 18.0.0-0ubuntu1.1

---------------
trove-dashboard (18.0.0-0ubuntu1.1) jammy; urgency=medium

  * d/gbp.conf: Create stable/yoga branch.
  * d/p/add-missing-files-to-egg-sources.patch: Add missing files
    to egg sources to ensure they are installed (LP: #2039318).

 -- Corey Bryant <email address hidden> Mon, 16 Oct 2023 17:53:20 -0400

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for trove-dashboard has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.