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

Give a proper error when misusing OPENSHIFT_INSTALL_AZURE_EMULATE_SINGLESTACK_IPV6 #3172

Conversation

danwinship
Copy link
Contributor

If you set OPENSHIFT_INSTALL_AZURE_EMULATE_SINGLESTACK_IPV6=true but accidentally pass an IPv4 config, the install will fail with:

ERROR                                              
ERROR Error: Insufficient record blocks            
ERROR                                              
ERROR   on  line 0:                                
ERROR   (source code not available)                
ERROR                                              
ERROR At least 1 "record" blocks are required.     
ERROR                                              
ERROR Failed to read tfstate: open /tmp/openshift-install-151306092/terraform.tfstate:
no such file or directory 
FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create
cluster: failed to apply using Terraform 

If you pass an IPv6-only install-config it will fail with an even uglier error.

This PR fixes it to instead fail in both cases with:

FATAL failed to fetch Terraform Variables: failed to generate asset "Terraform
Variables": failed to get azure Terraform variables:
OPENSHIFT_INSTALL_AZURE_EMULATE_SINGLESTACK_IPV6 requires a dual-stack install-config 

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 24, 2020
@dcbw
Copy link
Contributor

dcbw commented Mar 3, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2020
Copy link
Contributor

@patrickdillon patrickdillon left a comment

Choose a reason for hiding this comment

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

We need this, but I think it should live in install-config/platform validation. Perhaps somewhere around here: https://github.com/openshift/installer/blob/master/pkg/types/validation/installconfig.go#L173

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2020
@danwinship
Copy link
Contributor Author

@patrickdillon ah, indeed. Done.

@danwinship
Copy link
Contributor Author

/retest

1 similar comment
@danwinship
Copy link
Contributor Author

/retest

@patrickdillon
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2020
@patrickdillon
Copy link
Contributor

/assign @abhinavdahiya

Needs approve

@abhinavdahiya
Copy link
Contributor

/approve

/skip

/test e2e-azure

@abhinavdahiya abhinavdahiya added the version/4.6 Tracking changes that should end up in 4.6 release label May 8, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya

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 May 8, 2020
@openshift-bot
Copy link
Contributor

/retest

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

7 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 3, 2020

@danwinship: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-libvirt 4a9769f link /test e2e-libvirt
ci/prow/e2e-aws-fips 4a9769f link /test e2e-aws-fips

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.

@openshift-bot
Copy link
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 05dc9d6 into openshift:master Jun 4, 2020
@danwinship danwinship deleted the emulate-single-stack-error branch June 8, 2020 14:50
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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. version/4.6 Tracking changes that should end up in 4.6 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants