Bug 1081592
Summary: | Attempt to deploy a package to the resource from the repository gives error | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> | ||||||||
Component: | Content | Assignee: | Jirka Kremser <jkremser> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | JON 3.2 | CC: | ahovsepy, hrupp, loleary, myarboro, rvanbiljon, spinder | ||||||||
Target Milestone: | DR03 | Keywords: | NeedsTestCase, Regression, Triaged | ||||||||
Target Release: | JON 3.2.2 | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2014-07-29 00:17:04 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | 1081597 | ||||||||||
Bug Blocks: | |||||||||||
Attachments: |
|
Description
bkramer
2014-03-27 16:10:22 UTC
Forgot to add, this is version JBoss ON 3.2.0 Created attachment 881143 [details]
Excerpt from server.log with debug enabled
Attaching a log excerpt for a server with debug logging enabled at the point where a WAR was being deployed. Steps to reproduce:
1. Start JBoss EAP 6.1 standalone server.
2. Start JBoss ON 3.2 system.
3. Import JBoss EAP server into inventory.
4. Configure connection settings for newly imported resource.
5. Deploy jboss-as-helloworld.war to JBoss EAP server.
6. Create test repository from Administration > Content / Repositories:
* *Name*: `Test Repo`
7. From Test Repo upload a new version of helloworld WAR:
* *Upload File*: jboss-as-helloworld-1.0.1.war (any WAR will do)
* *Type*: *File [Deployment:JBossAS7]*
8. Subscribe the imported JBoss EAP server to *Test Repo*:
1. Under *Resources Subscribed To This Repository* click *SUBSCRIBE...* button.
2. For search, enter `jboss-as-helloworld.war` and set type drop-down to *Service* and click search.
3. Check jboss-as-helloworld.war resource which was returned.
4. Click *SUBSCRIBE SELECTED*.
9. Navigate to the content page of the jboss-as-helloworld.war resource.
10. Select the new tab.
11. Check one of the new versions of jboss-as-helloworld.war (jboss-as-helloworld-1.0.1.war).
12. Click *DEPLOY SELECTED*.
At this point the browser loads what appears to be a legacy JSF page:
The page requested cannot be displayed due to some error.
return to the previous page, Dashboard, or Browse Resources page.
/portal/rhq/resource/content/confirm-create-plain.xhtml
Jirka, can you check and c-p over (if not yet in the branch) It's fixed in the master, so I need to find the commit and do the c-p didn't managed to get to DR3 => re-targeting to DR4 branch: release/jon3.2.x link: https://github.com/rhq-project/rhq/commit/682a46c73 time: 2014-06-25 17:42:27 +0200 commit: 682a46c730b146598c88141d6cd24eb0dad462d1 author: Lukas Krejci - lkrejci message: [BZ 1081592] - Attempt to deploy a package to the resource from the repository gives error This is a combination of 2 commits that were squashed toghether: * [BZ 1099485] Fix JSF file upload popup for all upload locations (cherry picked from commit 76f9e174ed62be4742f35a91bd3e9aa02934a81e) Signed-off-by: Jirka Kremser <jkremser> * [BZ 1078510] - Make sure to use the "plain" pagination on "plain" jsf pages This avoids the warning arising from the "non-plain" pagination trying to access page elements not present on the plain pages. (cherry picked from commit 3150c41379c2530a4ab50fd216fa891c0d78553d) Signed-off-by: Jirka Kremser <jkremser> Moving to ON_QA as available for test in latest build: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.2.GA/6-28-2014/ bug is not in DR3 moving back as modified and putting target milestone as CR1 Actually because of a decision to reopen DR03 to lower risk and payload of CR01, this and a few other changes that didn't originally make the DR3 cut were pulled into it successfully, contrary to Comment 5. Moving back to ON_QA and back into DR03 payload. Simeon, are you sure? My commit is not in the jon3.2.2.DR3 branch [1]. And QE test it against a build that is based on this branch (558495c:44428f7). I recall my commit went in after the jon3.2.2.DR3 fork. Perhaps it needs to be cherry-picked, or rather postponed to DR4/CR1. [1] https://github.com/rhq-project/rhq/commits/rc/jon3.2.2.DR3 Ok, after looking into it, the commit must be there, because originally it failed after clicking on "Deploy Selected". Now, the original error is gone, but there is another one in the server.log. I'll investigate this regression. 13:33:22,722 ERROR [org.jboss.as.ejb3.invocation] (http-/0.0.0.0:7080-2) JBAS014134: EJB Invocation failed on component ContentManagerBean for method public abstract org.rhq.core.domain.content.ContentServiceRequest org.rhq.enterprise.server.content.ContentManagerLocal.createDeployRequest(int,java.lang.String,java.util.Set,java.lang.String): javax.ejb.EJBException: javax.persistence.NoResultException: No entity found for query at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:165) [jboss-as-ejb3-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at ... ... org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.rhq.enterprise.server.content.ContentManagerLocal$$$view143.createDeployRequest(Unknown Source) [rhq-server.jar:4.12.0-SNAPSHOT] at org.rhq.enterprise.server.content.ContentManagerBean.deployPackages(ContentManagerBean.java:407) [rhq-server.jar:4.12.0-SNAPSHOT] at org.rhq.enterprise.server.content.ContentManagerBean.deployPackagesWithNote(ContentManagerBean.java:380) [rhq-server.jar:4.12.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55] ... -> Moving this back to ASSIGNED Created attachment 914526 [details]
failed_deploy
The original bug is fixed in DR4, however it is still far from perfect. Now, it should be the same as in 3.2.0GA. Deployments work quite well when using "Upload New Package" directly from the content tab, instead of going through the repositories. When using repositories the types of the package must match (mark the right plugin). There is no filter on types when defining a package that is targeted for platform for instance. This is because the resources subscribed to a repository can be heterogeneous and packages can be created before subscribing the resources. Also when deploying a content to a platform and selecting the package type as RPM it assumes the internal yum server to be running and configured, that's why I thought it's not working even on older JONs. However the JSF exception (ViewExpiredException: viewId:/rhq/resource/content/fileUpload.xhtml) is gone. I am not against opening some RFEs in this area, because the user experience was quite bad. I guess it is described in the docs, but still, very counterintuitive. initial BZ verified bz #1115397 and #=1118394 filed screen-shot attached Created attachment 917142 [details]
deploy_in_progress
This has been verified and released in Red Hat JBoss Operations Network 3.2 Update 02 (3.2.2) available from the Red Hat Customer Portal[1]. [1]: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=31783 |