Bug 1232836
| Summary: | NoResultException in server.log when deploying from resource content for war type != File (Deployment:AS7) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||
| Component: | Content | Assignee: | Josejulio Martínez <jmartine> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Sunil Kondkar <skondkar> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | JON 3.3.0 | CC: | fbrychta, jmartine, mfoley, skondkar, spinder | ||||
| Target Milestone: | DR01 | Keywords: | Triaged | ||||
| Target Release: | JON 3.3.6 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-07-27 15:30:02 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: | |||||||
| Attachments: |
|
||||||
I did reproduce this on JON 3.3.0 + jon-plugin-pack-eap-3.3.0.GA-update-01. However on JON 3.3.5 + jon-plugin-pack-eap-3.3.0.GA-update-01 the issue is gone, instead you get a message that doesn't allow you to complete the operation: Could not send deploy request to agent Cause: javax.ejb.EJBException:java.lang.RuntimeException: Package of PackageType[name=cumulativePatch] cannot be deployed to resource of ResourceType[id=10183, name=Deployment, plugin=JBossAS7, category=Service] allowed packageTypes are [File [Deployment:JBossAS7]] -> java.lang.RuntimeException:Package of PackageType[name=cumulativePatch] cannot be deployed to resource of ResourceType[id=10183, name=Deployment, plugin=JBossAS7, category=Service] allowed packageTypes are [File [Deployment:JBossAS7]] Now the message is less verbose:
Package of PackageType[name=alpha-content0] cannot be deployed to resource of ResourceType[id=10253, name=Deployment, plugin=JBossAS7, category=Service] allowed packageTypes are [File [Deployment:JBossAS7]]
commit 861053d25434f1e0e879181aaac4fb541ae4dea8
Author: Josejulio Martínez <jmartine>
Date: Tue Apr 12 18:59:55 2016 -0500
Bug 1232836 - Shows a less verbose message when deploying package that doesn't match resource's expected type.
Moving to ON_QA as available to test with JON 3.3.6 DR01 brew build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=499890 Verified on version : 3.3.0.GA Update 06 Build Number : 675641d:2fcd5b7 When tried to deploy package that does not match expected type, below message is shown is UI: Package of PackageType[name=cumulativePatch] cannot be deployed to resource of ResourceType[id=10201, name=Deployment, plugin=JBossAS7, category=Service] allowed packageTypes are [File [Deployment:JBossAS7]] Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-1519.html |
Created attachment 1039998 [details] server.log_fragment Description of problem: NoResultException in server.log when deploying from resource content for war type != File (Deployment:AS7) Version-Release number of selected component (if applicable): JON 3.3.0 + jon-plugin-pack-eap-3.3.0.GA-update-01 How reproducible: always Steps to Reproduce: 1. install a versioned war iBook-1.0.0.war 2. create a repo content & add iBook-1.0.2.war with type != File (Deployment:AS7) 3. subscribe to iBook-1.0.0.war from repo 4. navigate to resource, content -> new, deploy the uploaded war file Actual results: iBook.war-1.0.0.war is not updated, exception in server.log (see fragment from server.log attached) GUI does not show history for deployment try Expected results: no exception in server.log GUI shows failure history Additional info: