When creating a custom errata, the CSV of "affected packages" search can fail to match a package in pulp when fields are blank.  When this happens, no feedback is given in either the REST API reply or CLI output.  There is nothing in the pulp.log to indicate that the empty field(s) caused the package to not be found in pulp.  The errata is just created.

Another issues is that the "affected packages" seems to be matched on the filename/checksum in the CSV but when matching to applicable consumers, uses the NEVRA specified in the CVS.  Since the NEVRA can be different than the package referened by the filename/checksum, users can create an errata that appears to reference the correct package but will not match on NEVRA when applying to consumers as expected.