migtools / crane-runner

Apache License 2.0
2 stars 11 forks source link

[BUG] After migrating to OCP4.9 pods are not running #28

Open varodrig opened 2 years ago

varodrig commented 2 years ago

What version of crane are you running, and what are your clutsters+platform

Platforms

To get the crane/crane-lib version:

crane: Version: v0.0.3 crane-lib: Version: v0.0.5

What date were you attending the hackathon?

Monday Jan31 -Tuesday Feb1st

What scenario were you running when you encountered the issue?

https://crane-docs.konveyor.io/content/examples/stateless-app-mirror/ but changing the destination platform

What did you expect to happen?

-redis master and slave pods running (no data though)

What actually happened?

Service object has the same clusterIP address than the source cluster. I have changed this, but still with issues. The deployment confi

Please include any relevant logs or errors

frontend Pod logs

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.131.0.156. Set the 'ServerName' directive globally to suppress this message (13)Permission denied: AH00072: make_sock: could not bind to address [::]:80 (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down AH00015: Unable to open logs


Annotation in the frontend pod:

annotations: k8s.v1.cni.cncf.io/network-status: |- [{ "name": "openshift-sdn", "interface": "eth0", "ips": [ "10.131.0.156" ], "default": true, "dns": {} }] k8s.v1.cni.cncf.io/networks-status: |- [{ "name": "openshift-sdn", "interface": "eth0", "ips": [ "10.131.0.156" ], "default": true, "dns": {} }]