Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1720173

Summary: NoOptionError: No option 'region' in section: 'identity'
Product: Red Hat OpenStack Reporter: Attila Fazekas <afazekas>
Component: openstack-packstackAssignee: Alfredo Moralejo <amoralej>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: jjoyce
Target Milestone: z7Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-packstack-12.0.0-7.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1721085 (view as bug list) Environment:
Last Closed: 2019-07-10 12:17:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Attila Fazekas 2019-06-13 10:13:36 UTC
This bug was initially created as a copy of Bug #1716434

I am copying this bug because: 
The issue exists with the 13 major version as well.
Please backport it to 13 as well.



Description of problem:
Discover config fails as part of InfraRed Tempest run, packstack deployment only:

root@aio $ /usr/bin/discover-tempest-config --debug -v --create --image http://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img identity.uri $OS_AUTH_URL identity.admin_password $OS_PASSWORD scenario.img_dir ~/tempest-dir/etc --out ~/tempest-dir/etc/tempest.conf

...
DEBUG config_tempest.constants [-] Setting [heat_plugin] admin_password = redhat set /usr/lib/python2.7/site-packages/config_tempest/tempest_conf.py:107
DEBUG config_tempest.constants [-] Setting [heat_plugin] project_name = demo set /usr/lib/python2.7/site-packages/config_tempest/tempest_conf.py:107
CRITICAL tempest [-] Unhandled error: NoOptionError: No option 'region' in section: 'identity'
ERROR tempest Traceback (most recent call last):
ERROR tempest   File "/usr/bin/discover-tempest-config", line 10, in <module>
ERROR tempest     sys.exit(main())
ERROR tempest   File "/usr/lib/python2.7/site-packages/config_tempest/main.py", line 597, in main
ERROR tempest     verbose=args.verbose
ERROR tempest   File "/usr/lib/python2.7/site-packages/config_tempest/main.py", line 519, in config_tempest
ERROR tempest     services = Services(clients, conf, credentials)
ERROR tempest   File "/usr/lib/python2.7/site-packages/config_tempest/services/services.py", line 42, in __init__
ERROR tempest     self.discover()
ERROR tempest   File "/usr/lib/python2.7/site-packages/config_tempest/services/services.py", line 111, in discover
ERROR tempest     service.set_default_tempest_options(self._conf)
ERROR tempest   File "/usr/lib/python2.7/site-packages/config_tempest/services/orchestration.py", line 42, in set_default_tempest_options
ERROR tempest     conf.set(sec, 'region', conf.get('identity', 'region'))
ERROR tempest   File "/usr/lib64/python2.7/ConfigParser.py", line 618, in get
ERROR tempest     raise NoOptionError(option, section)
ERROR tempest

Version-Release number of selected component (if applicable):
OSP14, puddle 2019-05-31.1

Steps to Reproduce:
1. Deploy OSP14 using packstack and IR
2. Run Tempest deployment

Additional info:
It seems that the difference between last working job and the new failing one is:
python2-tempestconf-2.2.0-0.20190507153823.e0d5dd6.el7ost.noarch <- new
python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost <- from latest passing job, previous puddle
# the discover command is the same for both builds

Comment 1 Alfredo Moralejo 2019-06-13 13:13:35 UTC
fixed in openstack-packstack-12.0.0-7.el7ost

Comment 6 errata-xmlrpc 2019-07-10 12:17:21 UTC
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:1729