Bug 1054752
| Summary: | Given version of deployment is overwritten by computed sha when deploying via CLI | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Filip Brychta <fbrychta> | ||||||||
| Component: | CLI, Content, Plugins | Assignee: | Nobody <nobody> | ||||||||
| Status: | NEW --- | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 4.10 | CC: | hrupp | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 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: |
|
||||||||||
Created attachment 851553 [details]
screen shot
Created attachment 851554 [details]
deployment
Update: Ignore original 'Additional info' section. Update works. |
Created attachment 851552 [details] cli script Description of problem: I deployed a new EAR to EAP5.2.0 via CLI and given version of deployment was overwritten by computed sha. Version-Release number of selected component (if applicable): Version : 4.10.0-SNAPSHOT Build Number : 05fa7f2 How reproducible: Always Steps to Reproduce: 1. EAP is imported in the inventory 2. run attached cli script with a correct path to attached deployment: ./rhq-cli.sh -f /tmp/test.js --args-style=named deployment=/tmp/MiscBeans-3.2.2.ear -s <your server IP> -u rhqadmin -p rhqadmin 3. go to content tab of newly created MiscBeans.ear resource in the UI Actual results: Displayed version is a computed sha instead of given version in the CLI script (see attached screen shot) Expected results: Displayed version is: 3.2.2 Additional info: There is the same problem for deployment updates.