Description of problem: The v1beta3 is in master-config.yaml after upgrade. As design 'support for the v1beta3 api was removed in 3.1. /etc/origin/master/master-config.yml cannot have it listed as one of the `apiLevels`, it should be removed from master-config.yaml Version-Release number of selected component (if applicable): openshift-ansible-playbooks-3.0.7-1.git.156.70ed54c.el7aos.noarch How reproducible: always Steps to Reproduce: 1. upgrade from v3.0.2 to v3.1 2. check the api level in master-config.yaml after upgrade Actual results: # head master-config.yaml apiLevels: - v1beta3 - v1 apiVersion: v1 assetConfig: logoutURL: "" masterPublicURL: https://openshift-120.lab.sjc.redhat.com:8443 publicURL: https://openshift-120.lab.sjc.redhat.com:8443/console/ Expected results: The api level support for the v1beta3 should be removed. Additional info:
I'm not able to duplicate this? Did you verify that the 3.1 repo was available and the deployment_type was set to openshift_enterprise? Otherwise only a 3.0 minor upgrade would be performed. Any additional information that you could provide related to how the upgrade was performed (installer wrapper vs ansible directly, configuration files, etc) would help troubleshoot the problem.
Verified and pass. the v1beta3 was removed from master-config.yml
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://access.redhat.com/errata/RHEA-2015:2492