Hide Forgot
Description of problem: I'm marking this as low priority, but wanted to document this bug. I do have a workaround. During my testing of openshift-ansible aws provisioning, I have noticed that there isn't support for having the API port be different than the load balancer port. What I am attempting to do is this: web browser -> ELB (port 443) -> Masters (port 8443) When openshift-ansible gets to the "Verify API" https://github.com/openshift/openshift-ansible/blob/release-3.9/roles/openshift_master/tasks/check_master_api_is_ready.yml#L8 The variable "openshift.master.api_url" gets set to "elb-dns-name:8443" This will not work, because the ELB is listening on port 443. My inventory has these variables set: openshift_master_api_port=8443 openshift_master_console_port=8443 This is correct, because I want the port on the instance to listen on 8443, and it gets setup correctly. The problem happens when the API url is generated, it tries to talk to the ELB on the wrong port, where it isn't listening. To work around this, I set everything to 443, so everything lines up: openshift_master_api_port=443 openshift_master_console_port=443 Version-Release number of selected component (if applicable): openshift-ansible 3.9
This behavior is fixed. openshift_master_api_port must be in extra_vars file or we default to the openshift_facts defaults key openshift_master_api_port=8443. We end up with mismatched elb listener, forwarder, healthcheck, instances OutOfService while api is listening on inventory openshift_master_api_port=443 To manually specify listening and forwarding port on ELB as well as api ports please set the values in role/openshift_aws/default/main file or override them in extra_vars.
Matt, can you provide a use case for this?
*** Bug 1569627 has been marked as a duplicate of this bug. ***
Per mwoodson the ask in this bz is no longer necessary. load balancer listener, forwarder and api ports will always be equal. Closing...
In my opinion, this is a bug, just not a high priority bug.