Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate config brancher by auto-config-brancher job at Sat, 19 Sep 2020 08:02:54 UTC #12034

Merged

Conversation

openshift-bot
Copy link
Contributor

/cc @ghost

… openshift-priv --only-org openshift --whitelist-file ./core-services/openshift-priv/_whitelist.yaml
@openshift-bot openshift-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 19, 2020
@openshift-ci-robot
Copy link
Contributor

@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: ghost.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @ghost

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-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 19, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

The pull request process is described here

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

1 similar comment
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

The pull request process is described here

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

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/ovirt-csi-driver-operator/release-4.7/e2e-ovirt 0cb6f34 link /test pj-rehearse

Full PR test history. Your PR dashboard.

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 072b95d into openshift:master Sep 19, 2020
@openshift-ci-robot
Copy link
Contributor

@openshift-bot: Updated the following 3 configmaps:

  • ci-operator-4.6-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-priv-bond-cni-release-4.6.yaml using file ci-operator/config/openshift-priv/bond-cni/openshift-priv-bond-cni-release-4.6.yaml
    • key openshift-priv-cluster-api-provider-ovirt-release-4.6.yaml using file ci-operator/config/openshift-priv/cluster-api-provider-ovirt/openshift-priv-cluster-api-provider-ovirt-release-4.6.yaml
    • key openshift-priv-loki-release-4.6.yaml using file ci-operator/config/openshift-priv/loki/openshift-priv-loki-release-4.6.yaml
    • key openshift-priv-node-feature-discovery-release-4.6.yaml using file ci-operator/config/openshift-priv/node-feature-discovery/openshift-priv-node-feature-discovery-release-4.6.yaml
    • key openshift-priv-node-problem-detector-release-4.6.yaml using file ci-operator/config/openshift-priv/node-problem-detector/openshift-priv-node-problem-detector-release-4.6.yaml
    • key openshift-priv-ovirt-csi-driver-operator-release-4.6.yaml using file ci-operator/config/openshift-priv/ovirt-csi-driver-operator/openshift-priv-ovirt-csi-driver-operator-release-4.6.yaml
    • key openshift-bond-cni-release-4.6.yaml using file ci-operator/config/openshift/bond-cni/openshift-bond-cni-release-4.6.yaml
    • key openshift-cluster-api-provider-ovirt-release-4.6.yaml using file ci-operator/config/openshift/cluster-api-provider-ovirt/openshift-cluster-api-provider-ovirt-release-4.6.yaml
    • key openshift-loki-release-4.6.yaml using file ci-operator/config/openshift/loki/openshift-loki-release-4.6.yaml
    • key openshift-node-feature-discovery-release-4.6.yaml using file ci-operator/config/openshift/node-feature-discovery/openshift-node-feature-discovery-release-4.6.yaml
    • key openshift-node-problem-detector-release-4.6.yaml using file ci-operator/config/openshift/node-problem-detector/openshift-node-problem-detector-release-4.6.yaml
    • key openshift-ovirt-csi-driver-operator-release-4.6.yaml using file ci-operator/config/openshift/ovirt-csi-driver-operator/openshift-ovirt-csi-driver-operator-release-4.6.yaml
  • ci-operator-4.7-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-priv-bond-cni-release-4.7.yaml using file ci-operator/config/openshift-priv/bond-cni/openshift-priv-bond-cni-release-4.7.yaml
    • key openshift-priv-cluster-api-provider-ovirt-release-4.7.yaml using file ci-operator/config/openshift-priv/cluster-api-provider-ovirt/openshift-priv-cluster-api-provider-ovirt-release-4.7.yaml
    • key openshift-priv-loki-release-4.7.yaml using file ci-operator/config/openshift-priv/loki/openshift-priv-loki-release-4.7.yaml
    • key openshift-priv-node-feature-discovery-release-4.7.yaml using file ci-operator/config/openshift-priv/node-feature-discovery/openshift-priv-node-feature-discovery-release-4.7.yaml
    • key openshift-priv-node-problem-detector-operator-release-4.7.yaml using file ci-operator/config/openshift-priv/node-problem-detector-operator/openshift-priv-node-problem-detector-operator-release-4.7.yaml
    • key openshift-priv-node-problem-detector-release-4.7.yaml using file ci-operator/config/openshift-priv/node-problem-detector/openshift-priv-node-problem-detector-release-4.7.yaml
    • key openshift-priv-ovirt-csi-driver-operator-release-4.7.yaml using file ci-operator/config/openshift-priv/ovirt-csi-driver-operator/openshift-priv-ovirt-csi-driver-operator-release-4.7.yaml
    • key openshift-bond-cni-release-4.7.yaml using file ci-operator/config/openshift/bond-cni/openshift-bond-cni-release-4.7.yaml
    • key openshift-cluster-api-provider-ovirt-release-4.7.yaml using file ci-operator/config/openshift/cluster-api-provider-ovirt/openshift-cluster-api-provider-ovirt-release-4.7.yaml
    • key openshift-loki-release-4.7.yaml using file ci-operator/config/openshift/loki/openshift-loki-release-4.7.yaml
    • key openshift-node-feature-discovery-release-4.7.yaml using file ci-operator/config/openshift/node-feature-discovery/openshift-node-feature-discovery-release-4.7.yaml
    • key openshift-node-problem-detector-release-4.7.yaml using file ci-operator/config/openshift/node-problem-detector/openshift-node-problem-detector-release-4.7.yaml
    • key openshift-ovirt-csi-driver-operator-release-4.7.yaml using file ci-operator/config/openshift/ovirt-csi-driver-operator/openshift-ovirt-csi-driver-operator-release-4.7.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-priv-node-feature-discovery-master.yaml using file ci-operator/config/openshift-priv/node-feature-discovery/openshift-priv-node-feature-discovery-master.yaml
    • key openshift-priv-ovirt-csi-driver-master.yaml using file ci-operator/config/openshift-priv/ovirt-csi-driver/openshift-priv-ovirt-csi-driver-master.yaml

In response to this:

/cc @ghost

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
3 participants