Skip to content

Conversation

vikaschoudhary16
Copy link

@vikaschoudhary16 vikaschoudhary16 commented Aug 22, 2019

Fixing:

Will rebase this PR once openshift/cluster-api-actuator-pkg#111 gets merged. This PR is further updating cluster-api-pkg-dependencies to 4.1 release

@openshift-ci-robot
Copy link

@vikaschoudhary16: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Use cluster api 4.1

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-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 22, 2019
@vikaschoudhary16 vikaschoudhary16 force-pushed the use-cluster-api-4.1 branch 2 times, most recently from ef96bc6 to 6b76b83 Compare August 23, 2019 12:48
@openshift-ci-robot
Copy link

@vikaschoudhary16: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Use cluster api 4.1

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.

Copy link

@michaelgugino michaelgugino left a comment

Choose a reason for hiding this comment

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

Looks like some dependencies are updated into 4.2 stuff.

Choose a reason for hiding this comment

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

This looks like 4.2 stuff.

@eparis
Copy link
Member

eparis commented Aug 24, 2019

We MUST have a 4.1.z target release bug in the title (of the form Bug NNNNNNN: title title title)
That bug MUST 'depend on' an 4.2 target release bz.
And that 4.2 BZ MUST be VERIFIED by QE.
We also need lgtm and approved from the team after review.

@vikaschoudhary16 vikaschoudhary16 changed the title Use cluster api 4.1 Bug 1732929: Use cluster api 4.1 Aug 26, 2019
@openshift-ci-robot
Copy link

@vikaschoudhary16: This pull request references Bugzilla bug 1732929, which is invalid:

  • expected dependent Bugzilla bug 1733708 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1732929: Use cluster api 4.1

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-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Aug 26, 2019
@vikaschoudhary16
Copy link
Author

We MUST have a 4.1.z target release bug in the title (of the form Bug NNNNNNN: title title title)
That bug MUST 'depend on' an 4.2 target release bz.
And that 4.2 BZ MUST be VERIFIED by QE.
We also need lgtm and approved from the team after review.

Updated. 4.2 bug is "ON_QA" so will wait till that gets "VERIFIED".

@vikaschoudhary16
Copy link
Author

/retest

@openshift-ci-robot
Copy link

@vikaschoudhary16: This pull request references Bugzilla bug 1732929, which is invalid:

  • expected dependent Bugzilla bug 1733708 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1732929: Use cluster api 4.1

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.

@vikaschoudhary16 vikaschoudhary16 changed the title Bug 1732929: Use cluster api 4.1 Bug 1732929: Pin dependencies to 4.1 Aug 27, 2019
@vikaschoudhary16
Copy link
Author

/test e2e-aws-operator

1 similar comment
@vikaschoudhary16
Copy link
Author

/test e2e-aws-operator

@ingvagabund
Copy link
Member

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 28, 2019
@openshift-ci-robot
Copy link

@ingvagabund: This pull request references Bugzilla bug 1732929, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/bugzilla refresh

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.

Use openshift-4.1-cluster-api-0.0.0-alpha.4
Pin cluster-api-actuator-pkg to release-4.1
@ingvagabund
Copy link
Member

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund

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

enxebre commented Sep 16, 2019

/retest

1 similar comment
@knobunc
Copy link

knobunc commented Sep 16, 2019

/retest

@openshift-bot
Copy link

/retest

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

1 similar comment
@openshift-bot
Copy link

/retest

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

@openshift-ci-robot
Copy link

@knobunc: The label(s) /label cherry-pick-approved cannot be appled. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga

In response to this:

/label cherry-pick-approved

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 openshift deleted a comment from openshift-ci-robot Sep 16, 2019
@openshift-bot
Copy link

/retest

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

@knobunc
Copy link

knobunc commented Sep 16, 2019

@vikaschoudhary16 I'm pulling approval for the backport until the tests pass. I tried a few times and I think it's a problem with the PR.

@knobunc knobunc removed the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 16, 2019
@openshift-bot
Copy link

/retest

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

13 similar comments
@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@openshift-bot
Copy link

/retest

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

@ingvagabund
Copy link
Member

@openshift-bot
Copy link

/retest

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

@ingvagabund
Copy link
Member

/retest

@bparees bparees added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 19, 2019
@openshift-merge-robot openshift-merge-robot merged commit 9fe3645 into openshift:release-4.1 Sep 19, 2019
@openshift-ci-robot
Copy link

@vikaschoudhary16: All pull requests linked via external trackers have merged. Bugzilla bug 1732929 has been moved to the MODIFIED state.

In response to this:

Bug 1732929: Pin dependencies to 4.1

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-robot
Copy link

@vikaschoudhary16: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-upgrade d8a62dd link /test e2e-aws-upgrade

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.