Skip to content

Conversation

chiragkyal
Copy link
Member

@chiragkyal chiragkyal commented Aug 12, 2024

Description of the change:

  • Update openshift/release/ansible/requirements.yml file to use community.docker 3.10.3
  • Run openshift/release/ansible/update-collections.sh script to update the vendored collections

Motivation for the change:

Signed-off-by: chiragkyal <ckyal@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 12, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 12, 2024

@chiragkyal: This pull request references CFE-1100 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Description of the change:

Motivation for the change:

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

openshift-ci bot commented Aug 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chiragkyal

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 12, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 13, 2024

@chiragkyal: This pull request references CFE-1100 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Description of the change:

  • Update openshift/release/ansible/requirements.yml file to use community.docker 3.10.3
  • Run openshift/release/ansible/update-collections.sh script to update the vendored collections

Motivation for the change:

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 openshift-eng/jira-lifecycle-plugin repository.

@chiragkyal
Copy link
Member Author

/assign @arkadeepsen @TrilokGeer

@chiragkyal
Copy link
Member Author

/test images

@chiragkyal
Copy link
Member Author

/hold
for testing with the downstream image

@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 Aug 13, 2024
@arkadeepsen
Copy link
Member

arkadeepsen commented Aug 13, 2024

/retitle CFE-1110: UPSTREAM: : Bump community.docker to 3.10.3

@openshift-ci openshift-ci bot changed the title CFE-1100: UPSTREAM: <carry>: Bump community.docker to 3.10.3 CFE-1110: UPSTREAM: <carry>: Bump community.docker to 3.10.3 Aug 13, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 13, 2024

@chiragkyal: This pull request references CFE-1110 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.18.0" version, but no target version was set.

In response to this:

Description of the change:

  • Update openshift/release/ansible/requirements.yml file to use community.docker 3.10.3
  • Run openshift/release/ansible/update-collections.sh script to update the vendored collections

Motivation for the change:

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 openshift-eng/jira-lifecycle-plugin repository.

@chiragkyal
Copy link
Member Author

/unhold
e2e test passed locally

@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 Aug 14, 2024
@chiragkyal
Copy link
Member Author

/hold
putting a hold, until #11 is finalized

@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 Aug 14, 2024
@arkadeepsen
Copy link
Member

/remove-approve

@arkadeepsen
Copy link
Member

/approve cancel

@TrilokGeer
Copy link
Contributor

/override e2e-ansible

Copy link

openshift-ci bot commented Aug 21, 2024

@TrilokGeer: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • e2e-ansible

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-ansible
  • ci/prow/images
  • ci/prow/sanity
  • ci/prow/unit
  • pull-ci-openshift-ansible-operator-plugins-main-images
  • pull-ci-openshift-ansible-operator-plugins-main-sanity
  • pull-ci-openshift-ansible-operator-plugins-main-unit
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override e2e-ansible

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-sigs/prow repository.

@TrilokGeer
Copy link
Contributor

/override ci/prow/e2e-ansible

Copy link

openshift-ci bot commented Aug 21, 2024

@TrilokGeer: Overrode contexts on behalf of TrilokGeer: ci/prow/e2e-ansible

In response to this:

/override ci/prow/e2e-ansible

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-sigs/prow repository.

Copy link

openshift-ci bot commented Aug 21, 2024

@chiragkyal: all tests passed!

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

@arkadeepsen
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2024
@arkadeepsen
Copy link
Member

@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 Aug 21, 2024
@chiragkyal
Copy link
Member Author

/cc @KeenonLee
for QE label

@openshift-ci openshift-ci bot requested a review from KeenonLee August 21, 2024 18:37
Copy link
Member

@KeenonLee KeenonLee left a comment

Choose a reason for hiding this comment

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

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Aug 22, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 22, 2024

@chiragkyal: This pull request references CFE-1110 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.18.0" version, but no target version was set.

In response to this:

Description of the change:

  • Update openshift/release/ansible/requirements.yml file to use community.docker 3.10.3
  • Run openshift/release/ansible/update-collections.sh script to update the vendored collections

Motivation for the change:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 2624a32 into openshift:main Aug 22, 2024
@arkadeepsen
Copy link
Member

/cherrypick release-4.17

@openshift-cherrypick-robot
Copy link
Contributor

@arkadeepsen: Failed to get PR patch from GitHub. This PR will need to be manually cherrypicked.

Error messagestatus code 406 not one of [200], body: {"message":"Sorry, the diff exceeded the maximum number of files (300). Consider using 'List pull requests files' API or locally cloning the repository instead.","errors":[{"resource":"PullRequest","field":"diff","code":"too_large"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#list-pull-requests-files","status":"406"}

In response to this:

/cherrypick release-4.17

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-sigs/prow repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-ansible-operator
This PR has been included in build openshift-enterprise-ansible-operator-container-v4.18.0-202408220316.p0.g2624a32.assembly.stream.el8.
All builds following this will include this PR.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants