-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
None
When populating a system by conduit and the RHSM API returns the fact "cpu.thread(s)_per_core" with value "confidential" instead of a number, we throw an exception and don't populate this system in HBI:
2024-09-17T00:50:41.801+0000 [thread=rhsm-conduit-task-processor-0-C-1] [level=WARN] [category=org.candlepin.subscriptions.conduit.InventoryController] - Skipping consumer e14a08e7-dbc8-494a-8e77-28cdefef99c1 due to exception java.lang.NumberFormatException: For input string: "confidential" at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) at java.base/java.lang.Integer.parseInt(Integer.java:668) at java.base/java.lang.Integer.parseInt(Integer.java:786) at org.candlepin.subscriptions.conduit.InventoryController.extractHardwareFacts(InventoryController.java:329) at org.candlepin.subscriptions.conduit.InventoryController.getFactsFromConsumer(InventoryController.java:205) at org.candlepin.subscriptions.conduit.InventoryController.lambda$validateConsumer$10(InventoryController.java:676) at io.micrometer.core.instrument.AbstractTimer.recordCallable(AbstractTimer.java:178) at org.candlepin.subscriptions.conduit.InventoryController.validateConsumer(InventoryController.java:676) at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
This happens a lot in production, see splunk query here.
Acceptance Criteria
- If the fact "cpu.thread(s)_per_core" is not present or the value present is not a number, we should not update this fact in HBI and move forward.
- relates to
-
SWATCH-2917 Improve logging to identify systems being updated in conduit
-
- Closed
-