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

[Seyeong Kim]

Hello,

I verified this issue fixed.

Below are steps I followed

1. deploy newton env.
2. upgrade it to ocata.
3. check if there is ui error ( it was )
4. upgrade pkg from -proposed ocata
5. check if there is ui error ( it's gone )

Thanks a lot

root at juju-4a8232-0-lxd-5:~# dpkg -l | grep dashboard
ii  openstack-dashboard              3:11.0.4-0ubuntu1~cloud2.5                 all          Django web interface for OpenStack
ii  openstack-dashboard-ubuntu-theme 3:11.0.4-0ubuntu1~cloud2.5                 all          Transitional dummy package for Ubuntu theme for Horizon

** Tags removed: verification-ocata-needed
** Tags added: verification-ocata-done

-- 
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:
  Invalid
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in horizon package in Ubuntu:
  Invalid

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