Description of problem:
In Candlepin, a consumer can list installed products. Each installed product will typically contain:
1. productId, e.g. 69
2. productName, e.g. Red Hat Enterprise Linux Server
3. version, e.g. 6.5
4. arch, e.g. x86_64
There are a few properties that should be met:
- It is expected that version will never be null.
- It is expected that arch will never be null.
- It is expected that arch will only contain one arch (that is, we expect "x86_64", and not something like "x86_64,ia64,x86")
However, looking at the Candlepin PROD DB, all of these properties have been broken by a few consumers. All have a null version, most will also have a null arch, and very few will have multiple arch's.
The reason why I'm listing this as a BZ with subscription-manager and not Candlepin is because I believe subscription-manager is not providing candlepin with the correct information in these instances.
Version-Release number of selected component (if applicable):
Hard to tell since the version is always null, but it happens to any RHEL Desktop/Server/Workstation, and I believe it can happen across version 6.x and 7.x.
I've not reproduced it, but I can provide evidence that it continues to be stored in Candlepin
Steps to Reproduce:
Installed products for a system can have a null version and a null arch. Or, a system can have a null version and a weird arch.
All Installed products will always specify a version and an arch.
@devs: It looks likely that the installed product information is not being updated from a very old certificate. We should investigate if current subman product id logic will update the product cert to a new version in the case that there is a cert with a null version (or different arch data).
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.