deployment fails because of malformed yaml due to missing ips from hosts file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
Critical
|
Unassigned |
Bug Description
On a deployment deploy_
2018-02-08 12:19:46 | The error appears to have been in '/var/lib/
2018-02-08 12:19:47 | be elsewhere in the file depending on the eOvercloud configuration failed.
2018-02-08 12:19:47 | END return value: 1
2018-02-08 12:19:47 | xact syntax problem.
2018-02-08 12:19:47 |
2018-02-08 12:19:47 | The offending line appears to be:
2018-02-08 12:19:47 |
2018-02-08 12:19:47 | overcloud.
2018-02-08 12:19:47 | 192.168.24.3 centos-
2018-02-08 12:19:47 | ^ here
2018-02-08 12:19:47 |
2018-02-08 12:19:47 | exception type: <class 'yaml.parser.
2018-02-08 12:19:47 | exception: while parsing a block mapping
2018-02-08 12:19:47 | in "<unicode string>", line 2377, column 7
2018-02-08 12:19:47 | did not find expected key
2018-02-08 12:19:47 | in "<unicode string>", line 2386, column 9
The error happens on this piece of yaml
<.... snip, snip...>
ControllerHosts
config: |
<.... snip, snip...>
creation_time: "2018-02-
deployment_name: ControllerHosts
group: script
id: b590a39d-
inputs:
- name: hosts
description:
type: String
value: |-
<.... snip, snip...>
From what I can see it is related to http://
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Critical |
tags: | added: alert ci |
Problem seems to be gone. Not sure what fixed it but I'm not seeing it anymore. Marked as invalid because of that. If it reappears we can reopen the bug