Bug 828838
| Summary: | Exception when trying to deploy bundle with new parameter | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> | ||||
| Component: | Provisioning | Assignee: | John Mazzitelli <mazz> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | JON 3.0.1 | CC: | klaus.erber, loleary, mazz, vnguyen | ||||
| Target Milestone: | --- | ||||||
| Target Release: | JON 3.1.1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 828843 | ||||||
| : | 828843 (view as bug list) | Environment: | |||||
| Last Closed: | 2013-09-11 10:58:34 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: | 820333, 828843 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
This looks to be the same as bug 820333 (and bug 818751). For a workaround - set required to "false" and I think it will work. You might also want to consider setting a default value for the new property in your deploy.xml recipe. That might also help work around this (but not sure about that - I'm more confident required="false" will workaround the issue). See bug 828843 for more info. before applying any fix for this bug, you have to apply fix to bug 818751 (git commit 184dabf) git commit to release/jon3.1.x branch: cb5116aa5c55f970a46ea81a59c8bdbbce2ccc04 JON 3.1.1 ER1 build is available. Moving to ON_QA. https://brewweb.devel.redhat.com/buildinfo?buildID=226942 Verified with 3.1.1.ER1 |
Created attachment 589518 [details] screen shot that shows the exception Description of problem: Initial deployment of the bundle that contains parameters works fine. However, if I try to deploy new version of the bundle that has an additional parameter, deployment will fail with the following message in the UI: Failed to create deployment: java.lang.RuntimeException:[1338882586243] javax.ejb.EJBException:java.lang.IllegalArgumentException: Invalid Configuration: [Required property 'bego.param02' has a null value in Configuration[id=0].] -> java.lang.IllegalArgumentException:Invalid Configuration: [Required property 'bego.param02' has a null value in Configuration[id=0].] Version-Release number of selected component (if applicable): JON 3.0.1 How reproducible: Always Steps to Reproduce: 1. Upload and deploy the bundle jee_test-1.0.0-SNAPSHOT-bundle.zip (attached with this bugzilla) to a destination. This bundle contains one parameter with a default value - "param 01". 2. Upload the bundle jee_test-1.0.1-SNAPSHOT-bundle.zip (attached here) and deploy it to the same destination. This bundle contains an additional parameter bego.param02 with a default value - "param new". 3. Press Next (to accept default values); 4. Press Next button (Provide Deployment Information screen); Actual results: In the "Deploy Bundle to Destination Platforms" screen, the error message is logged: Failed to create deployment: java.lang.RuntimeException:[1338882586243] javax.ejb.EJBException:java.lang.IllegalArgumentException: Invalid Configuration: [Required property 'bego.param02' has a null value in Configuration[id=0].] -> java.lang.IllegalArgumentException:Invalid Configuration: [Required property 'bego.param02' has a null value in Configuration[id=0].] (see attached screen shot). Expected results: Deployment should work fine and default value that is defined for bego.param02 should be accepted. Additional info: Initial deployment of the bundle that has parameters will work fine. I tried to deploy jee_test-1.0.1-SNAPSHOT-bundle.zip bundle (without 1.0.0 version) and deployment was successful.