Red Hat Bugzilla – Bug 1298723
Problem with setting retirement date on Workloads explorer
Last modified: 2016-02-10 10:35:16 EST
+++ This bug was initially created as a clone of Bug #1298722 +++ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/717
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=abf3fdd2d74f056a56c6d67bd15b56b63e650288 commit abf3fdd2d74f056a56c6d67bd15b56b63e650288 Author: Hanna Novikava <arnikasky@gmail.com> AuthorDate: Thu Jan 14 07:42:15 2016 -0500 Commit: Harpreet Kataria <hkataria@redhat.com> CommitDate: Thu Jan 14 16:22:38 2016 -0500 Update ci_processing.rb https://bugzilla.redhat.com/show_bug.cgi?id=1298722 https://bugzilla.redhat.com/show_bug.cgi?id=1298723 (cherry picked from commit b0c78ff) app/controllers/application_controller/ci_processing.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=a5bcb0601369a423c94d9f3b8b1c12e8d73235b1 commit a5bcb0601369a423c94d9f3b8b1c12e8d73235b1 Merge: d8a2146 abf3fdd Author: Dan Clarizio <dclarizi@redhat.com> AuthorDate: Thu Jan 14 18:35:01 2016 -0500 Commit: Dan Clarizio <dclarizi@redhat.com> CommitDate: Thu Jan 14 18:35:01 2016 -0500 Merge branch '55z_pr_6182' into '5.5.z' Update ci_processing.rb https://bugzilla.redhat.com/show_bug.cgi?id=1298722 https://bugzilla.redhat.com/show_bug.cgi?id=1298723 (cherry picked from commit b0c78ff) @dclarizi please review/merge, clean cherry-pick for https://github.com/ManageIQ/manageiq/pull/6182 See merge request !717 app/controllers/application_controller/ci_processing.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Created attachment 1120494 [details] retirement date Verified in 5.5.2.4.20160127105142_395c086
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-2016:0159