Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The issue in question is just caused by test data, no real data should ever appear like this. (at this point in time)
We discussed explicitly filtering out these alphanumeric provided product. We can't do that on the client as that's just backing ourselves into a corner should this situation ever arise.
Filtering it server side could be done, but IMO this can't happen with real data today, if it did, we'd need to support it, so a fix for this is a fix that would never be used until we needed to, in which case it would need to be undone.
Will's just going to fix the test data so this doesn't appear. If we start seeing alphanumeric provided product IDs in real world data, we'll have to have a discussion about what they're doing there and what that means. In meantime the filter to keep them out of entitlement certs (due to numeric OID issues in v1 certs) is still there. Probably better to just leave the data freeform. Test data fix incoming, let us know if you have concerns.
Comment 4Jesus M. Rodriguez
2014-06-26 14:45:24 UTC
Because this was test data related and not something the customer would ever see. I'm going to close the bug as NOTABUG. The test data has been fixed, but it seems a waste of time to track this and spend QA resources testing something that isn't a product issue.