Bug 1359150 - Error when retiring an orchestration stack from list view
Summary: Error when retiring an orchestration stack from list view
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.1
Assignee: Milan Zázrivec
QA Contact: Shveta
URL:
Whiteboard: stack
Depends On:
Blocks: 1360385
TreeView+ depends on / blocked
 
Reported: 2016-07-22 12:11 UTC by Milan Zázrivec
Modified: 2022-07-09 07:47 UTC (History)
7 users (show)

Fixed In Version: 5.6.1.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1360385 (view as bug list)
Environment:
Last Closed: 2016-08-18 17:59:28 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1634 0 normal SHIPPED_LIVE Important: CFME 5.6.1 security, bug fix, and enhancement update 2016-08-18 21:43:52 UTC

Description Milan Zázrivec 2016-07-22 12:11:08 UTC 
Description of problem:
The following error occurs when retiring orchestration stack from
list view:

Error caught: [ActiveRecord::RecordNotFound] Couldn't find VmOrTemplate with 'id'=2
...
app/controllers/application_controller/ci_processing.rb:183:in `retirevms'
app/controllers/orchestration_stack_controller.rb:113:in `button'


Version-Release number of selected component (if applicable):
CFME 5.6

How reproducible:
Always

Steps to Reproduce:
1. Compute -> Cloud -> Stacks
2. From list view, select a stack
3. Policy -> Set retirement date

Actual results:
The error above.

Expected results:
No error.

Additional info:
N/A
Comment 1 Milan Zázrivec 2016-07-22 12:11:30 UTC 
https://github.com/ManageIQ/manageiq/pull/9933
Comment 3 Shveta 2016-08-02 22:17:58 UTC 
Fixed.
Verified in 5.6.1.0.20160726144018_810a94f
Comment 5 errata-xmlrpc 2016-08-18 17:59:28 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://rhn.redhat.com/errata/RHSA-2016-1634.html
Note You need to log in before you can comment on or make changes to this bug.