Displaying notifications causes ActiveRecord::Attribute error about manageiq-schema HOT 6 CLOSED

Oleg came up with the conclusion that these records are not useful across versions. And we should not do heroics to keep the records alive.

from manageiq-schema.

Interesting, so options is able to be yaml loaded but when you walk the attributes, that's when it blows up? Weird.

Never trust a ActiveRecord::LazyAttributeHash.

from manageiq-schema.

I'm curious if it is a problem with CloudVolumes, or the specific error type. There are 4 cloud volume errors in the notifications table, the 4th one being that the cloud volume was removed.

Personal reference
errors: 468,469,470
ok: 467

from manageiq-schema.

I think the solution may be as simple as:

UPDATE notifications
SET options = REPLACE(options, 'ActiveRecord::Attribute', 'ActiveModel::Attribute')
WHERE (options LIKE '%ActiveR%');

Notification.where("options LIKE '%ActiveRecord%'") \
            .update_all("options = REPLACE(options, 'ActiveRecord::Attribute', 'ActiveModel::Attribute')"

from manageiq-schema.

Interesting, so options is able to be yaml loaded but when you walk the attributes, that's when it blows up? Weird.
-- @jrafanie

No, I can not access options, I got this data from sql

Never trust a ActiveRecord::LazyAttributeHash.

agreed

from manageiq-schema.

This has been deemed a low priority and the notifications can be cleared out between upgrades so a fix is present.
We are a number of miq versions past this problem so I am closing.

@chessbyte please open if you feel we still may want to address in the future

from manageiq-schema.