After digging into this, it appears that it's possible the OCP4 cluster may not be configured to allow users to create services with externalIPs. In OCP3 this was a setting in the `master-config-yaml` file. I am trying to learn more about how the cluster network operator can be configured to allow for external IPs.
Okay, I have learned more and it appears that the migration here will succeed assuming the OCP4 cluster has been configured to allow for externalIPs. I was able to migrate a loadbalancer service to my OCP 4.2 cluster, but looking at the network configuration (Go to Administration->Cluster Settings->Global Configuration->Network) I do not have a configured `externalIP` policy:
- cidr: 10.128.0.0/14
I migrated a loadbalancer service and our plugin properly cleared the `externalIPs` from the service so that the OCP4 cluster assigned the svc a new external IP.
Sergio, could you please look at your cluster configuration on the target and see if it matches mine? I'm curious if different externalIP policies could be breaking this. If this is the case, we may need to solve this in the CPMA tool.
Assuming that Sergio confirms this issue was related to a cluster configuration, I'd like to treat this BZ as a RFE to add more validations to CAM.
Tracking this under an epic in JIRA: https://issues.redhat.com/browse/MIG-167
My initial thoughts are a validation at this level would require a different pattern than we've implemented up to now, I'm assigning this to next release as we build up more use-cases for expanded validation.
Closing as this is quite old, and I expect that we'll continue to track this via the RFE Jira.