Skip to content

Conversation

@droslean
Copy link
Member

@droslean droslean commented Sep 7, 2021

/cc @openshift/test-platform
Signed-off-by: Nikolaos Moraitis [email protected]

@openshift-ci openshift-ci bot requested a review from a team September 7, 2021 09:56
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 7, 2021
@droslean droslean force-pushed the azure-2-release-jobs branch from 61c2b9b to 36137a1 Compare September 7, 2021 10:15
@droslean
Copy link
Member Author

droslean commented Sep 7, 2021

/hold

It needs #21633

@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 Sep 7, 2021
@droslean
Copy link
Member Author

droslean commented Sep 9, 2021

/test pj-rehearse

3 similar comments
@droslean
Copy link
Member Author

droslean commented Sep 9, 2021

/test pj-rehearse

@droslean
Copy link
Member Author

droslean commented Sep 9, 2021

/test pj-rehearse

@droslean
Copy link
Member Author

/test pj-rehearse

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 12, 2021
@droslean
Copy link
Member Author

/test pj-rehearse

@droslean droslean force-pushed the azure-2-release-jobs branch from 36137a1 to 9749dfb Compare September 13, 2021 15:10
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 13, 2021
@droslean
Copy link
Member Author

/test pj-rehearse

1 similar comment
@droslean
Copy link
Member Author

/test pj-rehearse

@droslean droslean changed the title WIP Change the azure release periodic jobs to run on the 2nd subscription Change the azure release periodic jobs to run on the 2nd subscription Sep 16, 2021
@droslean droslean force-pushed the azure-2-release-jobs branch from 9749dfb to da0a936 Compare September 16, 2021 11:51
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 20, 2021
@droslean droslean force-pushed the azure-2-release-jobs branch from da0a936 to 7a8f773 Compare September 20, 2021 13:30
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 20, 2021
@droslean droslean force-pushed the azure-2-release-jobs branch from 7a8f773 to f7f3bd7 Compare September 20, 2021 13:33
@droslean
Copy link
Member Author

/test pj-rehearse

2 similar comments
@droslean
Copy link
Member Author

/test pj-rehearse

@droslean
Copy link
Member Author

/test pj-rehearse

@droslean
Copy link
Member Author

/test pj-rehease

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2021

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

  • /test ci-secret-bootstrap-config-validation
  • /test app-ci-config-dry
  • /test boskos-config
  • /test boskos-config-generation
  • /test build-clusters
  • /test build01-dry
  • /test build02-dry
  • /test ci-operator-config
  • /test ci-operator-config-metadata
  • /test ci-operator-registry
  • /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 ordered-prow-config
  • /test owners
  • /test pj-rehearse-blocking
  • /test prow-config
  • /test prow-config-filenames
  • /test prow-config-semantics
  • /test release-config
  • /test release-controller-config
  • /test secret-generator-config-valid
  • /test services-valid
  • /test step-registry-metadata
  • /test step-registry-shellcheck
  • /test openshift-image-mirror-mappings
  • /test pylint
  • /test yamllint

The following commands are available to trigger optional jobs:

  • /test arm01-dry
  • /test pj-rehearse
  • /test vsphere-dry

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

  • pull-ci-openshift-release-ci-secret-bootstrap-config-validation
  • pull-ci-openshift-release-master-app-ci-config-dry
  • pull-ci-openshift-release-master-arm01-dry
  • pull-ci-openshift-release-master-boskos-config
  • pull-ci-openshift-release-master-boskos-config-generation
  • pull-ci-openshift-release-master-build-clusters
  • pull-ci-openshift-release-master-build01-dry
  • pull-ci-openshift-release-master-build02-dry
  • 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-hive-dry
  • 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-master-vsphere-dry
  • pull-ci-openshift-release-openshift-image-mirror-mappings
  • pull-ci-openshift-release-yamllint
Details

In response to this:

/test pj-rehease

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.

@droslean
Copy link
Member Author

/test pj-rehearse

1 similar comment
@droslean
Copy link
Member Author

droslean commented Oct 1, 2021

/test pj-rehearse

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 1, 2021

@droslean: 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/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-cilium f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.6-e2e-azure-ovn f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-compact-serial f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-compact-serial f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-serial f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-techpreview-serial f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.8-e2e-azure-cilium f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-ovn f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-cilium f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.8-e2e-azure-serial f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-techpreview-serial f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-upgrade f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-compact-upgrade f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-compact-upgrade f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.8-e2e-azure-compact-upgrade f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.6-e2e-azure-upgrade f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-upgrade f7f3bd7 link unknown /test pj-rehearse
ci/prow/pj-rehearse f7f3bd7 link false /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-compact f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-compact f7f3bd7 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-azure-techpreview f7f3bd7 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.

cluster_profile: azure4
cluster_profile: azure-2
env:
BASE_DOMAIN: ci2.azure.devcluster.openshift.com
Copy link
Contributor

Choose a reason for hiding this comment

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

qq: is there a reason i don't see this env change being reflected on any job objects in the other file?

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

@abhinavdahiya If you mean the job yaml file, this env var doesn't have to, because it will be consumed by ci-operator itself.

Copy link
Contributor

Choose a reason for hiding this comment

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

@abhinavdahiya If you mean the job yaml file, this env var doesn't have to, because it will be consumed by ci-operator itself.

Ah, that makes sense then..

@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 1, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 1, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, droslean

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

@droslean
Copy link
Member Author

droslean commented Oct 1, 2021

/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 Oct 1, 2021
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 7895043 into openshift:master Oct 1, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 1, 2021

@droslean: Updated the following 2 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-master__ci-4.10.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.10.yaml
    • key openshift-release-master__ci-4.6.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.6.yaml
    • key openshift-release-master__ci-4.7.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.7.yaml
    • key openshift-release-master__ci-4.8.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.8.yaml
    • key openshift-release-master__ci-4.9.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.9.yaml
  • job-config-master configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-master-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml
Details

In response to this:

/cc @openshift/test-platform
Signed-off-by: Nikolaos Moraitis [email protected]

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.

@droslean droslean deleted the azure-2-release-jobs branch October 1, 2021 22:24
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.

4 participants