Description of problem: ----------------------- Overcloud upgrade fails during package update on overcloud: ... Transaction check error: file /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.d from install of openstack-dashboard-1:14.0.1-0.20180903221923.e975afd.el7ost.2.noarch conflicts with file from package openstack-dashboard-1:13.0.1-2.el7ost.noarch Version-Release number of selected component (if applicable): ------------------------------------------------------------- openstack-dashboard-theme-13.0.0-1.el7ost.noarch openstack-dashboard-13.0.1-2.el7ost.noarch How reproducible: ----------------- 100% Steps to Reproduce: ------------------- 1. Upgrade RHOS-13 uc to RHOS-14 2. Prepare overcloud to upgrade(repos/docker images) 3. Setup upgrade playbooks(openstack overcloud upgrade prepare ...) 4. Run upgrade of Controller role: openstack overcloud upgrade run \ --stack overcloud \ --roles Controller --playbook all 2>&1 Actual results: --------------- Upgrade fails Additional info: ---------------- Virtual setup: 3controllers + 2computes + 3ceph
This looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1406746
And also https://bugzilla.redhat.com/show_bug.cgi?id=1361148
I wonder where openstack-dashboard-1:14.0.1 came from, because the latest spec we have downstream is for openstack-dashboard-1:14.0.0-1
I could not reproduce this with the latest puddles for osp13 and osp14 in packstack. I suspect there may be some tripleo magic in play here.
Actually I spoke too fast, I got: Transaction check error: file /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.d from install of openstack-dashboard-1:14.0.1-0.20180903221923.e975afd.el7ost.2.noarch conflicts with file from package openstack-dashboard-1:13.0.1-2.el7ost.noarch
I see the problem. In OSP13 that directory is a symlink to one in /etc, but OSP14 undid that.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days