Description of problem: nova-scheduler distinguish availability zone in metadata or CONF.default_availability_zone. However, scheduler.pp doesn't contain nova::availability_zone class. Because of that, nova.conf for nova-scheduler in controller needs to be updated manually. It should be included in scheduler.pp. This trigger a failure of instance creation with volume when a user defines an availability zone in Cinder and cross_az_attach option in nova.conf is false. Version-Release number of selected component (if applicable): puppet-nova-12.4.0-17 How reproducible: Always Steps to Reproduce: 1. Configure availability_zone in cinder and nova through director. ~~~ parameter_defaults: ExtraConfig: nova::availability_zone::default_availability_zone: "AZ_TEST" cinder::storage_availability_zone: "AZ_TEST" ~~~ 2. After deployment, try to launch the instance with volume. 3. Actual results: The instance creation failed. Expected results: The instance creation succeed. Additional info: The issue is filed as https://bugs.launchpad.net/puppet-nova/+bug/1824273 And Gerrit is https://review.openstack.org/#/c/651690/
Hi Rajesh, The gerrit for master branch was merged status. Now, the fix is being proposed to stable/rocky and stable/queens branch. Would you please follow-up those gerrits in upstream? Kind Regards, Keigo Noha
Hi Keigo, Thanks for the update. I will backport those patches downstream in OSP14 and OSP13, as soon as they are merged upstream.
Hi Rajesh, All patch into stable/queens and stable/rocky was merged. Would you please backport them into RHOSP internal gerrit? Kind Regards, Keigo Noha
Hi Rajesh, Thank you for your work in upstream. In upstream, Tobias commented that the fix should not be done in puppet-nova. If the fix should be done in puppet-tripleo, I'm happy to revert a patch then put it into puppet-tripleo. Martin shared his opinion to Tobias's comment. But if I don't align to the contributor's guide or the rules in puppet-nova, I'd like to fix it. I'd like to hear your opinion to it. Kind Regards, Keigo Noha
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:1738