improve handling of empty resource_registry in env file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Low
|
John Fulton |
Bug Description
If a user runs 'openstack overcloud deploy ... -e foo.yaml' where foo.yaml contains only:
$ cat foo.yaml
resource_registry:
$
The deployment will fail with the following:
Exception occured while running the command
Traceback (most recent call last):
File "/usr/lib/
super(Command, self).run(
File "/usr/lib/
return super(Command, self).run(
File "/usr/lib/
return_code = self.take_
File "/usr/lib/
parsed_
File "/usr/lib/
check_
File "/usr/lib/
service in content[
TypeError: argument of type 'NoneType' is not iterable
argument of type 'NoneType' is not iterable
While we could say a user shouldn't pass an empty resource_registry it would also be nice if we could handle it better. Basically if the resource_registry is empty in an env file, just ignore it.
Fix proposed to branch: master /review. opendev. org/666895
Review: https:/