Kibana status is showing incorrect build hash

[liza-mae]

Kibana version: Latest 7.13 and 7.14 snapshots

Server OS version: Ubuntu

Original install method (e.g. download page, yum, from source, etc.):
Snapshots

Description of the problem including expected versus actual behavior:
When I run /api/status the build_hash for 7.13 is incorrect and invalid.

Steps to reproduce:

1. Install latest snapshot for 7.13 or 7.14
2. Go to /api/status, observe the build hash is incorrect/invalid.

Both 7.13 and 7.14 are showing the same hash and the last time it worked was on Jun 4. Both are showing this hash 5b2de169-2785-441b-ae8c-186a1936b17d.

7.13.2

{"name":"e26da0b0eba8","uuid":"5b2de169-2785-441b-ae8c-186a1936b17d","version":{"number":"7.13.2","build_hash":"5cab87e2069dd31848490f83964291fc802d6889","build_number":40927,"build_snapshot":true},"status":{"overall":{"since":"2021-06-07T05:18:23.866Z","state":"green","title":"Green","nickname":"Looking good","icon":"success","uiColor":"secondary"},"statuses":[{"id":"core:elasticsearch@7.13.2","message":"Elasticsearch is available","since":"2021-06-07T05:18:23.866Z","state":"green","icon":"success","uiColor":"secondary"},{"id":"core:savedObjects@7.13.2","message":"SavedObjects service has completed migrations and is available","since":"2021-06-07T05:18:23.866Z","state":"green","icon":"success","uiColor":"secondary"}

7.14.0

{"name":"8e872e923e30","uuid":"5b2de169-2785-441b-ae8c-186a1936b17d","version":{"number":"7.14.0","build_hash":"5cab87e2069dd31848490f83964291fc802d6889","build_number":41498,"build_snapshot":true},"status":{"overall":{"since":"2021-06-06T10:14:02.207Z","state":"green","title":"Green","nickname":"Looking good","icon":"success","uiColor":"secondary"},"statuses":[{"id":"core:elasticsearch@7.14.0","message":"Elasticsearch is available","since":"2021-06-06T10:14:02.207Z","state":"green","icon":"success","uiColor":"secondary"},{"id":"core:savedObjects@7.14.0","message":"SavedObjects service has completed migrations and is available","since":"2021-06-06T10:14:02.207Z","state":"green","icon":"success","uiColor":"secondary"}

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[jbudz]

Can you share where the builds are from or where they were started? Trying to track this down - I ran a few local builds and the checked artifacts API snapshots - build_hashes seem to be functioning there.

[liza-mae]

@jbudz This is on cloud.

[mshustov]

We need to validate that sha in package.json contains different values for both versions.

[liza-mae]

@mshustov I confirmed the sha is different in both versions.

[tylersmalley]

I did find this is a valid commit hash on the Infra repo: https://github.com/elastic/infra/commit/5cab87e2069dd31848490f83964291fc802d6889

[liza-mae]

This is not specific to cloud, installed on-prem on Ubuntu and same issue. @tylersmalley is right the build_hash is matching up with the infra repo not kibana repo.