Bug 1668774
Summary: | OSP Director - handle lowercase uuid change for dmidecode >= 3.1 for ceph-ansible per-node customizations | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Matt Flusche <mflusche> | |
Component: | openstack-tripleo-common | Assignee: | Francesco Pantano <fpantano> | |
Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 13.0 (Queens) | CC: | ccopello, elicohen, fpantano, gfidente, joflynn, mburns, mflusche, shdunne, slinaber, troels, yrabl | |
Target Milestone: | z5 | Keywords: | Triaged, ZStream | |
Target Release: | 13.0 (Queens) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-tripleo-common-8.6.6-16.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
This bug was caused by updated versions of dmidecode 3.1 or later that returned system UUIDs in lowercase. As a consequence, systems deployed with per node ceph-ansible customization prior to this version can break if UUID case mismatches and cause deployment failures. This fix updates the `openstack-tripleo-common` package to accept uppercase or lowercase UUIDs. Forced lowercase on dmidecode output make the code case insensitive.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1671049 1671065 (view as bug list) | Environment: | ||
Last Closed: | 2019-03-14 13:55:11 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1671049 | |||
Bug Blocks: |
Description
Matt Flusche
2019-01-23 14:59:51 UTC
it looks like this was an issue introduced in dmidecode 3.1 and fixed starting from 3.2, see https://github.com/mirror/dmidecode/commit/aec83995082070c47edf394c4b7f9f17fea7fd16 and https://savannah.nongnu.org/bugs/index.php?53569 we'll probably need to ensure our code makes case-insesitive matching anyway Seems like the relevant fix is not in the code base for osp 13. Puddle used was 2019-02-25.2 The file /usr/share/openstack-tripleo-heat-templates/docker/services/ceph-ansible/ceph-base.yaml is missing the new code as per https://github.com/openstack/tripleo-heat-templates/commit/c01d9d8475d7b256fed944227a06f028e8d487f8 Clarification. Fix is in code base, other code may be missing, resulting in the following error upon deployment: 2019-02-28 19:36:53Z [overcloud]: CREATE_FAILED Resource CREATE failed: resources.WorkflowTasks_Step2_Execution: resources.AllNodesDeploySteps.Failure caused by error in tasks: ceph_base_ansible_workflow ceph_base_ansible_workflow [task_ex_id=d7318d1f-6f92-4f63-bd8a-8a72a6872eae] -> Failed to handle Stack overcloud CREATE_FAILED overcloud.AllNodesDeploySteps.WorkflowTasks_Step2_Execution: resource_type: OS::TripleO::WorkflowSteps physical_resource_id: e2c5a650-2f64-4b0c-99a5-73eaac687aec status: CREATE_FAILED status_reason: | ... File "/usr/lib/python2.7/site-packages/mistral/expressions/__init__.py", line 79, in _evaluate_item return evaluate(item, context) File "/usr/lib/python2.7/site-packages/mistral/expressions/__init__.py", line 71, in evaluate return evaluator.evaluate(expression, context) File "/usr/lib/python2.7/site-packages/mistral/expressions/yaql_expression.py", line 119, in evaluate cls).evaluate(trim_expr, data_context) File "/usr/lib/python2.7/site-packages/mistral/expressions/yaql_expression.py", line 73, in evaluate ", data=%s]" % (expression, str(e), data_context) YaqlEvaluationException: Can not evaluate YAQL expression [expression=json_parse($.node_data_lookup), error=Expecting property name enclosed in double quotes: line 1 column 2 (char 1), data={}] Returned to QA - Deployment should be done with NodeDataLookup as json string in osp13, not json. Retest Tested with NodeDataLookup passed as json string and verified as fixed 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/RHBA-2019:0448 |