chef / chef/chef-server

Nodes not updating last check in time

Open
#2,921 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect: Integration Component: opscode-erchef Triage: Try Reproducing Type: Bug
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Automate UI under Infrastructure > Client Runs and Infrastructure > Chef Infra Server > Nodes, using the stated Chef Infra Server and Chef Client versions. Compare the client-run check-in data with the empty node Last Check-in field; done means connected nodes display an updated Last Check-in time.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.