Back to bug 1326866
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Greg Blomquist | 2016-04-14 14:07:12 UTC | Priority | unspecified | medium |
| Assignee | gblomqui | agrare | ||
| Dave Johnson | 2016-04-15 16:46:10 UTC | Whiteboard | vmware | |
| Dave Johnson | 2016-04-15 16:47:24 UTC | QA Contact | dajohnso | anewman |
| Adam Grare | 2016-04-21 15:09:20 UTC | Status | NEW | ON_DEV |
| Adam Grare | 2016-04-26 12:27:02 UTC | Status | ON_DEV | POST |
| Satoe Imaishi | 2016-04-29 11:49:36 UTC | Status | POST | MODIFIED |
| CC | simaishi | |||
| Satoe Imaishi | 2016-05-03 22:44:44 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | 5.6.0.5 | |||
| Alex Newman | 2016-05-13 19:16:22 UTC | Status | ON_QA | VERIFIED |
| Marianne Feifer | 2016-05-26 19:56:38 UTC | CC | mfeifer | |
| Doc Text | Cause: 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. Consequence: Setting an empty VM Note in VMware does not clear the VM | Container | Notes field Fix: To fix this set the hardware[:annotation] field to nil explicitly if the config.annotation property is blank. Result: |
|||
| Dayle Parker | 2016-06-27 05:01:21 UTC | Doc Text | Cause: 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. Consequence: Setting an empty VM Note in VMware does not clear the VM | Container | Notes field Fix: To fix this set the hardware[:annotation] field to nil explicitly if the config.annotation property is blank. Result: | Previously, setting an empty note did not clear 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. |
| Dayle Parker | 2016-06-27 05:31:22 UTC | Doc Text | Previously, setting an empty note did not clear 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. | 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. |
| errata-xmlrpc | 2016-06-29 07:23:03 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-29 15:49:06 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-29 11:49:06 UTC |
Back to bug 1326866