Red Hat Bugzilla – Bug 1020966
Mappings defaults to TCP when to Protocols specified in manifest.yml
Last modified: 2015-05-14 19:30:44 EDT
Description of problem: This issue came from the Zend cartridge, where they are using this Endpoint: - Private-IP-Name: IP Private-Port-Name: CONSOLE_PORT Private-Port: 16081 Public-Port-Name: PROXY_CONSOLE_PORT Mappings: - Frontend: "/ZendServer" Backend: "/ZendServer" Having this in manifest.yml and deployed on the latest devenv, will cause that the endpoint is not properly created, due to the missing 'Protocols: [http]' property. Without this property, OpenShift will default to TCP protocol, which is not what is expected I think... I think we should default to '[http,ws]'. Steps to Reproduce: 1. Create app with mappings set to something like in Description 2. The '/ZendServer' URl will not be routed to IP:CONSOLE_PORT/ZendServer Expected results: The routing should work as before, without breaking compatibility. Additional info: I would also suggest to update Documentation and explain the Protocol directive to cartridge authors.
If this is not the first endpoint in the manifest, then the behavior is expected. You should add ['http','ws'] as its protocol. Keeping this bug open to update the documentation.
The pre-protocols behaviour was to assume http if a mapping was specified. Stage: https://github.com/openshift/origin-server/pull/3929 Master: https://github.com/openshift/origin-server/pull/3930 Release ticket updated.
*** This bug has been marked as a duplicate of bug 1020791 ***
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/531f9f3a0596c05c17c1c0ed3039036ceefb974c Bug 1020966 - the pre protocols behaviour was to assume http if there was a mapping defined. Do that by default.