Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Created a repository - test; 2. Uploaded New Package and confirmed that the package is listed in the Packages list 3. Subscribed resource to this repository - confirmed that the resource is listed in the "Resources Subscribed To This Repository" list 4. Selected resource that is subscribed to the newly created repository 5. Navigate to Content -> New and select package name from the list 6. Press "Deploy Selected" button to deploy selected package Actual results: The following exception is shown: ********************************* Error 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 ********************************* and package is not deployed. No exception is thrown in the server.log file. However, when uploading a package in the step 2 the following is logged: ********************************* 15:45:20,163 INFO [org.rhq.enterprise.server.content.RepoManagerBean] (http-/0.0.0.0:7080-7) User [Subject[id=2,name=rhqadmin]] created [Repo: id=[10011], name=[newRepo]]. 15:45:20,182 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (http-/0.0.0.0:7080-7) Scheduled cron job [6dfaa932:syncRepo] to fire next at [Fri Mar 28 03:00:00 GMT 2014] with the cron string [0 0 3 * * ?]. 15:45:20,300 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id reposDataTableScroller 15:45:26,043 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id repoContentProvidersDataTableScroller 15:45:26,062 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id repoResourcesDataTableScroller 15:45:26,097 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id repoPackageVersionsDataTableScroller 15:45:39,059 SEVERE [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-/0.0.0.0:7080-7) JSF1054: (Phase ID: RESTORE_VIEW 1, View ID: ) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@1100588f] 15:45:39,087 INFO [org.rhq.enterprise.gui.common.upload.FileUploadUIBean] (http-/0.0.0.0:7080-8) A file named [rdp-jmx-plugin-1.12-SNAPSHOT.jar] with a size of [4097] has been uploaded to [/tmp/-4fb9ae6a-145036d9f14--7ffb573198192587551686.upload] 15:45:39,093 INFO [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-/0.0.0.0:7080-8) WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=null[severity=(INFO 0), summary=(Content has been received - you may now hit CONTINUE to commit the upload), detail=()] 15:45:39,070 ERROR [org.ajax4jsf.webapp.BaseXMLFilter] (http-/0.0.0.0:7080-7) Exception in the filter chain: javax.servlet.ServletException: viewId:/rhq/resource/content/fileUpload.xhtml - View /rhq/resource/content/fileUpload.xhtml could not be restored. at javax.faces.webapp.FacesServlet.service(FacesServlet.java:270) [jsf-api-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at sun.reflect.GeneratedMethodAccessor360.invoke(Unknown Source) [:1.6.0_15] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_15] ... Caused by: javax.faces.application.ViewExpiredException: viewId:/rhq/resource/content/fileUpload.xhtml - View /rhq/resource/content/fileUpload.xhtml could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:189) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:102) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) [jsf-api-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] ... 90 more 15:45:39,095 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/portal].[Faces Servlet]] (http-/0.0.0.0:7080-7) JBWEB000236: Servlet.service() for servlet Faces Servlet threw exception: javax.faces.application.ViewExpiredException: viewId:/rhq/resource/content/fileUpload.xhtml - View /rhq/resource/content/fileUpload.xhtml could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:189) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:102) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) [jsf-api-1.2_15-b01-redhat-3.jar:1.2_15-b01-redhat-3] ... 15:45:39,734 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id repoContentProvidersDataTableScroller 15:45:39,748 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id repoResourcesDataTableScroller 15:45:39,769 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-7) AJAX Status component not found for AjaxComponent with id repoPackageVersionsDataTableScroller 15:46:09,342 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoContentProvidersDataTableScroller 15:46:09,363 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoResourcesDataTableScroller 15:46:09,385 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoPackageVersionsDataTableScroller 15:46:25,501 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoSubscriptionsDataTableScroller 15:46:25,505 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoUnsubscriptionsDataTableScroller 15:46:29,838 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoSubscriptionsDataTableScroller 15:46:29,848 WARN [org.ajax4jsf.renderkit.AjaxRendererUtils] (http-/0.0.0.0:7080-8) AJAX Status component not found for AjaxComponent with id repoUnsubscriptionsDataTableScroller 15:46:57,086 WARN [org.rhq.core.domain.server.PersistenceUtility] (http-/0.0.0.0:7080-11) Queries should really supply default sort columns. Caller did not: org.rhq.enterprise.server.content.ContentUIManagerBean.getPackageVersionCompositesByFilter(ContentUIManagerBean.java:252) 15:46:57,090 WARN [org.rhq.core.domain.server.PersistenceUtility] (http-/0.0.0.0:7080-11) Queries should really supply default sort columns. Caller did not: org.rhq.enterprise.server.content.ContentUIManagerBean.getPackageVersionCompositesByFilter(ContentUIManagerBean.java:267) ********************************* Expected results: No error page is shown and the package is deployed. Additional info:
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