WIP: Make test change to nodeup

[justinsb]

Do not merge; checking if pull-kops-e2e-cni-cilium-ipv6 passes on main branch

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from justinsb by writing /assign @justinsb in a comment. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[justinsb]

/test pull-kops-e2e-cni-cilium-ipv6

[justinsb]

/test pull-kops-e2e-cni-cilium-ipv6

[justinsb]

Something weird is happening here; at least on my test account the ipv6-only nodes are stuck in pending state. I can launch an instance manually with similar/identical configurations and it will also be stuck in pending. If I do a similar/identical configuration without the IAM instance profile, it does launch.

[justinsb]

Tweaked this dummy PR to print the instance state and indeed:

I0129 06:31:56.730237   39340 toolbox_dump.go:202] instance "i-00efbf1422afb8d1b" has state "pending"
I0129 06:31:56.731469   39340 toolbox_dump.go:202] instance "i-06691f19b34754536" has state "pending"
I0129 06:31:56.731485   39340 toolbox_dump.go:202] instance "i-06afcb8e1d5cff60c" has state "pending"
I0129 06:31:56.731501   39340 toolbox_dump.go:202] instance "i-06e7db7bd73b7668e" has state "pending"
I0129 06:31:56.731515   39340 toolbox_dump.go:202] instance "i-095e5855974d4be84" has state "running"
I0129 06:31:56.731529   39340 toolbox_dump.go:202] instance "i-0a7227efa7b2a83f9" has state "running"

[justinsb]

/test pull-kops-e2e-cni-cilium-ipv6

[justinsb]

Trying a revert of 716a420 , because that coincides with https://testgrid.k8s.io/kops-ipv6#kops-aws-cni-cilium-ipv6 starting to fail, but I think this is likely an AWS issue.

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-cni-cilium-ipv6	4eb9ec5	link	false	/test pull-kops-e2e-cni-cilium-ipv6

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.

[k8s-ci-robot]

PR needs rebase.

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.