I'm seeing this issue again. We cannot avoid setting host port because it is needed for accessing the service from external networks.
On Mon, Dec 29, 2014 at 1:13 PM, Imesh Gunaratne <[email protected]> wrote: > Hi Devs, > > I found another problem with Kubernetes v0.5.2 while testing the > 4.1.0-alpha codebase. The problem is that when the host port is set in > container ports, the api server throws the following error when a > replication controller is created: > > Error scheduling [pod-id] The assignment would cause a constraint > violation; retrying > > As I found this issue has been already identified and fixed here: > https://github.com/openshift/origin/issues/210 > > I'm now trying to test without setting the host port, will update with the > status. > > Thanks > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
