Bug 1290317
Summary: | When start a build manually, --env option does't work with --from-repo --from-dir, --from-file binary build option | ||
---|---|---|---|
Product: | OKD | Reporter: | Wang Haoran <haowang> |
Component: | Build | Assignee: | Michal Fojtik <mfojtik> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.x | CC: | aos-bugs, mfojtik, misalunk, wsun, wzheng, xiazhao |
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: | 2016-05-12 17:14:01 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
Wang Haoran
2015-12-10 08:43:39 UTC
1. This has nothing to do with options --from-repo --from-dir, --from-file, issue reproduced if trigger new build without these options: $oc start-build <bcname> --env=RACK_ENV=development 2. The step4 of command output "oc logs -f" kept saying "Step 4 : ENV RACK_ENV production" regardless of how we set value to RACK_ENV in --env when doing "oc start-build" (In reply to Xia Zhao from comment #1) > 1. This has nothing to do with options --from-repo --from-dir, --from-file, > issue reproduced if trigger new build without these options: > $oc start-build <bcname> --env=RACK_ENV=development > I think it's different code logic , both exists the problem. > 2. The step4 of command output "oc logs -f" kept saying "Step 4 : ENV > RACK_ENV production" regardless of how we set value to RACK_ENV in --env > when doing "oc start-build" If start the build like what you said , it will add the env in the step 1. and then overlaped by step 4. if there is a new env not exits in previous dockerfile , this option will work.So problem is the env passed through --env option haven't replace the exits one in dockerfile . I think this is a bug but not related to the binary build. The --env option was added recently, I will have a look. After some investigation the bug that the --env option is passed into a BuildRequest from CLI, but the binary builds are using BinaryBuildRequest, where this field is missing. I'm fixing this now, so you're right, this is actually related to the binary builds ;-) Upstream issue about this: https://github.com/kubernetes/kubernetes/issues/18649 Wang: This bug will be fixed by showing a warning when you use --env/--build-loglevel with combination with binary build source. The warning PR is here: https://github.com/openshift/origin/pull/6298 I think this bug can be verified and closed. will verify this once the PR is merged. the --env options is removed from the oc start-build command , so this senario will disappear. origin version: openshift v1.1-428-ged29520 Moving NeedInfo tag. *** Bug 1257254 has been marked as a duplicate of this bug. *** |