Feature Overview

Currently a system must perform a sequence of steps before patch knows which advisories are installable or not:

• subscription-manager must refresh either manually or via rhsmcertd after ~6 hours
• dnf must decide to fetch new metadata, which won't happen unless some yum action is performed (and the default cache limit ~48hours) has expired
• insights-client needs to checkin which only runs ever ~24 hours

This can be frustrating for new users.  Since console dot knows everything about the template already, this shouldn't be necessary. 

This should not affect package installability, as that will still rely on the system checking in 

Background and Strategic Fit

Goals & requirements

Installable advisory updates for a system are available immediately* upon:

• Assigning a template
• removing a template
• updating a template's date
• adding or removing a repository from a template

• immediately defined as within ~30 seconds.

  Non-Functional Requirements

  Use Cases (User Experience & Workflow)

• User has an already registered system
• User assigns it to a content template
• User navigates to patch
• User sees installable advisories

Customer Considerations

< Enumerate any customer considerations that would add further clarification and context for this feature. Are there assumptions being made regarding prerequisites and dependencies? Are there assumptions about hardware, software or specific skill sets needed to deliver?>

Documentation Considerations

• May need to update documentation to reflect this