Bug 1206641
| Summary: | Fix for BZ-1088046 is lost when storage node is installed from 3.3 Update-01 patched server | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Larry O'Leary <loleary> |
| Component: | Storage Node | Assignee: | Simeon Pinder <spinder> |
| Status: | CLOSED ERRATA | QA Contact: | Mike Foley <mfoley> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | JON 3.3.1 | CC: | loleary, skondkar |
| Target Milestone: | ER01 | ||
| Target Release: | JON 3.3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-30 16:11:13 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: | 1088046 | ||
| Bug Blocks: | 1185375 | ||
This is fixed with the following commits to jon.git: 8c189a53200720 d301b9fa673e06 The solution was to update the storage node artifact as part of the patch application. Moving to MODIFIED for testing with next brew build. Moving to ON_QA for testing with latest cumulative patch build: https://brewweb.devel.redhat.com//buildinfo?buildID=429507 Note: Build maps to JON 3.3.2 ER01 build. Discussed with Simeon and verified as below: 1) ON host 1 Installed JON3.3GA server+storage node and applied JON3.3.2CR01 patch 2) On host 2, unpacked JON3.3GA and applied JON3.3.2CR01 patch and then started the storage node with: ./rhqctl install --storage --agent-preference="rhq.agent.server.bind-address=<IP of host 1>" verified that ./rhqctl start --storage does not show the ./cassandra: numactl: not found error Putting a need info to confirm is the verification steps are correct Confirmation steps are acceptable. Please note that this fix/verification is only in preparation for future support of patching the installer/upgrade. The 3.3.2 release does not official provide support for patching pre-installed components. For user's with JBoss ON subscriptions, the expectation is that they must first install and configure the standalone storage node and accept that the script is broken and will report these errors. This does not prevent the install from completing. Once the install is completed, the 3.3 update-02 (3.3.2) can be applied to resolve the script issue. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0920.html |
Description of problem: If you apply update-01 to 3.3 standalone server and then later install a storage node on the same server using rhqctl install --storage, the installer spits out the following error: ./cassandra: numactl: not found This is a regression as this bug was fixed in 3.3.1. Version-Release number of selected component (if applicable): 3.3.1 How reproducible: Always Steps to Reproduce: 1. Install, configure, and start JBoss ON 3.3 standalone server. Please note that his requires a storage node to be running on a different host. Either install a standalone storage node somewhere else or install a JBoss ON sever and storage node on host-1 and then add a second JBoss ON server on host-2 using: rhqctl install --server 2. Apply update-01 (3.3.1) to the standalone JBoss ON server. 3. Do to BZ-1206387, you will need to manually delete <RHQ_SERVER_HOME>/rhq-storage before proceeding to the next step. The apply-updates command creates this directory and makes the installer think rhq-storage is already installed. 4. Install the storage node: rhqctl install --storage 5. Start the storage node: rhqctl start --storage Actual results: Start command prints the following: ./cassandra: numactl: not found Expected results: No "not found" error is reported. Additional info: This bug was fixed in BZ-1088046 however it appears that only the rhq-storage/bin/cassandra script was included in the update. In addition to including the cassandra script file for a pre-existing rhq-storage directory, the update needs to also include: ./modules/org/rhq/rhq-cassandra-installer/main/rhq-cassandra-ccm-core-4.12.0.JON330GA.jar ./modules/org/rhq/rhq-installer-util/main/rhq-cassandra-ccm-core-4.12.0.JON330GA.jar