When using property files to configure a server, if there is a failure, it is not easy to debug because applyConfig.py does AdminTask.applyConfigProperties('[-propertiesFileName ' + filename + ' -validate true]') w/o specifying a report file, so the details of any failure are lost. Something like AdminTask.applyConfigProperties('[-propertiesFileName ' + filename + ' -validate true -reportFileName applyConfigPropsReport.txt -reportFilterMechanism Errors]') would allow you to create a container from the image, shell into it and look at the failure. The alternative is to create a container from the image, shell into it and attempt to apply the config props again specifying a report file name, but since the config was saved by the build step, you're going to have issues with trying to apply the same config twice for those objects that were successfully created.
When using property files to configure a server, if there is a failure, it is not easy to debug because applyConfig.py does
AdminTask.applyConfigProperties('[-propertiesFileName ' + filename + ' -validate true]')w/o specifying a report file, so the details of any failure are lost. Something likeAdminTask.applyConfigProperties('[-propertiesFileName ' + filename + ' -validate true -reportFileName applyConfigPropsReport.txt -reportFilterMechanism Errors]')would allow you to create a container from the image, shell into it and look at the failure. The alternative is to create a container from the image, shell into it and attempt to apply the config props again specifying a report file name, but since the config was saved by the build step, you're going to have issues with trying to apply the same config twice for those objects that were successfully created.