Known Issue: The lightweight Kubernetes agent incorrectly logs an inventory upload as a failure if the beacon returns an HTTP status of 201 CREATED (IOJ-2233879)
Known Issue: The lightweight Kubernetes agent incorrectly logs an inventory upload as a failure if the beacon returns an HTTP status of 201 CREATED (IOJ-2233879)
Summary
When the lightweight Kubernetes agent uploads an inventory file to a beacon, the agent's logging incorrectly suggests the upload has failed if the beacon returns an HTTP 201 CREATED status code.
Despite this, the inventory is actually successfully uploaded.
Details
Logging from the lightweight Kubernetes agent shows details similar to the following when this issue occurs:
lwk 2021-11-24T17:19:24.384104218Z INFO – inv: producing initial inventory
lwk 2021-11-24T17:19:24.42259509Z INFO – inv: uploading k8s-inventory-1e0369a0-20211124T171924.ndi
lwk 2021-11-24T17:19:32.490747497Z ERROR – inv: error producing inventory: inv: failed upload: upload: bad status code 201:
Despite the logging referring to a "failed upload", the status code 201 can generally be trusted to indicate a successful upload.
Fix details
This issue has been fixed by updating the lightweight Kubernetes agent to correctly handle HTTP status codes representing success.
Fix status
This issue has been fixed in the following FlexNet Manager Suite releases: 2021 R1.4 / Mar 2022 (Cloud), 2022 R1 (On Premises)
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
