Skip to content

Conversation

@kwoodson
Copy link
Contributor

@kwoodson kwoodson commented Feb 3, 2022

…sumption

Fix for this issue:
�[36mINFO�[0m[2022-02-03T21:05:42Z] Running step e2e-alibaba-ipi-conf-alibabacloud.
�[36mINFO�[0m[2022-02-03T21:06:12Z] Logs for container test in pod e2e-alibaba-ipi-conf-alibabacloud:
�[36mINFO�[0m[2022-02-03T21:06:12Z] Alibaba region: us-east-1
/bin/bash: line 18: CI_RESOURCE_GROUP_ID: unbound variable
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2022-02-03T21:06:09Z"}
error: failed to execute wrapped command: exit status 1
�[36mINFO�[0m[2022-02-03T21:06:12Z] Step e2e-alibaba-ipi-conf-alibabacloud failed after 30s.

@kwoodson kwoodson requested review from mtulio and rvanderp3 February 3, 2022 21:20
@kwoodson
Copy link
Contributor Author

kwoodson commented Feb 3, 2022

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2022
@kwoodson
Copy link
Contributor Author

kwoodson commented Feb 3, 2022

Let's verify we get a e2e-alibaba to pass the error we are seeing.

@kwoodson
Copy link
Contributor Author

kwoodson commented Feb 3, 2022

/test e2e-alibaba

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2022

@kwoodson: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test app-ci-config-dry
  • /test boskos-config
  • /test boskos-config-generation
  • /test build-clusters
  • /test build01-dry
  • /test build02-dry
  • /test build03-dry
  • /test build04-dry
  • /test ci-operator-config
  • /test ci-operator-config-metadata
  • /test ci-operator-registry
  • /test ci-secret-bootstrap-config-validation
  • /test ci-testgrid-allow-list
  • /test config
  • /test core-valid
  • /test correctly-sharded-config
  • /test deprecate-templates
  • /test generated-config
  • /test generated-dashboards
  • /test hive-dry
  • /test openshift-image-mirror-mappings
  • /test ordered-prow-config
  • /test owners
  • /test pj-rehearse-blocking
  • /test prow-config
  • /test prow-config-filenames
  • /test prow-config-semantics
  • /test pylint
  • /test release-config
  • /test release-controller-config
  • /test secret-generator-config-valid
  • /test services-valid
  • /test step-registry-metadata
  • /test step-registry-shellcheck
  • /test yamllint

The following commands are available to trigger optional jobs:

  • /test arm01-dry
  • /test pj-rehearse
  • /test pj-rehearse-max
  • /test pj-rehearse-more
  • /test sync-rover-groups
  • /test vsphere-dry

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-release-master-build-clusters
  • pull-ci-openshift-release-master-ci-operator-config
  • pull-ci-openshift-release-master-ci-operator-config-metadata
  • pull-ci-openshift-release-master-ci-operator-registry
  • pull-ci-openshift-release-master-config
  • pull-ci-openshift-release-master-core-valid
  • pull-ci-openshift-release-master-correctly-sharded-config
  • pull-ci-openshift-release-master-deprecate-templates
  • pull-ci-openshift-release-master-generated-config
  • pull-ci-openshift-release-master-generated-dashboards
  • pull-ci-openshift-release-master-ordered-prow-config
  • pull-ci-openshift-release-master-owners
  • pull-ci-openshift-release-master-pj-rehearse
  • pull-ci-openshift-release-master-prow-config
  • pull-ci-openshift-release-master-prow-config-filenames
  • pull-ci-openshift-release-master-prow-config-semantics
  • pull-ci-openshift-release-master-release-config
  • pull-ci-openshift-release-master-release-controller-config
  • pull-ci-openshift-release-master-secret-generator-config-valid
  • pull-ci-openshift-release-master-services-valid
  • pull-ci-openshift-release-master-step-registry-metadata
  • pull-ci-openshift-release-master-step-registry-shellcheck
  • pull-ci-openshift-release-openshift-image-mirror-mappings
  • pull-ci-openshift-release-yamllint
Details

In response to this:

/test e2e-alibaba

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2022
Copy link
Contributor

@mtulio mtulio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kwoodson, mtulio

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kwoodson
Copy link
Contributor Author

kwoodson commented Feb 3, 2022

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2022
@kwoodson
Copy link
Contributor Author

kwoodson commented Feb 3, 2022

Tests are failing because of unknown provider error:

E0203 22:20:06.388593     856 test_context.go:503] Unknown provider "alibabacloud". The following providers are known: aws azure baremetal gce gke ibmcloud kubemark kubevirt local openstack ovirt skeleton vsphere

I have merged the new provider here openshift/origin#26782.

I see the code in the 4.10 branch here https://github.com/openshift/origin/blob/release-4.10/cmd/openshift-tests/provider.go#L87

The master branch as well includes the change https://github.com/openshift/origin/blob/master/cmd/openshift-tests/provider.go#L87.

Did we miss a step? @rvanderp3 @mtulio

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2022

@kwoodson: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/pj-rehearse 8bc7085 link false /test pj-rehearse
ci/rehearse/openshift/installer/release-4.11/e2e-alibaba 8bc7085 link unknown /test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit e2ebd8f into openshift:master Feb 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2022

@kwoodson: Updated the step-registry configmap in namespace ci at cluster app.ci using the following files:

  • key ipi-conf-alibabacloud-commands.sh using file ci-operator/step-registry/ipi/conf/alibabacloud/ipi-conf-alibabacloud-commands.sh
Details

In response to this:

…sumption

Fix for this issue:
�[36mINFO�[0m[2022-02-03T21:05:42Z] Running step e2e-alibaba-ipi-conf-alibabacloud.
�[36mINFO�[0m[2022-02-03T21:06:12Z] Logs for container test in pod e2e-alibaba-ipi-conf-alibabacloud:
�[36mINFO�[0m[2022-02-03T21:06:12Z] Alibaba region: us-east-1
/bin/bash: line 18: CI_RESOURCE_GROUP_ID: unbound variable
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2022-02-03T21:06:09Z"}
error: failed to execute wrapped command: exit status 1
�[36mINFO�[0m[2022-02-03T21:06:12Z] Step e2e-alibaba-ipi-conf-alibabacloud failed after 30s.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants