Created attachment 1458030 [details]
Description of problem:
the overcloud_update_setup.sh script exit with an error:
"The Resource Type (OS::TripleO::Services::ManilaBackendGeneric) could not be found"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. instal osp12 GA
2. Update to passed_phase2 (in this test 2018-06-29.1)
see attached tar for home/stack files,
more logs and sosreport can be found in the job
Hey Raviv, the logs provided are not available anymore. Also, I downloaded the home directory logs and there are not enough data to know what happened. Could you please provide the heat templates version it was installed to? I guess that info can be found in the job logs, so it would be great if you could paste some new logs from the job.
Please provide full logs from the job if possible. The pasted one are not accessible anymore. Thanks
The mistral log from undercloud is attahced,
Additional logs from overcloud nodes, can be found in the job page on production Jenkins:
If you need additional info or logs please let me know.
Created attachment 1470238 [details]
undercloud mistral logs
This bug seems really similar to this other Yurii opened https://bugzilla.redhat.com/show_bug.cgi?id=1541382 . There is a preparation task inside tripleo-upgrade . The ManilaBackendGeneric service has been deprecated, so we need to remove it from the roles_data.yml, or it would be possible to add the tasks used for major upgrade which convert the roles_data in tripleo-upgrade repo: https://github.com/openstack/tripleo-upgrade/commit/38e9f537f14a1d518ec29c0794730728d4fca365
I updated the External Tracker with the patch that removes the generic driver template from stable/pike. It is downstream, though not in OSP12 GA. For updating from GA (which by definition we cannot change) to a later Z-stream where it is fixed perhaps an update doc note indicating to edit as noted above would be appropriate?
I order to test and promote the patch I'm trying to deploy fresh osp12 GA on a private setup in TLV lab.
Unfortunately, deployment fails with sporadic errors,
last one I have is:
"failed: Update does not conform to the configured schema"
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.