Thanks for sharing Gregor. My/our bad, I was suspicious of how the templates were setup based on your emails and did not think what you shared could be something to do with the DB upgrade path bug.
Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com ________________________________ From: Riepl, Gregor (SWISS TXT) <gregor.ri...@swisstxt.ch> Sent: Monday, June 24, 2019 3:23:23 PM To: us...@cloudstack.apache.org; dev@cloudstack.apache.org Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0 > https://github.com/apache/cloudstack/pull/3417 > > > The issue only affects 4.11.2.0 users for which the upgrade path does > not run (a noop upgrade path runs) and it does not automatically fix > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've > mentioned workaround steps on the PR. This sounds pretty much exactly like the issue we had... https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E rohit.ya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
