Red Hat Bugzilla – Bug 1284427
Appliances originally running 5.3.0 are using automations not present in their current release even after reset of the datastore
Last modified: 2015-11-26 09:27:19 EST
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):
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
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/
the datastore of ManageIQ and RedHat are comparable to the contents of a deployed 184.108.40.206 (if 220.127.116.11 is the level the apppliance is updated to)
note : to reset the datastore the UI is used.
Created attachment 1097613 [details]
datastore affected - export taken after reset.
Created attachment 1097614 [details]
datastore sample from a 18.104.22.168 appliance.zip
attaching the datastores used to generate the diff as well
*** Bug 1284426 has been marked as a duplicate of this bug. ***
Could you please provide the logs after you done the reset from the UI.
Do you have an environment setup to reproduce this issue? If so, can I access it?
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:export DOMAIN=ManageIQ EXPORT_AS=different_name_here_if_you_want EXPORT_DIR=./db/fixtures/ae_datastore
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-22.214.171.124 deployed systems updated to 126.96.36.199 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.
I'm still investigating your issue, but there are few things I'd like to mention.
My understanding of the attached datastores.
datastore sample 188.8.131.52 - initial 184.108.40.206 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 220.127.116.11. and the datastore reset did the right thing and brought it to the 18.104.22.168 level.
datastore sample 22.214.171.124 IVRSM - 7 instances/ 8 methods
datastore affected IVRSM - 11 instances/ 9 methods
I've attached the ManageIQ domains for versions 126.96.36.199, 188.8.131.52, and 184.108.40.206 which I've gotten from checking out the various branches.
220.127.116.11 IVRSM - 11 instances / 9 methods
18.104.22.168 IVRSM - 11 instances / 9 methods
22.214.171.124 IVRSM - 7 instances / 8 methods
vm-207's ManageIQ domain has the IVRSM 11/9 count like it should and the preserved ManageIQ_126.96.36.199 IVRSM counts of 7/8 look like that of the 188.8.131.52 version.
We're on holiday for a few days, but I'll check in on the ticket.
my reference system was not in the state I thought it was - closing as not a bug.