It could be Red Hat fault, not Katello. Some users are complaining that Red Hat put 7.3 packages in 7.2 repo:
https://www.reddit.com/r/redhat/comments/5aybxs/red_hat_powers_network_storage_performance_with/d9kcc8f/ trešdiena, 2016. gada 9. novembris 07:01:09 UTC+1, Unix SA rakstīja: > > >>As Sean mentions. When 7.3 is released, the 7.2 repo will still be well, > 7.2 > > this is not correct, recently i did sync for 7.2, and it included 7.3 > rpms, due to this, my OS is getting installed with 7.3 .. > > > On Monday, 10 October 2016 07:38:56 UTC+5:30, Andrew Schofield wrote: >> >> As Sean mentions. When 7.3 is released, the 7.2 repo will still be well, >> 7.2. If you're not using 7Server then you don't need to create a filtered >> view (although the general recommendation is to create a filtered view...). >> When 7.3 is released, so will a new RHEL 7 repo 7.3... >> >> On Tuesday, October 4, 2016 at 1:23:41 AM UTC-4, Unix SA wrote: >>> >>> Hello, >>> >>> i am using RHEL7.2 repo only ... and i continully sync it for updates >>> till RHEL7.3 release, after RHEL7.3 release, i will freeze RHEL7.2 and keep >>> updating RHEL7.3 and for RHEL7.2, will only add Erratas and bug fixes. >>> >>> Thanks, >>> Dhaval >>> >>> On Monday, 3 October 2016 17:17:59 UTC+5:30, Sean O'Keeffe wrote: >>>> >>>> Why not just sync the RHEL7.2 repo and use that in the content view ? I >>>> assume you are currently using the RHEL 7Server repo >>>> >>>> On Monday, 3 October 2016, Unix SA <[email protected]> wrote: >>>> >>>>> Hello, >>>>> >>>>> >>>>> I have some requirement so when i am working on RHEL7.2 OS release, i >>>>> sync repos daily night and run some CI jobs and publish and promote CV >>>>> version as per success of jobs. >>>>> >>>>> now when RHEL7.3 OS is ready to release, i want to freeze sync for >>>>> RHEL7.2 CV and below is what i think i should be doing >>>>> >>>>> 1) i will create filter with "Include all rmps" and "include all >>>>> errata up to today's date" ... >>>>> >>>>> 2) publish CV, and promote it to all life cycle envs >>>>> >>>>> 3) now i will start updating 7.3 CV till 7.4 releases .. >>>>> >>>>> 4) if any bug fix or erratas comes in, i will "include" that in 7.2 CV >>>>> (filters) and publish. >>>>> >>>>> >>>>> >>>>> Now question i have is, when i do step 1 above, is it good step to >>>>> freeze CV? is that CV version will be same as earlier version (before >>>>> filters) ? >>>>> >>>>> >>>>> Do i need to include "package groups" or it automatically include >>>>> those ? >>>>> >>>>> >>>>> whenever new erratas come in, i will change "Errata" date or include >>>>> another filter to include errata date to today, and publish CV, when i >>>>> publish CV will it change any RPM version as well ? ( apart from errata? >>>>> , >>>>> for example kernel rpm version ) >>>>> >>>>> >>>>> Does anyone have some better way of doing it? >>>>> >>>>> >>>>> Thanks, >>>>> DJ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Foreman users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/foreman-users. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
