Description of problem: The BuildDefaultsConfig does not propagate the variables to the build. Simply it does not work as described in docs [1]. Tested on 3.4 and 3.5. Master config look like: kubernetesMasterConfig: admissionConfig: pluginConfig: BuildDefaults: configuration: apiVersion: v1 env: - name: BUILD_LOGLEVEL value: 9 - name: NO_PROXY value: .cluster.local,172.30.0.0,0.0.0.0 kind: BuildDefaultsConfig [1] https://docs.openshift.com/container-platform/3.4/install_config/build_defaults_overrides.html#manually-setting-global-build-defaults Version-Release number of selected component (if applicable): OpenShift Container Platform 3.4 and 3.5 How reproducible: Configure the build defaults as described in docs. Actual results: No env propagated to Build Config. Expected results: The Build defaults will be visible in build config and will be used during the build. Additional info: Please, also report that to documentation as described solution does not work.
you've nested the config under kubernetesMasterConfig. That is not where it goes, the admissionConfig for openshift is a toplevel section, which is why the doc does not show "kubernetesMasterConfig" in the example. your config should look like: admissionConfig: pluginConfig: builddefualtconfig goes here kubernetesMasterConfig: blahblah
Hello Ben, I tried that also in admissionConfig, and it still doesn't work: admissionConfig: pluginConfig: BuildDefaults: configuration: apiVersion: v1 env: - name: BUILD_LOGLEVEL value: 9 - name: NO_PROXY value: .cluster.local,172.30.0.0,0.0.0.0 kind: BuildDefaultsConfig I did test on both locations. It doesn't work. Just for your info, I restarted the master-api and master-controllers service. Thx
how are you confirming the variables are not being set? they will not show up in the buildconfig or in the buildobject. the only way to really check is to have your Dockerfile or assemble script reference them.
Hello Ben, I am configuring the logging level of the build: - name: BUILD_LOGLEVEL value: 9 So I expect that I would see the full build log. However, I edited it, restarted master-api and controllers service. Somehow the build will stay in New status, no pod is created. Any idea? thx
oc describe the build please, and also provide the build yaml.
fyi this master-config worked as expected for me: admissionConfig: pluginConfig: BuildDefaults: configuration: apiVersion: v1 kind: BuildDefaultsConfig env: - name: BUILD_LOGLEVEL value: "8" ................ your issue may be that you did not quote 9, but in my case not doing so resulted in the server not even starting up because the master-config is not parseable.
Hello Ben, yes, this could be the issue. I will test it on my lab and let you know. Thx
Hello Ben and Vladislav It both works in version openshift v3.5.5.31.1 and v3.4.1.44.1 and add test case(id:OCP-14967) for the senario.
Not correct. The admission config does not go in the kubernetesMasterConfig section. The docs are incorrect. This PR fixed them and apparently was never ported into the OCP docs: https://github.com/openshift/openshift-docs/pull/3480 I'm going to reassign this bug to the docs team to get the changes into the OCP docs.
As Ben said above, this was a problem with the release. This has been fixed. As mentioned in the PR, here's the links to the published sections: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.5/html-single/installation_and_configuration/#manually-setting-global-build-defaults https://access.redhat.com/documentation/en-us/openshift_container_platform/3.5/html-single/installation_and_configuration/#manually-setting-global-build-overrides If there's more to this BZ, then please let us know. I'll close this BZ.