Created attachment 1097611 [details] diff -r -q affected_datastore_extracted non_affected_datastore_extracted.out Description of problem: Appliances originally running 5.3.0 are using automations not present in their current release even after reset of the appliance's datastores Version-Release number of selected component (if applicable): 5.4.3.1 How reproducible: all the time Steps to Reproduce: 1. install a 5.3.0 appliance 2. create a sample automation 3. upgrade to 5.4 using the documented path from the release notes 4. reset the datastore Actual results: in the ManageIQ and RedHat automations, content dating from 5.3.0 will continue to be present even after reset of the appliance datastore, such as /ManageIQ/Infrastructure/VM/Retirement/ Expected results: the datastore of ManageIQ and RedHat are comparable to the contents of a deployed 5.4.3.1 (if 5.4.3.1 is the level the apppliance is updated to) Additional info:
note : to reset the datastore the UI is used.
Created attachment 1097613 [details] datastore_affected.zip datastore affected - export taken after reset.
Created attachment 1097614 [details] datastore sample from a 5.4.3.1 appliance.zip attaching the datastores used to generate the diff as well
*** Bug 1284426 has been marked as a duplicate of this bug. ***
Hi, Could you please provide the logs after you done the reset from the UI. Thanks, Madhu
Hi Felix, Do you have an environment setup to reproduce this issue? If so, can I access it? Thanks, Tina
While I investigate your issue further, there are rake tasks that might help you in the meantime. You can import and export the domains you want. Detail about the import/export commands: rake evm:automate:usage sample export rake evm:automate:export DOMAIN=ManageIQ EXPORT_AS=different_name_here_if_you_want EXPORT_DIR=./db/fixtures/ae_datastore sample import rake evm:automate:import DOMAIN=ManageIQ PREVIEW=false IMPORT_AS=can_rename_it_here_as_well IMPORT_DIR=./db/fixtures/ae_datastore
thanks for the commands - it may interest you that for cfme-5.4.2.0 deployed systems updated to 5.4.3.1 the /var/www/miq/vmdb/db/fixues/ae_database/ManageIQ content does show the /ManageIQ/Infrastructure/VM/Retirement/StateMachines/Methods.class/startretirement.rb but that is not showing up in the automation explorer at all.
Hi Felix, I'm still investigating your issue, but there are few things I'd like to mention. My understanding of the attached datastores. datastore sample 5.4.3.1 - initial 5.4.3.1 pristine datastore datastore affected - after reset The datastore contents look like they're reversed using the count of instances and methods for /Infrastructure/VM/Retirement/StateMachines/Methods(I'll refer to that as IVRSM) as an indication. It almost looks like you started with 5.2.0.0. and the datastore reset did the right thing and brought it to the 5.4.3.1 level. datastore sample 5.4.3.1 IVRSM - 7 instances/ 8 methods datastore affected IVRSM - 11 instances/ 9 methods I've attached the ManageIQ domains for versions 5.3.0.0, 5.4.2.0, and 5.4.3.1 which I've gotten from checking out the various branches. 5.4.3.1 IVRSM - 11 instances / 9 methods 5.4.2.0 IVRSM - 11 instances / 9 methods 5.3.0.0 IVRSM - 7 instances / 8 methods vm-207's ManageIQ domain has the IVRSM 11/9 count like it should and the preserved ManageIQ_5.4.3.1 IVRSM counts of 7/8 look like that of the 5.3.0.0 version. We're on holiday for a few days, but I'll check in on the ticket. Regards, Tina
my reference system was not in the state I thought it was - closing as not a bug.