Bug 1215516
| Summary: | OpenStack - "unknown attribute: state" when trying to terminate an instance. | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Nikhil Gupta <ngupta> |
| Component: | Providers | Assignee: | Greg Blomquist <gblomqui> |
| Status: | CLOSED ERRATA | QA Contact: | Shveta <sshveta> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.3.0 | CC: | dajohnso, dclarizi, drieden, gblomqui, jfrey, jhardy, mfalesni, mfeifer, obarenbo, sshveta |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.3.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.3.5.1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1212052 | Environment: | |
| Last Closed: | 2015-07-15 12:55:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1212052 | ||
| Bug Blocks: | |||
|
Comment 1
Nikhil Gupta
2015-04-27 04:58:43 UTC
New commit detected on cfme/5.3.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=150813561fea1dee7a04f9b5f2f9fb17f596d3f1 commit 150813561fea1dee7a04f9b5f2f9fb17f596d3f1 Author: Greg Blomquist <gblomqui> AuthorDate: Mon Apr 20 11:46:41 2015 -0400 Commit: Greg Blomquist <gblomqui> CommitDate: Thu May 7 15:31:03 2015 -0400 Destroying an OpenStack VM should not set state attr The state attribute on VMs is read only and used purely as a normalization layer in order to display a common state for all different types of VMs. When VMs are destroyed (or, otherwise acted upon), the appliance will set a temporary power state in order to reflect the impending change that's been submitted to the provider. The change submitted to the provider is handled largely asynchronously with any updates from the change coming in the form of events received after the fact. The temporary power state change when destroying OpenStack VMs was trying to set the state attribute. By changing that to the raw_power_state attribute, the power state is updated and reflected in the read only state attribute. https://bugzilla.redhat.com/show_bug.cgi?id=1215516 Conflicts: vmdb/app/models/vm_openstack/operations.rb vmdb/app/models/vm_openstack/operations.rb | 6 +++--- vmdb/spec/models/vm_openstack_spec.rb | 17 +++++++++++++++++ 2 files changed, 20 insertions(+), 3 deletions(-) New commit detected on cfme/5.3.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=9ed62f9bef2cc910eb4d0aaf302c326e4dcd8967 commit 9ed62f9bef2cc910eb4d0aaf302c326e4dcd8967 Merge: 00cfc41 1508135 Author: Jason Frey <jfrey> AuthorDate: Thu May 7 16:31:16 2015 -0400 Commit: Jason Frey <jfrey> CommitDate: Thu May 7 16:31:16 2015 -0400 Merge branch 'bz1215516-cherrypick-1212052' into '5.3.z' Destroying an OpenStack VM should not set state attr The state attribute on VMs is read only and used purely as a normalization layer in order to display a common state for all different types of VMs. When VMs are destroyed (or, otherwise acted upon), the appliance will set a temporary power state in order to reflect the impending change that's been submitted to the provider. The change submitted to the provider is handled largely asynchronously with any updates from the change coming in the form of events received after the fact. The temporary power state change when destroying OpenStack VMs was trying to set the state attribute. By changing that to the raw_power_state attribute, the power state is updated and reflected in the read only state attribute. https://bugzilla.redhat.com/show_bug.cgi?id=1215516 Conflicts: vmdb/app/models/vm_openstack/operations.rb See merge request !44 vmdb/app/models/vm_openstack/operations.rb | 6 +++--- vmdb/spec/models/vm_openstack_spec.rb | 17 +++++++++++++++++ 2 files changed, 20 insertions(+), 3 deletions(-) Configuration/tasks does not show error . instance terminates and disappears Verified in 5.3.5.1.20150630091250_5515226 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://rhn.redhat.com/errata/RHBA-2015-1223.html |