Bug 796192 - Error on installing package from the repository
Error on installing package from the repository
Status: NEW
Product: RHQ Project
Classification: Other
Component: Content (Show other bugs)
4.3
Unspecified Unspecified
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-22 08:07 EST by Sunil Kondkar
Modified: 2012-02-22 10:20 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
WAR file used (846 bytes, application/octet-stream)
2012-02-22 09:48 EST, Sunil Kondkar
no flags Details

  None (edit)
Description Sunil Kondkar 2012-02-22 08:07:55 EST
Description of problem:

After creating a content source and repository, trying to install package from repository displays below error

Failed to deploy packages: [I@2fc068bf to Resources subscribed to repository: 10062 Error: javax.persistence.NoResultException: No entity found for query

I used a WAR file as a package. Attaching the WAR file as a reference.

There is no error in sever log or agent log.

Version-Release number of selected component (if applicable):

Build Version: JON 3.0.1.GA RC5 (Build Number: dd8a001:fbca611)
Browser: Firefox 3.6.3
Database : PostgreSQL 8.3.8

How reproducible:

Always

Steps to Reproduce:

1.Create directory structure at platform as below:

mkdir /testrepo
cd /testrepo
mkdir test
cd test

Place a WAR file in folder "test"

2. Login to UI
3. Navigate to Administration->Content->Content Sources
4. Click on 'Create New' button.
5. Click on 'Local Disk Storage Content Source'.
6. Enter below details:

Name: testrepo
Download Mode: Never
Root Directory: /testrepo
Package Type Name: JBossAS5 - Web Application (WAR) - WAR File
Architecture Name: noarch
Resource Type: JBossAS5 - Web Application (WAR)
Repo Source Enabled : yes


7. After creating the content source, it dsplays  repository with name 'test' in Candidate Repositories section.
8. Import 'test' repository. It displays  repository with name 'test' in Repositories section.
9. Click on the repository with name 'test'.
10.Click on the 'Syncronize' button in the UI for repository.
11.It displays the WAR file in 'Packages' section of the repository.
12. Subscribe the repository to an EAP5 resource. ( I did it for EAP 5.0.0.GA resource)
13. Navigate to the repository 'test'.
14. Select the WAR file in 'Packages' section and click on 'Install Packages'
15. Click on OK button on the confirmation message.
16. It displays below error in UI.

Failed to deploy packages: [I@2fc068bf to Resources subscribed to repository: 10062 Error: javax.persistence.NoResultException: No entity found for query
  
Actual results:

Error on installing package from the repository.

Expected results:

No error

Additional info:
Comment 1 Sunil Kondkar 2012-02-22 09:48:02 EST
Created attachment 564994 [details]
WAR file used
Comment 2 Sunil Kondkar 2012-02-22 10:14:40 EST
There are no errors in server log and agent log.
The server log displays below:

2012-02-22 20:42:55,442 INFO  [org.rhq.enterprise.server.content.ContentManagerBean] Deploying 1 packages on resource ID [10003]
2012-02-22 20:42:55,613 WARN  [org.ajax4jsf.renderkit.AjaxRendererUtils] AJAX Status component not found for AjaxComponent with id repoContentProvidersDataTableScroller
2012-02-22 20:42:55,626 WARN  [org.ajax4jsf.renderkit.AjaxRendererUtils] AJAX Status component not found for AjaxComponent with id repoResourcesDataTableScroller
2012-02-22 20:42:55,632 WARN  [org.jboss.seam.ui.renderkit.DefaultActionRendererBase] Must set an id for the default action source
2012-02-22 20:42:55,643 WARN  [org.ajax4jsf.renderkit.AjaxRendererUtils] AJAX Status component not found for AjaxComponent with id repoPackageVersionsDataTableScroller

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