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.

Sign up for GitHub

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

Jump to bottom

User reported issue with (their) us-east-1b & us-east-1c #382

Closed
justinsb opened this issue Aug 29, 2016 · 11 comments
Closed

User reported issue with (their) us-east-1b & us-east-1c #382

justinsb opened this issue Aug 29, 2016 · 11 comments
Assignees
@krisnova
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
1.5.2

Comments

@justinsb
Copy link
Member

Apparently some accounts can't run ELBs in us-east-1b and us-east-1c

When launching a ELB in K8s, Error creating load balancer (will retry): Failed to create load balancer for service default/servicename: ValidationError: The requested Availability Zone us-east-1b is constrained and cannot be used together with us-east-1c. Please retry your request by not choosing us-east-1b and us-east-1c together.
@justinsb justinsb modified the milestone: 1.3.0 Sep 6, 2016
@chrislovecnm
Copy link
Contributor

Didn't you fix this?

@justinsb
Copy link
Member Author

No, this is a really weird AWS issue that I've only seen on that one account.

@krisnova
Copy link
Contributor

Is this a kops issue? Maybe we note it in FAQ / Troubleshooting and close the issue?

Maybe open an issue w/ AWS and point the two?

Ideas...?

@chrislovecnm
Copy link
Contributor

I think we need to close

@krisnova krisnova mentioned this issue Oct 28, 2016
Closed
@krisnova krisnova assigned krisnova and unassigned justinsb Oct 28, 2016
@justinsb
Copy link
Member Author

We can move to kubernetes/kubernetes, but let's not close.

Correct mitigation will probably be a warning at deployment time. Once you have a cluster up and running, it's too late.

@brandoncole
Copy link

brandoncole commented Dec 2, 2016 •
edited
Loading

I have few different AWS accounts, and the availability of us-east-1b and us-east-1c seem to be inconsistent. Shown below are zone availabilities from the 2 different accounts FWIW.

image

@krisnova
Copy link
Contributor

krisnova commented Dec 2, 2016

@brandoncole this is a great point! I would imagine this might have something to do with the discrepancy we see here.

@chrislovecnm and @justinsb - just wondering why this is pegged for 1.4.2? Do we have replication steps - or at least an idea of what to do here?

@justinsb justinsb modified the milestones: 1.4.4, 1.5.0, 1.5.1 Dec 28, 2016
@wjordan
Copy link

wjordan commented Mar 19, 2017

I have few different AWS accounts, and the availability of us-east-1b and us-east-1c seem to be inconsistent.

Just thought I'd point out that availability zone inconsistency across accounts is expected behavior, as documented in the Availability Zones section of the EC2 documentation:

An Availability Zone is represented by a region code followed by a letter identifier; for example, us-east-1a. To ensure that resources are distributed across the Availability Zones for a region, we independently map Availability Zones to identifiers for each account. For example, your Availability Zone us-east-1a might not be the same location as us-east-1a for another account. There's no way for you to coordinate Availability Zones between accounts.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 22, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 21, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

justinsb added a commit to justinsb/kops that referenced this issue Dec 9, 2020
@justinsb
Update etcd-manager to 20201209
dc48ca6 
Highlights:

* Fix arm64 images, which were built with an incorrect base image.
* Initial (experimental) Azure support

Full change list:

* Update Kops dependency for Azure Blob Storage support [kubernetes#372](kopeio/etcd-manager#372)
* Exclude gazelle from tools/deb-tools [kubernetes#373](kopeio/etcd-manager#373)
* Regenerate bazel in tools/deb-tools [kubernetes#374](kopeio/etcd-manager#374)
* Release notes for 3.0.20201202 [kubernetes#375](kopeio/etcd-manager#375)
* Remove travis CI [kubernetes#377](kopeio/etcd-manager#377)
* Fix vendor generation for tools/deb-tools subproject [kubernetes#376](kopeio/etcd-manager#376)
* Add script to verify image hashes [kubernetes#380](kopeio/etcd-manager#380)
* Fix some incorrect base image hashes for arm64 [kubernetes#379](kopeio/etcd-manager#379)
* Support Azure [kubernetes#378](kopeio/etcd-manager#378)
* Add more descriptions to wait loops [kubernetes#383](kopeio/etcd-manager#383)
* Rename fields in the azure client struct [kubernetes#382](kopeio/etcd-manager#382)
* Fix small typo in code comment [kubernetes#381](kopeio/etcd-manager#381)
hakman pushed a commit to hakman/kops that referenced this issue Dec 9, 2020
@justinsb
Update etcd-manager to 20201209
c3ca2ac 
Highlights:

* Fix arm64 images, which were built with an incorrect base image.
* Initial (experimental) Azure support

Full change list:

* Update Kops dependency for Azure Blob Storage support [kubernetes#372](kopeio/etcd-manager#372)
* Exclude gazelle from tools/deb-tools [kubernetes#373](kopeio/etcd-manager#373)
* Regenerate bazel in tools/deb-tools [kubernetes#374](kopeio/etcd-manager#374)
* Release notes for 3.0.20201202 [kubernetes#375](kopeio/etcd-manager#375)
* Remove travis CI [kubernetes#377](kopeio/etcd-manager#377)
* Fix vendor generation for tools/deb-tools subproject [kubernetes#376](kopeio/etcd-manager#376)
* Add script to verify image hashes [kubernetes#380](kopeio/etcd-manager#380)
* Fix some incorrect base image hashes for arm64 [kubernetes#379](kopeio/etcd-manager#379)
* Support Azure [kubernetes#378](kopeio/etcd-manager#378)
* Add more descriptions to wait loops [kubernetes#383](kopeio/etcd-manager#383)
* Rename fields in the azure client struct [kubernetes#382](kopeio/etcd-manager#382)
* Fix small typo in code comment [kubernetes#381](kopeio/etcd-manager#381)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@krisnova krisnova

Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
1.5.2
Development

Successfully merging a pull request may close this issue.

Adding troubleshooting documentation DualSpark/kops
7 participants
@wjordan @justinsb @chrislovecnm @brandoncole @krisnova @k8s-ci-robot @fejta-bot