Red Hat Bugzilla – Bug 487412
NEVRA Problems with export & sat sync
Last modified: 2009-03-04 23:59:29 EST
Description of problem:
I'm seeing an ISE when deleting a package. I believe this is a NEVRA issue.
Further it looks like the packages are not being imported consistently.
I can add a package and delete it, so this is not a simple problem with deleting custom content.
On a satellite I created 2 custom channels:
customCentOS & customRHEL
I rhnpushed "helios" to each CentOS & RHEL channel, I pushed the respective version of each to it's channel.
Now I have 2 custom channels each containing a single package which shares the same NEVRA info.
I export both channels in one export command.
I tar up the data.
I copy it to a new install of Sat 5.3.0
I untar the export
run satsync with both channels.
Note: I saw "unscriptable object" once, it hasn't show up again
Looking in the WebUI I see 2 channels were created, one for RHEL and one for CentOS.
Both channels have the same package in them, the CentOS package.
The RHEL package is left as unmanaged.
When I attempt to delete the "RHEL" package it is deleted. This is the "unmanaged" package.
When I attempt to delete the "CentOS" package, the managed one in both channels, I get an ISE.
2009-02-25 15:50:33,469 [TP-Processor7] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/rhn].[action] - Servlet.service() for servlet action thr
java.sql.SQLException: ORA-00001: unique constraint (RHNSAT.RHN_PFDQUEUE_PATH_UQ) violated
Version-Release number of selected component (if applicable):
Installed using QA's install-sat.sh
NFS mounting /var/satellite using QA exports
Seems consistent, reproduced on 2 Satellites. Requires the export*.tar.bz2 I am attaching.
Steps to Reproduce:
1. sat-sync with attached export
2. delete both custom channels
3. delete the package which is not in either channel, deletes fine
4. delete the package which is in both channels, see ISE
I'm seeing some odd behavior where I can't delete the packages. Then I rhnpush some more content, go back and I can delete the trouble package. I haven't been able to identify enough of this behavior to make sense of it.
Created attachment 333229 [details]
This is an export of 2 custom channels each with 1 package each sharing same NEVRA
There was some discussion (outside of Bugzilla apparently), that we are not planning on supporting this scenario for Satellite. I don't understand this and I feel this is a blocker. Let's take RHEL out of the equation here. I can see a situation where a customer has two channels, one beta and one production. They want to sign the beta packages with a beta key and put them into the beta channel. Turns out that particular NVREA is a good one, so they sign the package with their beta package with a production key and then put them into the production channel (which is now supported with NEVRA). Now I export those channels and want to Sat Sync onto another Satellite. Well, now its busted. We would need more information on why this case couldn't be supported. Apparently the exporter is doing the right thing but satellite-sync isn't.