Bug 1379940 - db:migrate failure : unexpected format of report attribute encountered
Summary: db:migrate failure : unexpected format of report attribute encountered
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.6.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: GA
: 5.7.0
Assignee: Gregg Tanzillo
QA Contact: Jan Krocil
URL:
Whiteboard: upgrade:migration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-28 07:58 UTC by Prasad Mukhedkar
Modified: 2020-01-17 15:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-18 18:48:21 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
Error_ruby run history from our lab (208.68 KB, text/plain)
2016-10-19 07:23 UTC, tachoi
no flags Details

Comment 5 tachoi 2016-10-10 02:58:32 UTC
Imported customer db in our lab and did migrate. but all went well
CEE thought only difference would be minor version difference
- our lab ver: 5.6.0.13-1
- customer ver: 5.6.0.13-20160624114606_13a9153

Recommended customer to upgrade CFME to the latest version and try again.

However, customer reported back when they tried to use pg_dump/restore command rather than psql command, all went well without upgrading CFME code. Also they reported that there is a possibility that someone deleted customized report which is preventing migration in between those attempts.

Initially, customer reported that they followed https://access.redhat.com/articles/2327481 documentation for the upgrade task which is having pg_dump command but it seems like customer used psql command actually.

Comment 6 tachoi 2016-10-10 03:03:10 UTC
For the deleting customized report, the possibility is very low as we did successfully import/migrate their db in our lab, if there was violated report, we would have seen it from our lab.

Comment 8 tachoi 2016-10-19 07:23:53 UTC
Created attachment 1211995 [details]
Error_ruby run history from our lab


Note You need to log in before you can comment on or make changes to this bug.