[Pulp-dev] Katello/Pulp3 Integration meeting

Grant Gainey ggainey at redhat.com
Wed Mar 24 17:16:02 UTC 2021


Overview

   -

   Katello Schedule
   -

      3.18 November 2020
      -

         pulpcore 3.7
         -

      4.0 branching ~February 2021 (dry-run needed by end-of-Dec)
      -

         pulpcore 3.9
         -

      4.1 branching ~May 2021
      -

         pulpcore 3.10 (or newer)
         -

      4.2 branching ~August 2021
      -

      4.3 branching ~Nov 2021

Pulp

   -

   Pulpcore
   -

      3.12 slated for 6-APR
      -

         Auto-distribution
         -

         Fixes for imp/exp opened by katello
         -

   RPM
   -

      No release yet, will (probably) happen this week
      -

      One outstanding PR remaining
      -

         Allow-unsafe-advisory-resolution -
         https://github.com/pulp/pulp_rpm/pull/1950
         -

      ttereshc/jsherrill/dalley to discuss 3.10 fixes
      -

   Migration
   -

      0.10.0 released
      -

         Jsherrill to retest fix
         -

         Pulp2-orphaned-data will now be cleaned up in pulp2content-table
         -

      Known issues, not fixed
      -

         Zck in pulp2 https://pulp.plan.io/issues/8400
         -

         No declared artifact error https://pulp.plan.io/issues/8377
         -

            Unable to reproduce so far but reported by a katello user
            -

            Stephen to get ggainey a 6.9-level machine to test on
            -

   Ansible
   -

      Update about question from last week: token authentication is for
      katello-4.2
      -

   Pulp Container
   -

      2.2.1 released
      -

      2.4.0 released
      -

   Pulp CLI
   -

   FIPS discussion from bmbouters
   -

      GHA and public runners and security make us Sad
      -

      patch will be carried downstream-only


Katello

   -

   Dogfood testing
   -

      ttereshc to talk w/KatelloKrew about some findings
      -

   work on 3.11 upgrade starting
   -

   Ansible collection work ongoing (token support for syncing)
   -

   Auth’d podman pull support on container gateway
   -

   Pipeline for live vcr testing with latest bindings


QE

   -

   New test scenario added + continue testing
   -

      Remigration scenarios + switchover
      -

      Remigration after fixing corrupted/missing rpm + switchover
      -

   Customer & dogfood DB
   -

      Successful migration on both
      -

      Need to verify sample data set on dogfood to ensure migration is
      correct
      -

      Tanya created script to better list out missing/corrupted RPM
      -

   No new BZs filed
   -

   Still testing 4 ON_QAs
   -

      Reset ruby binding -
      https://bugzilla.redhat.com/show_bug.cgi?id=1929392
      -

         Best to leave this until katello reset bz is in?
         -

      ForeignKeyViolation -
      https://bugzilla.redhat.com/show_bug.cgi?id=1929395
      -

         Question regarding tfm-rubygem-pulp_2to3_migration_client-0.8.0-1
         because snap 18 has 0.7.0
         -

         The important package is python3-pulp_2to3_migration which should
         be 0.9.0
         -

   Snap 19
   -

      Will all pulp bz with QA whiteboard “Pulp3” be in final snap?
      -

         13 BZs (New, assigned, post, on_dev, modified)
         -


         https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&list_id=11768633&namedcmd=Pulp3
         -

         “Today’s build” is a GA Candidate for downstream
         -

   QE/Pulp3 discussion around automation of migration-related testing


G
-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210324/18c91762/attachment.htm>


More information about the Pulp-dev mailing list