Bug 1314134 - [Docs][Release Notes] 'category_create' method does not work as expected. Add the workaround to Release Notes
Summary: [Docs][Release Notes] 'category_create' method does not work as expected. Add...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 5.6.0
Assignee: Red Hat CloudForms Documentation
QA Contact: Dayle Parker
URL:
Whiteboard: doc
Depends On: 1035394
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 01:23 UTC by Shikha
Modified: 2017-08-30 01:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-09 07:11:57 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shikha 2016-03-03 01:23:15 UTC 
Document URL: https://access.redhat.com/documentation/en/red-hat-cloudforms/4.0/release-notes/release-notes

Section Number and Name: https://access.redhat.com/documentation/en/red-hat-cloudforms/4.0/release-notes/chapter-4-known-issues

Describe the issue: Document the information with the workaround for create_category discrepancy in Bug 1035394 under Known Issues in Release Notes and provide a link in Methods Available for Automation Guide, 1.41. Creating Categories and Tags

Regards,
Shikha
Comment 3 Dayle Parker 2016-03-15 04:32:25 UTC 
Assigning myself as QE as this relates to what I'm QE-ing in BZ1035394.
Comment 4 Dayle Parker 2016-03-15 06:40:17 UTC 
Verifying that the note was added to Known Issues to go with Bug 1035394 -- all looks good. Thank you, Shikha.
Comment 7 Lucy Bopf 2016-05-09 07:11:57 UTC 
This bug has been added to the Release Notes as a known issue at the following location:

https://access.redhat.com/documentation/en/red-hat-cloudforms/version-4.0/release-notes/#known_issues

Closing.
Note You need to log in before you can comment on or make changes to this bug.