Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1141734 - JON agent native support is not supported for Solaris 10 and Solaris 11 x86
JON agent native support is not supported for Solaris 10 and Solaris 11 x86
Status: CLOSED CURRENTRELEASE
Product: JBoss Operations Network
Classification: JBoss
Component: Documentation (Show other bugs)
JON 3.3.0
Unspecified Unspecified
unspecified Severity unspecified
: GA
: JON 3.3.0
Assigned To: Jared MORGAN
Mike Foley
Jared MORGAN
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-15 06:56 EDT by Radim Hatlapatka
Modified: 2015-08-09 21:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
Agent native support is not supported on Solaris 10 and Solaris 11 x86 systems. While EAP 5 is supported on Solaris 10 (x86, x86_64. sparc64) and EAP 6 is supported on both Solaris 10 and Solaris 11 (x86, x86_64. sparc64), the JON agent does not provide native support for these platforms. For more information about supported platforms, see https://access.redhat.com/articles/112523
Story Points: ---
Clone Of:
Environment:
[Release_Notes] Ready for Review
Last Closed: 2014-12-11 09:05:17 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Radim Hatlapatka 2014-09-15 06:56:20 EDT
To track inconsistency between platforms supported by JON and by EAP, mainly for documentation purpose


EAP 5 and EAP 6 are also supported on Solaris 10 and Solaris 11 x86 [1][2] but JON agent doesn't provide native support for the that platform [3].

JON plugins for EAP requires agent native support to be able to manage EAP resources.



[1] https://access.redhat.com/articles/113083
[2] https://access.redhat.com/articles/111663
[3] https://access.redhat.com/articles/112523

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