[Glass] error upgrading stone: become is not allowed

Dale Henrichs via Glass glass at lists.gemtalksystems.com
Thu Apr 27 11:30:57 PDT 2017



On 04/27/2017 11:14 AM, Johan Brichau via Glass wrote:
> Dale,
>
> Correction, I’ using this script: 
> https://github.com/glassdb/webEditionHome/blob/master/docs/upgrade/upgradeToGemStone3.2.md
>
> Should I check out the GsDevKit script?
> Since we have a directory structure for multiple stones on a server 
> that predates the one defined by GsDevKit, I’ve stayed away from it 
> for now.
>
The GsDevKit_home upgradeStone is intended to pretty much automate the 
whole upgrade process (including the running of the postconv script as 
described in the release notes) so I started with the steps described in 
webEditionHome and expanded them to include upgrades to versions other 
than 3.2 (each version boundary can present it's own little issues) and 
then fixes any issues that ran across iwhile testing ...

The script is regulary tested by doing upgrades between various versions 
of Gemstone on travis-ci[1], so I would recommend that you take a look 
at the script as inspiration for your own script ...

If you have an upgrade process that is working for you, then I would 
stick with it:)

Dale

[1] https://travis-ci.org/GsDevKit/GsDevKit_home/builds/219459311
>
>> On 27 Apr 2017, at 20:10, Johan Brichau <johan at yesplan.be 
>> <mailto:johan at yesplan.be>> wrote:
>>
>> Hey Dale,
>>
>>> I guess to start with, I'd like to see more of the stack …
>>
>> In the file in attachment.
>>
>>> So the first thing to explore is why you are migrating the class 
>>> when no class versions should have been created --- assuming that 
>>> the shape of the class NPGsFileWrapper hasn't changed …
>>
>> The old version of NPGsFileWrapper has become a subclass of 
>> Obsolete23GsFile in the upgraded extent.
>> Reloading our application code loads the NPGsFileWrapper class being 
>> a subclass of GsFile, triggering the instance migration.
>>
>>> I am also curious what steps you've done to do the upgrade prior to 
>>> loading. Ideally you would be doing something very similar to what 
>>> is done by the GsDevKit_home upgradeStone script[1] …
>>
>> I’m executing that script, with a boot load of GLASS1.0-beta.9-3
>> The application load script first uses GsUpgrader to load GLASS1 and 
>> latest Grease, etc… followed by a load of our ConfigurationOfNextPlan.
>>
>> Except this GsFileWrapper thing… the upgrade process is going well. 
>> Nothing in production yet, as we are sorting through compatibilities, 
>> automated tests for all platforms, quality checks,
>> But all in all, I must say I’m glad we’re finally able to do this at 
>> Yesplan ;)
>>
>> Thanks for any info you can think of to be a little bit at peace of 
>> mind with this issue!
>>
>> Johan
>>
>> <migrateStackError.txt>
>
>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170427/47f3b3bc/attachment.html>


More information about the Glass mailing list