Multiple jobs fail on fetching resource metadata for serverless.kyma-project.io/v1alpha2

[Tomasz-Smelcerz-SAP]

Description

Multiple jobs fail with the following error:

 Upgrade test preparation
[ERROR] HttpError: Failed to fetch resource metadata for serverless.kyma-project.io/v1alpha2/Function: HTTP request failed
    1) CommerceMock test fixture should be ready


  0 passing (842ms)
  1 failing

  1) Upgrade test preparation
       CommerceMock test fixture should be ready:
     HttpError: Failed to fetch resource metadata for serverless.kyma-project.io/v1alpha2/Function: HTTP request failed
      at Request._callback (node_modules/@kubernetes/client-node/dist/object.js:416:32)
      at Request.self.callback (node_modules/request/request.js:185:22)
      at Request.<anonymous> (node_modules/request/request.js:1154:10)
      at IncomingMessage.<anonymous> (node_modules/request/request.js:1076:12)
      at endReadableNT (internal/streams/readable.js:1333:12)
      at processTicksAndRejections (internal/process/task_queues.js:82:21)

An example

It could be related to the v1alpha2 API version which is not recognized.

Expected result

The job doesn't fail

Actual result

Example 1 Example 2 Example 3

Steps to reproduce

Troubleshooting

[cnvergence]

It is also blocking us in https://github.com/kyma-incubator/reconciler/pull/1141

• https://status.build.kyma-project.io/view/gs/kyma-prow-logs/pr-logs/pull/kyma-incubator_reconciler/1141/pre-main-reconciler-cli-integration-kyma-latest-k3d/1554382741867335680
• https://status.build.kyma-project.io/view/gs/kyma-prow-logs/pr-logs/pull/kyma-incubator_reconciler/1141/pre-main-reconciler-cli-kyma-prev-to-last-release-upgrade-k3d/1554382741959610368

[jeremyharisch]

The following pipeline is still failing with the same issues mentioned in this ticket:

• pre-main-reconciler-cli-kyma-prev-to-last-release-upgrade-k3d (link)

[jakobmoellerdev]

@m00g3n could you take another look here?

[adityabhatia]

There has been another failure reported regulary. Seems to me an implementation issue. Could you have a look please @dbadura?

       Logging Tests:
         Istio Access Logs tests
           Should query Loki and verify format of Istio Access Logs:
     TypeError: Cannot read property 'values' of undefined
      at Object.verifyIstioAccessLogFormat (logging/loki.js:57:45)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at async Context.<anonymous> (logging/index.js:29:7)```

[tobiscr]

There has been another failure reported regulary. Seems to me an implementation issue. Could you have a look please @dbadura?

       Logging Tests:
         Istio Access Logs tests
           Should query Loki and verify format of Istio Access Logs:
     TypeError: Cannot read property 'values' of undefined
      at Object.verifyIstioAccessLogFormat (logging/loki.js:57:45)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at async Context.<anonymous> (logging/index.js:29:7)```

Issue found in our pipeline, is fixed with PR https://github.com/kyma-project/test-infra/pull/5932

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale