Bug 708327
| Summary: | as7: Deploy already present content to a new server-group | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Heiko W. Rupp <hrupp> |
| Component: | Plugins | Assignee: | Heiko W. Rupp <hrupp> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1 | CC: | hrupp, skondkar |
| 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: | 2012-02-07 19:20:00 UTC | Type: | --- |
| 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: | |||
| Bug Blocks: | 705059, 707223, 715334 | ||
|
Description
Heiko W. Rupp
2011-05-27 10:05:51 UTC
37f293f in branch as7plugin How to test: Go to the domain controller, create a new child resource "deployment", upload e.g. a war file. When this shows up as child of the domain controller, switch to that resource and go to its operations tab. Choose "deploy to server group", fill in the name of the server group (e.g. main-server-group) and if it should be enabled in that server group. Then submit. The operation should show no error and the deployment should (after some time) show up as child of the server group. failed during verification. discussed with heiko I see java.io.FileNotFoundException: http://localhost:9990/domain-api/add-content meaning the internal API in the AS has changed The api endpoint /domain-api got renamed to /management The change in 50fb595 follows this renaming. Unit test for upload and deploy (which is disabled by default, as it needs a running AS 7) shows that this change works with an AS7 instance as of June 29th (beta3, close to cr1). still having trouble verifying this ... i logged BZ 717699 while attempting to verify this BZ https://bugzilla.redhat.com/show_bug.cgi?id=717699 Can you retry with 5ed2f29d30db493e579cd66e5a0c95c172357935 (internal jenkins build #167 ) Tried to create a new child resource to the domain controller by uploading a
war file. The child history tab of DomainController displays failed status with
error "No handler for deploy at address [("deployment" => "counter.war")],
rolled-back=true".
Filed a separate bug#724929:
https://bugzilla.redhat.com/show_bug.cgi?id=724929
Verified on build#218 (Version: 4.1.0-SNAPSHOT Build Number: 6eedd25) Created a new child resource by uploading a war file to the Domain Controller. Navigated to the operations tab of the war file and scheduled a new operation 'Deploy to server group'. deployed it to the main-server-group. The operation was successful. After doing discovery -f at the agent command prompt, the deployment is displayed as child resource of the main-server-group. Marking as verified. Sunil ... after verifying this, please make sure to add a testcase for this: Standalone: https://tcms.engineering.redhat.com/plan/4065/ Domain Controller: https://tcms.engineering.redhat.com/plan/4071/ Added below test cases: Domain Controller: https://tcms.engineering.redhat.com/case/98615/?from_plan=4071 Standalone: Added a test case for creating a child resource to AS7 standalone by deploying a ear/war file. https://tcms.engineering.redhat.com/case/102978/?from_plan=4065 changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE |