[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata

[Corey Bryant]

I've just compared jquery.bootstrap.wizard.js files from 2 installations:
1) installed openstack-dashboard newton and upgraded to ocata
2) installed openstack-dashboard ocata

/usr/share/openstack-dashboard/horizon/static/horizon/lib/jquery/jquery.bootstrap.wizard.js
and
/var/lib/openstack-dashboard/static/horizon/lib/jquery/jquery.bootstrap.wizard.js
are the same for both installations (after upgrade to ocata for 1st installation).

Note that this is just an openstack-dashboard package install. I
currently don't have a test environment for charms but will try again
with charms once our test environment is back up and running.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1775170

Title:
  [SRU] Fixing empty create swift container dialog after upgrading
  horizon from newton to ocata

Status in Ubuntu Cloud Archive:
  New
Status in horizon package in Ubuntu:
  New

Bug description:
  [Impact]

  After upgrading openstack-dashboard from newton to ocata
  Create Container dialog show us empty dialog.

  I'm sure this is needed for ocata UCA
  but not sure pike or newer version.
  because upgrading 2 steps is not recommended.
  Please let me know if the patch for the other releases are also needed.
  e.g from newton to pike or from xenial to Z A B?

  [Test Case]

  1. deploy newton env with object store
  2. check if create container dialog show us proper contents ( yes )
  3. upgrade newton to coat
  4. check if create container dialog show us proper contents ( no )

  [Regression Potential]
  After this patch, every installing or upgrading try to delete specific directories and files that no need in ocata anymore. affected file are related to newton only but if ocata has changes in that directory, that file also can be deleted. but this case unlikely happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions