Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1358450 - Data Processing section doesn't show up in the Dashboard
Summary: Data Processing section doesn't show up in the Dashboard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-puppet-elements
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: Upstream M3
: 10.0 (Newton)
Assignee: Elise Gafford
QA Contact: Udi
URL:
Whiteboard:
Depends On: 1351254
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-20 17:42 UTC by Elise Gafford
Modified: 2016-12-14 15:46 UTC (History)
14 users (show)

Fixed In Version: openstack-tripleo-puppet-elements-5.0.0-0.20160809165922.703eeea.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1351254
Environment:
Last Closed: 2016-12-14 15:46:46 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Launchpad 1604913 None None None 2016-07-20 18:23:39 UTC
Red Hat Product Errata RHEA-2016:2948 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 enhancement update 2016-12-14 19:55:27 UTC

Comment 1 Elise Gafford 2016-07-20 17:43:54 UTC
Cloned from bug in 9 (which was decided to be fixed through a manual doc process, given that openstack-sahara-ui is tech preview in 9.) Targeting Newton upstream release for integration.

Comment 5 errata-xmlrpc 2016-12-14 15:46:46 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/RHEA-2016-2948.html


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