Bug 1025267
Summary: | Met error "jbossews//bin/build: line 33: force_clean_build_enabled_for_latest_deployment command not found" when push changes to existing apps after migration. | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Liang Xia <lxia> |
Component: | Containers | Assignee: | Dan Mace <dmace> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | dmace, jhou |
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: | 2014-01-24 03:28:17 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: |
Description
Liang Xia
2013-10-31 10:54:04 UTC
Couldn't reproduce with a fresh upgrade from devenv_3974 to devenv-stage_532. Examining the yum log of ec2-54-205-26-133.compute-1.amazonaws.com leads me to believe it wasn't upgraded to the new RPMs properly. If this issue can be reproduced, please: 1. Tag the test VM(s) with -preserve 2. Specify the VM(s) in the bz Thanks! Tried again with following scenarios: non-scalable jbossews-2.0 without force_clean_build marker. non-scalable jbossews-2.0 with force_clean_build marker. scalable jbossews-2.0 without force_clean_build marker. scalable jbossews-2.0 with force_clean_build marker. Steps: 1. Create apps on devenv-stage_528. 2. Upgrade the devent-stage instance to latest as devenv_3978. 3. After upgrade, clear broker cache, restart broker and mcollective services 4. Do datastore migration # rhc-admin-migrate-datastore --compatible --version 2.0.35 5. Do gear migration # oo-admin-upgrade upgrade-node --version 2.0.35 --ignore-cartridge-version 6.change something in the app's local repo and git push. None of the scenarios met the error. Move to verified. Also tested after migration on devenv-stage_546, the issue is not reproduced. |