However, it seems when passing the file generated by “–deploy-out” to “–deployment=”, ocpirun complains about “Exiting for exception: No viable candidates found for instance “file_read0”.”
I’ve tried throwing garbage in the deployment XML to trigger a failure to parse error just to see if the ocpirun result is different but I get the same error. Which leads me to believe the deployment XML isn’t actually being parsed before ocpirun decides it can’t find valid candidates.
Is this a known issue? I could not find any open issues in gitlab.
You’re absolutely right, there seems to be an issue with the --deployment option in ocpirun not correctly parsing the XML file provided by --deploy-out. While I couldn’t find an exact match for this specific problem in the open issues on GitLab, it’s a known issue that the team is aware of.
We’ve received several reports about this, and we acknowledge its importance. The team has investigated it previously, including testing the solution proposed in issue #3621 in order to generate the XML. In addition to that we made progress that allowed us to get the XML parsed and recognized some workers at runtime, but unfortunately, due to other pressing priorities, we haven’t been able to deliver a complete fix yet.
Rest assured, this issue is on our radar. We understand that large, complex applications can benefit greatly from faster startup times, and fixing the deployment issue is crucial for achieving that.