Grouper Users - Open Discussion List

[Shilen Patel <>]

Yeah I believe it should be safe to run.  And you may want to run the
others too in case they were missed?

./bin/gsh.sh misc/postGrouper2_2Upgrade.gsh

./bin/gsh.sh misc/postGrouper2_2_1Upgrade.gsh

./bin/gsh.sh misc/postGrouper2_3_0Upgrade.gsh





Thanks!

- Shilen



On 7/15/16, 8:25 AM, "Scott Koranda" 
<>
 wrote:

>Hi,
>
>> First off, the loader type and assignments on groups should have been
>>migrated
>> during the upgrade.
>
>Understood.
>
>> Did you use the installer to upgrade or did you do it
>> manually?  
>
>Installer.
>
>> The installer would have run postGrouper2_2Upgrade.gsh to upgrade
>> the legacy attributes (among other things).
>
>I have done other upgrades on other systems (including a
>production deployement) and yes, that worked fine.
>
>I think I just missed something with this dev system.
>
>> If you did it manually, you would
>> have presumably followed the 2.2 and 2.3 upgrade instructions.  The 2.2
>> instructions 
>>(https://urldefense.proofpoint.com/v2/url?u=https-3A__spaces.internet2.ed
>>u_display_Grouper_&d=CwIBAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc
>>&r=sWqutME58phurE0oO57Icg&m=rL2edn_zpqSHOsJACyCAEvKMWCHfvjHxzbMst3onGvY&s
>>=sqCzbWLKIErBncL43wrpWXhUrBJOFcIzKsLGcCafCpo&e=
>> v2.2+Upgrade+Instructions+from+v2.1) step 9 deals with this.
>> 
>> Setting loader.autoadd.typesAttributes to true isn't working for you
>>because
>> the code sees that the migration above didn't complete.  You can re-run
>>the
>> migration:
>> 
>> new MigrateLegacyAttributes().saveUpdates(true).fullMigration()
>
>Thanks. That is what I was looking for.
>
>> Though if the postGrouper2_2Upgrade.gsh wasn't run at all, you'll run
>>into
>> other problems.
>
>Is it "safe" to run that now manually?
>
>> And if you want to add it manually, I updated the gsh commands on the
>>wiki.
>
>Thanks,
>
>Scott
>