Bug 1326866 - Setting an empty VM Note in VMware does not clear the VM | Container | Notes field
Summary: Setting an empty VM Note in VMware does not clear the VM | Container | Notes ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Adam Grare
QA Contact: Alex Newman
URL:
Whiteboard: vmware
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-13 15:02 UTC by Josh Carter
Modified: 2019-11-14 07:47 UTC (History)
5 users (show)

Fixed In Version: 5.6.0.5
Doc Type: Bug Fix
Doc Text:
Previously, setting an empty note did not clear the text from the Annotations field on a VMware virtual machine when the provider is refreshed. This happened because CloudForms did not correctly parse the empty field. This has been fixed in the code by setting hardware[:annotation] to nil if the config.annotation property is blank. As a result, CloudForms now interprets an empty Annotations field as expected.
Clone Of:
Environment:
Last Closed: 2016-06-29 15:49:06 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 RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Comment 2 CFME Bot 2016-04-21 15:56:07 UTC 
https://github.com/ManageIQ/manageiq/pull/8155
Comment 3 CFME Bot 2016-04-25 22:00:52 UTC 
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/2386d0ab5379a3b20cb1d7b3225032a45bb97efe

commit 2386d0ab5379a3b20cb1d7b3225032a45bb97efe
Author:     Adam Grare <agrare>
AuthorDate: Thu Apr 21 11:09:46 2016 -0400
Commit:     Adam Grare <agrare>
CommitDate: Thu Apr 21 11:47:21 2016 -0400

    Empty VM Notes doesn't clear container notes field
    
    When you clear the VM Notes field of a VM instead of setting
    hardware[:annotation] to nil we leave it unset so it the value
    in the database isn't cleared out.  To fix this set the
    hardware[:annotation] field to nil explicitly if the
    config.annotation property is blank.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1326866

 .../providers/vmware/infra_manager/refresh_parser.rb       |  2 +-
 .../providers/vmware/infra_manager/refresh_parser_spec.rb  | 14 ++++++++++++++
 2 files changed, 15 insertions(+), 1 deletion(-)
Comment 4 Alex Newman 2016-05-13 19:16:22 UTC 
5.6.0.6-beta2.5.20160511140943_ff75fb2
Comment 5 CFME Bot 2016-05-17 17:18:32 UTC 
https://github.com/ManageIQ/manageiq/pull/8473
Comment 7 errata-xmlrpc 2016-06-29 15:49:06 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://access.redhat.com/errata/RHBA-2016:1348
Note You need to log in before you can comment on or make changes to this bug.