Describe the bug
When a worker is starting, it has no state. During this period, the workers table shows "Creating" or "Job Creating," and the init count is not updating. The counters in the workers table are counted based on the worker's state. This means the worker should be in the 'init' state for the count to be updated.
Expected behavior
The init count should be updated according to the workers that are being created.
To Reproduce
Steps to reproduce the behavior:
Go to HKube Dashboard.
Create a new worker.
Click on Administration, then on Workers.
The new worker will be displayed, but the init count will be 0.
Additional context
The data for the workers counters is handled according to their states. You can find the stats in etcd, under discovery in task-executor, and then in actual->stats. You will see it listed as 'redundant' count since there is no state (the code treats a lack of state as redundant).
not relevant. Init state is given when Wrapper is being created.
When worker is starting, it has no state - but being handled as 'Creating'.
Issue closed.
HKube micro-service Worker
Describe the bug When a worker is starting, it has no state. During this period, the workers table shows "Creating" or "Job Creating," and the init count is not updating. The counters in the workers table are counted based on the worker's state. This means the worker should be in the 'init' state for the count to be updated.
Expected behavior The init count should be updated according to the workers that are being created.
To Reproduce Steps to reproduce the behavior:
Additional context The data for the workers counters is handled according to their states. You can find the stats in etcd, under discovery in task-executor, and then in actual->stats. You will see it listed as 'redundant' count since there is no state (the code treats a lack of state as redundant).