Description of problem: The installer is putting the following problematic yaml code snippet at the very top of the master-config.yaml: admissionConfig: pluginConfig: BuildDefaults: configuration: apiVersion: v1 env: [] kind: BuildDefaultsConfig resources: limits: {} requests: {} BuildOverrides: configuration: apiVersion: v1 kind: BuildOverridesConfig openshift.io/ImagePolicy: configuration: apiVersion: v1 executionRules: - matchImageAnnotations: - key: images.openshift.io/deny-execution value: 'true' name: execution-denied onResources: - resource: pods - resource: builds reject: true skipOnResolutionFailure: true kind: ImagePolicyConfig That code snippet is interfearing with the parsers ability to pick up the loggingPublicURL. When looking in the Web UI you will not see the View Archive link. If I comment out or move the above code snippet to the bottom of the master-config.yaml the View Archive link appears again in the UI. Version-Release number of the following components: # rpm -q openshift-ansible openshift-ansible-3.6.173.0.5-3.git.0.522a92a.el7.noarch # rpm -q ansible ansible-2.3.1.0-3.el7.noarch # ansible --version ansible 2.3.1.0 config file = /etc/ansible/ansible.cfg configured module search path = Default w/o overrides python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] How reproducible: Every time Steps to Reproduce: 1. Install OCP 3.6 using the advanced installation method with openshift_hosted_logging_deploy=true 2. 3. Actual results: At the top of the master-config.yaml we see the following code snippet: admissionConfig: pluginConfig: BuildDefaults: configuration: apiVersion: v1 env: [] kind: BuildDefaultsConfig resources: limits: {} requests: {} BuildOverrides: configuration: apiVersion: v1 kind: BuildOverridesConfig openshift.io/ImagePolicy: configuration: apiVersion: v1 executionRules: - matchImageAnnotations: - key: images.openshift.io/deny-execution value: 'true' name: execution-denied onResources: - resource: pods - resource: builds reject: true skipOnResolutionFailure: true kind: ImagePolicyConfig Expected results: The admissionConfig should be put somewhere other than above apiLevels. Additional info:
Can you provide logs from atomic-openshift-master or atomic-openshift-master-api and the entire contents of master-config.yaml ? journalctl --no-pager -u atomic-openshift-master -u atomic-openshift-master-api
Created attachment 1316431 [details] master-config.yaml
Sorry, I no longer have the logs.
This doesn't reproduce for us, we'll need logs from a reproducer.
*** Bug 1506436 has been marked as a duplicate of this bug. ***
@Eric Is this something the logging roles would be involved in changing?
@Jeff, I don't know what logging can do if its already updating the "loggingPublicURL" setting for the master config. If the issue is parsing the config to pull out that value then it sounds like that would be an issue in the web console unless we're setting it under the wrong properties but it sounds like just moving the admissionConfig properties causes this to work. @Nick, You can confirm that on clusters that are not showing that "View Archive" url, there is a populated "loggingPublicURL" value in the master config?
Yes, there is in fact a populated loggingPublicURL value in the master config.
@Nick, I'm closing this as WFM unless you see otherwise based on #c16