Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1129663 - RHEL6 RPMs: Upgrade jboss-hal to 2.2.10.Final-redhat-1
RHEL6 RPMs: Upgrade jboss-hal to 2.2.10.Final-redhat-1
Status: CLOSED ERRATA
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: RPMs (Show other bugs)
6.3.1
Unspecified Unspecified
unspecified Severity unspecified
: ER1
: EAP 6.3.1
Assigned To: Vladimir Dosoudil
Katerina Odabasi
Russell Dickenson
: Rebase
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-13 08:43 EDT by Fernando Nasser
Modified: 2015-02-20 06:18 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-09-23 15:58:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1285 normal SHIPPED_LIVE Low: Red Hat JBoss Enterprise Application Platform 6.3.1 update 2014-09-23 19:54:38 EDT

  None (edit)
Description Fernando Nasser 2014-08-13 08:43:55 EDT
Required upgrade.
Comment 1 Vladimir Dosoudil 2014-08-20 08:21:25 EDT
Source URL: git://git.app.eng.bos.redhat.com/hal/release-stream.git#711ce19cbdabe6210b4a1d282ef298cc061ef291
Mead-Build: org.jboss.hal-release-stream-2.2.10.Final_redhat_1-1
Brew-Build: jboss-hal-2.2.10-1.Final_redhat_1.1.ep6.el6
Comment 4 errata-xmlrpc 2014-09-23 15:58:10 EDT
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.

http://rhn.redhat.com/errata/RHSA-2014-1285.html

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