| Summary: | Installer allows to install RTGov server ithout FSW | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Installer | Assignee: | Gary Brown <gbrown> |
| Status: | CLOSED WORKSFORME | QA Contact: | Len DiMaggio <ldimaggi> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | atangrin, fcanas, gbrown, jpechane, soa-p-jira |
| Target Milestone: | ER4 | Flags: | gbrown:
needinfo?
(jpechane) |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-31 16:24:04 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: | |
|
Description
Jiri Pechanec
2013-09-27 04:32:12 UTC
Added to core-packs spec so user can no longer install RTGov-s without FSW selected. See commit for details: http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=2aa7c34cad3823a8830a00982c5ff355557513ed Jiri: From our spec document: https://docspace.corp.redhat.com/docs/DOC-147383 Selecting Serviceworks will also select RT-Gov Client, unless RT-Gov Server is also selected. Deselecting RT-Gov Server will also select RT-Gov Client if Serviceworks is currently selected. Both of these lines imply that it is possible to have RTGov server selected without Serviceworks being selected. If this is incorrect, the spec will need updating and we'd need a discussion relating to this. I've found this issue because I had RTGov server installed without FSW and there were missing dependencies - like Google ProtoBuf. So let's have PM/dev decide what is the bug - if the standalone or missing dependencies Could not reproduce this with ER4. Could you try again, and if problem still present, provide the steps to reproduce. I started up the server with no problem, and then reported some activities via the REST API. |