Hi, I don't think this is an issue of the Automatic Deployment component but I am trying to find out what could cause this (and how to avoid it in the future). We had the following error when using the automatic deployment from our DEV to TST environment. The error occurred on 3 consecutive days (but every day it was another module).Module XXX was successfully deployed but marked as inconsistent. Check error log for more details. Module should be published again before publishing consumers. The following conditions probably play a role or are a side effect of the problem:
Any hints to point me into the right direction?Kind regards,Arthur Haine
Hi Arthur,
The Automatic Deployment should be able to handle outdated modules. LifeTime (also the API) checks for broken references before the deployment, so when you try to deploy any outdated modules, this should not be a problem.
When I look at your question, the most important part for me is the last bullet about the versioning in the log. When you use Automatic Deployment to deploy, it looks for all modules that have a changed version on DEV and checks if this version is different from TST. When they are different, the system tries to create a new version number (1.2.3) where the last digit is incremented (1.2.4).
When you have done a hotfix on TST and manually upgraded this version (to 1.3), the next deployment run, the system will try to publish version (1.2.5), because the last version on DEV was still (1.2.4). The system will then return an error that the deployment failed, because (1.2.5) is lower than (1.3). You'll have to manually update the Version Tag in LifeTime to at least the same number as you have done for the hotfix (when nothing changed, otherwise use a higher version number).
This still doesn't make sense in the rest of your question, because you mention that some modules were published successfully... Which is not possible when the version number is the culprit. Then there was no deployment at all.
Can you check in the Deployment Plan history which deployment plans failed and see if they have anything in their deployment log that can explain what happened?
Otherwise, I'm thinking that somebody tried a manual deployment during the automatic deployment or a direct change on TST during a deployment.
Kind regards,
Remco Dekkinga
Hi,
Also your consumer and producer module do not have any inconsistency(Outdated) on both the module.
Thanks
CV
hi CV, I am not sure of that. There could have been outdated modules. I do know for sure they were not incompatible.Do you think outdated modules cause this error? Arthur
Hi Remco,Thanks for your quick and elaborate answer. The version part makes sense (I did not manually change version tags). I will try to get more details from the deployment plan and post them here.Kind regards,Arthur
Hi Remco,
The deployment notes only mention the same error. The time of the deploy makes me pretty confident no one else is publishing (3:00 AM). From your answer I think it must be something with mismatched version numbers as I did see something in the logging about it.I have some test modules I can play around with to try to recreate the issue (just to understand it). I will post the results.Kind regards,Arthur Haine
Remco,I have tried to recreate the problem several times with different ways of trying to make the versions collide but was unsuccessful. It must have been some kind of glitch that created this situation. As I said I don't think it is related to the automatic deployment component so thanks for thinking along!In case it will happen in the future I will get back to this thread.Kind regards,
Arthur Haine