Bug 1138856
| Summary: | Failed Bundle Deployment Shows As "Live" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Matt Mahoney <mmahoney> | ||||||
| Component: | Provisioning | Assignee: | RHQ Project Maintainer <rhq-maint> | ||||||
| Status: | CLOSED EOL | QA Contact: | Mike Foley <mfoley> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | JON 3.3.0 | ||||||||
| 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: | 2019-06-17 14:47:26 UTC | Type: | Enhancement | ||||||
| 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 934903 [details]
server.log
This is the intended, if somewhat unintuitive, behavior common to all bundle types. I agree that we should better discriminate between liveness and success/failure of the deployment so I'm changing this to an RFE bug and unsetting it as a blocker to BZ 1069547. JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121. This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version. |
Created attachment 934902 [details] Screen-shot Description of problem: Upon an EAP patch failed deploy (the patch did not deploy to the EAP), JON reports that the Patch Bundle which was attempted to be deployed still shows as the "Live" deploy (see screen shot) This particular assurance happened when an attempt to deploy a Patch Bundle to a Group containing an EAP Domain Controller failed to deploy Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy a patch bundle to a group that contains an EAP Domain Controller. 2. 3. Actual results: Live deploy was that of a failed deploy attempt. Expected results: A failed deploy should not result in JON reporting that deploy as being "Live". Additional info: