Oc describe node shows memory in mili instead of in Mi

[Dorsosiv]

I check my nodes using the command oc describe node.
When I scrolled I saw some nodes that had in the allocated resources -> memory section, the memory was written like its in milicores.
A good node:

Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests       Limits
  --------           --------       ------
  cpu                5099m (67%)    827630m (11035%)
  memory             10136Mi (68%)  14864Mi (99%)
  ephemeral-storage  0 (0%)         0 (0%)
  hugepages-2Mi      0 (0%)         0 (0%)

A bad node: (and its not the only one, I saw a few besides it.)

Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests               Limits
  --------           --------               ------
  cpu                4939m (65%)            9830m (131%)
  memory             10122952704290m (64%)  19063111681024m (122%)
  ephemeral-storage  0 (0%)                 0 (0%)
  hugepages-2Mi      0 (0%)                 0 (0%)

Version

$ oc version
Client Version: 4.6.12
Server Version: 4.7.9
Kubernetes Version: v1.20.0+7d0a2b2

Steps To Reproduce

1. just oc describe node. I have not done something interesting and the environment is ok.

Current Result

Im getting the allocated resources in mili instead of Mi.

Expected Result

Getting from all the nodes the allocated resources in Mi.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.