Description of problem: The Katello project is planning to migrate to pulpv2. It is possible that there are tens, hundreds or thousands of consumers registered to a given Katello instance when the server is upgraded. Each of those consumers would be running the pulpv1 version of the agent. This agent allows the consumers to receive package/package group/errata actions initiated from the server. Based on brief discussion with some Katello stakeholders, the expectation was that the pulpv2 server would interact with the older agents; however, this appears not to be the case. As a result, with the current implementation, admins would need to manually upgrade the agent on each of the consumers registered to Katello. Version-Release number of selected component (if applicable): pulpv2 beta
Last we discussed this, we decided this wasn't going to be addressed. Closing out as won't fix.