[katello-devel] activation keys referencing non-existent pools

[Brad Buckingham]

Tom,

Regarding the related note, I do not recall the background as to why an 
active record model was created in Katello for the akey-pool 
relationship; however, if the Katello model does not provide anything 
beyond what Candlepin provides, it could probably be refactored out in 
the future.

thanks,
Brad

On 04/27/2012 03:11 PM, Tom McKay wrote:
> I don't think disabling is an option. It's not there any more so there's nothing to reference.
>
> On a related note, it bothers me that we have our own activation keys at all that lie completely outside of candlepin. Shouldn't we be letting candlepin handle them and piggy-backing any additional info?
>
>
> ----- Original Message -----
>> From: "Og Maciel"<omaciel at redhat.com>
>> To: "Tom McKay"<thomasmckay at redhat.com>
>> Cc: katello-devel at redhat.com
>> Sent: Friday, April 27, 2012 3:07:34 PM
>> Subject: Re: [katello-devel] activation keys referencing non-existent pools
>>
>> ----- Original Message -----
>>> From: "Tom McKay"<thomasmckay at redhat.com>
>>> My thinking for a fix is that in models/activation_key I would
>>> check
>>> with candlepin that all of the pools referenced are still valid. If
>>> any are no longer valid, remove the reference and save the record.
>> Maybe disable instead of deleting? This way the end user is not
>> surprised when the next day that pool is gone...
>> --
>> Og Maciel
>>
>> Senior QA Engineer
>> Red Hat, Inc.
>> +1.919.754.4782
>> Freenode: OgMaciel
>>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel