[openstack-dev] [heat] Unknown resource OS::Heat::ScaledResource
Hi, I observed in one of the patch mentioned below, OS::Heat::ScaledResource is reported as unknown, could anyone help here to resolve the issue. Thanks. http://logs.openstack.org/76/157376/8/check/check-heat-dsvm-functional-mysql/c9a1be3/logs/screen-h-eng.txt.gz reports OS::Heat::ScaledResource as unknown Regards Kanagaraj M __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] Unknown resource OS::Heat::ScaledResource
On Wed, Mar 11, 2015 at 3:04 AM, Zane Bitter wrote: > On 10/03/15 12:26, Manickam, Kanagaraj wrote: > >> Hi, >> >> I observed in one of the patch mentioned below, OS::Heat::ScaledResource >> is reported as unknown, could anyone help here to resolve the issue. >> Thanks. >> >> http://logs.openstack.org/76/157376/8/check/check-heat- >> dsvm-functional-mysql/c9a1be3/logs/screen-h-eng.txt.gz >> >> >> reports OS::Heat::ScaledResource as unknown >> > > Some more context for anyone looking at this: > > * The resource type mapping is stored in the environment (for all > autoscaling group nested stacks). > * The error is happening when deleting the autoscaling group - i.e. upon > loading the stack from the database the mapping is no longer present in the > environment > * https://review.openstack.org/#/c/157376/8 is the patch in question, > which is changing the way the environment is stored (evidently incorrectly) > > Yeah, I'll sort it out. It's in stack_resource.py (it's not passing the env into the template constructor. -Angus > cheers, > Zane. > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] Unknown resource OS::Heat::ScaledResource
On 10/03/15 12:26, Manickam, Kanagaraj wrote: Hi, I observed in one of the patch mentioned below, OS::Heat::ScaledResource is reported as unknown, could anyone help here to resolve the issue. Thanks. http://logs.openstack.org/76/157376/8/check/check-heat-dsvm-functional-mysql/c9a1be3/logs/screen-h-eng.txt.gz reports OS::Heat::ScaledResource as unknown Some more context for anyone looking at this: * The resource type mapping is stored in the environment (for all autoscaling group nested stacks). * The error is happening when deleting the autoscaling group - i.e. upon loading the stack from the database the mapping is no longer present in the environment * https://review.openstack.org/#/c/157376/8 is the patch in question, which is changing the way the environment is stored (evidently incorrectly) cheers, Zane. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] Unknown resource OS::Heat::ScaledResource
On Tue, Mar 10, 2015 at 04:26:28PM +, Manickam, Kanagaraj wrote: >Hi, > > > >I observed in one of the patch mentioned below, OS::Heat::ScaledResource >is reported as unknown, could anyone help here to resolve the issue. >Thanks. > > > > > http://logs.openstack.org/76/157376/8/check/check-heat-dsvm-functional-mysql/c9a1be3/logs/screen-h-eng.txt.gz > > reports OS::Heat::ScaledResource as unknown Your patch appears to introduce a regression in this test: https://github.com/openstack/heat/blob/master/heat_integrationtests/functional/test_autoscaling.py#L636 You can see we override the normal mapping from OS::Heat::ScaledResource to AWS::EC2::Instance - the instance resource is overridden by provider.yaml in this test, which I assume means you're breaking the environment somehow in your patch and losing that mapping. Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
