[katello-devel] Manifest import error handling

[James Labocki]

----- Original Message -----
> From: "Marek Hulan" <mhulan at redhat.com>
> To: katello-devel at redhat.com
> Sent: Wednesday, January 16, 2013 3:08:15 AM
> Subject: [katello-devel] Manifest import error handling
> 
> Hi all
> 
> I'd like to know you opinion about about changes I'm going to
> introduce to
> solve a bug related to manifest import [1]. I described a proposed
> solution on
> wiki [2]. Comments?
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=790064
> [2]
> https://fedorahosted.org/katello/wiki/ManifestImportErrorHandlingDesign
> 

Putting on my user hat for a moment. The manifest import is something that is likely to occur on a less frequent basis then is the content synchronization. For example, if we look at the use of katello over 3 months in an organization it might be something like this:

Day 1  - Installation (Create orgs, import Red Hat manifests, synchronize content)
Day 7  - Sync new repositories (Sync JBoss, for example)
Day 30 - Sync new repositories (Sync OpenShift Enterprise, for example)
Day 45 - Sync new repositories (Sync Red Hat Storage, for example)
Day 50 - Purchase new entitlements from Red Hat (For RHEV, for example)
Day 51 - Import new manifest into org to obtain access to new entitlements (RHEV)
Day 51 - Sync new repositories (Sync RHEV, for example)

Given this, I think it would be important to notify the user when they are in the content syncrhonization page that certain products were not enabled because they failed during manifest import. This is not only because the actions may occur days apart (importing manfiest and syncing content), but because they may be done by different users within Katello. 

Just my .02 cents, not sure if it's outside of the scope of this or not.


> Thank you
> 
> --
> Marek
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>