PrajaktaPurohit
commented
2 years ago The Infra server team will try reproducing and discuss with the automate team how this can be implemented:
- The last_checked_in attribute is a part of the node data not the json, there might need to be some flags that get sent to the search api will will help the server pull this information from the db.
- Alternative is to query from the node API (might be expensive)
We are in the process from updating from Chef Server 12.5.1 to Chef Infra Server 14.5.29-1. I have migrated our data from Chef Server 12.5.1 to the new Chef Server using knife-ec-backup/knife-ec-restore.
I can connect our clients to the new Chef Server. However, for some reason, when I search for the connected clients in Chef Automate, it seems like the Last Check-In time is not updating. The clients are running Chef Client 12.13.37-1.
Is there something else I need to add, in order for the clients to show that they have Checked In, in Chef Automate?
Any help would be appreciated. Thank you.
This ticket includes a secure attachment. Use this link to access the attached files: Package ID# WF93-RFE2
To Reproduce 1/ Navigate to Automate UI > Infrastructure > Client Runs -- See the check-in time of the node. 2/ Navigate to Automate UI > Infrastructure > Chef Infra Server > Nodes -- See the Last check-in time of the node. Last Check-in time is empty for all the nodes. PFA the screen shots.
Expected behavior Last Check-in time should be updated on the nodes section in Automate UI.