Red Hat Bugzilla – Bug 489789
CSP CP to Product relationships are not accurate
Last modified: 2011-01-31 12:48:04 EST
Description of problem:
For example in the CSP feed the 4.3.0.GA_CP01 patch says that it is applicable to EAP instances with version 4.3.0.GA_CP01, when in fact it should say 4.3.0.GA. There are many instances of this in the 4.3 line of CPs and all of them need to be reviewed.
Example bad piece of feed
<dc:subject>JBoss EAP 4.3.0.GA_CP01</dc:subject>
<jbn:product jbn:jonResourceType="JBoss 4.0"
jbn:productVersion="4.3.0.GA_CP01" rdf:about="https://support.redhat.com/jbossnetwork/rss/product#SOFT-10260">Application Platform; 4.3.0.GA_CP01</jbn:product>
Version-Release number of selected component (if applicable):
This is a data error that will persist in the RSS feed to JON until corrected.
Steps to Reproduce:
1. Review JON RSS response https://support.redhat.com/jbossnetwork/restricted/feed/software.html?product=all&downloadType=all&flavor=rss&version=&jonVersion=2.0
2. JON resource version and product version for 4.3.0.GA_CP01 will be 4.3.0.GA_CP01. They need to be different, CP-01 does not replace itself.
Approved. Moving to XPlanner backlog.
Note that Issue-Tracker #271224 can be tackled as part of the fix for this release.
I looked at the I-T ticket. I think this will have to be addressed separately. SEP provides the ability to delete repositories, but it does not provide the ability to delete software entries. Each version in the version pick list directly corresponds to a software entry in SEP (or more specifically a row in the software table). So removing a version from the version pick list equates to removing a software entry. Presently, that would have to be done with a SQL script.
There are a couple other things you consider adding separate tickets for in bugzilla. 1) Add the capability to delete software rows in SEP. 2) Update the business logic for the versions pick list so that it does not include versions for which there is no content.
Pending additional data from ccrouch: Email below
"We believe that we clearly understand the issue, in that the CP for 4.3.0.GA can not be deployed via JON because there is an improper mapping of CP_01 to 4.3.0 GA--4.3.0 GA is not currently defined in the RSS feed.
We need to know which of the jbn: product fields in the RSS need to be changed? Which field defines the base version and which field defines the replacement? If it would be easier, you could update the JIRA, and I will pick up the correspondence from there."
The improper mapping, which currently exists, is from CP01 to jbn:jonResourceVersion="4.3.0.GA_CP01"
The correct mapping is from CP01 to jbn:jonResourceVersion="4.3.0.GA"
> We need to know which of the jbn: product fields in the RSS need to be
> changed? Which field defines the base version and which field defines
> the replacement?
Look at https://support.redhat.com/support-portal/restricted/software/repositoryDetails.html?id=788 (4.3 CP04) for an example:
The Products field holds:
Where for example SOFT-10284 maps to https://support.redhat.com/support-portal/restricted/software/softwareDetails.html?id=284 (4.3.0.GA_CP02)
Those are the things which generate the <jbn:product> elements.
So basically what you need to do is determine the SOFT-NNNNN mappings to product versions, then update the appropriate repository details for each patch so they have the correct values of SOFT-NNNNN in the "Products" field.
I spoke with Charles Crouch to get a better understanding of the issue. CPs apply to previous CPs up to and including the base version. So a bug fix for 4.3.0.GA_CP04 applied to 4.3.0.GA_CP03, 4.3.0.GA_CP02, 4.3.0.GA_CP01, and 4.3.0.GA.
I looked at one 4.3.0.GA_CP02 EAP patch (there may be others) with Charles that is mapped to Application Server 4.2.0. This is wrong for two reason as explained by Charles. First, EAP patches are not applied to App Server. Secondly, a patch from the 4.3 line cannot be applied to the 4.2.x line. It could break the installation. We probably want to open a separate bug to perform an audit of what is mapped to Application Server downloads. We'll need to do the same for Developer Subscription. I see that some of the EAP patches are mapped to it, and I do not know if that is correct.
Lastly, if a patch does not provide automated instructions, JBoss ON altogether ignores the patch since it applies the patches using the automated instructions.
Bugs are no longer tracked under this classification. CSP is now monitored in
Other | Customer Portal | Integrated app: JBoss CSP.
Please refile any current defect records or RFEs under the current