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

Provisioning K8s HEAD and Stable v1.12.2 failing on Packet #175

Closed
lixuna opened this issue Nov 1, 2018 · 1 comment
Closed

Provisioning K8s HEAD and Stable v1.12.2 failing on Packet #175

lixuna opened this issue Nov 1, 2018 · 1 comment

Comments

@lixuna
Copy link
Contributor

lixuna commented Nov 1, 2018

Problem:

  • provisioning K8s HEAD and Stable v1.12.2 failing on Packet

Projects affected:

  • Kubernetes

Providers affected:

  • Packet

Failing Stage:

  • provisioning

Failing jobs:

Error logs:

Error: Error applying plan:

3 error(s) occurred:

* module.master.packet_device.masters[0]: 1 error(s) occurred:

* packet_device.masters.0: provisioning time limit exceeded; the Packet team will investigate
* module.master.packet_device.masters[1]: 1 error(s) occurred:

* packet_device.masters.1: provisioning time limit exceeded; the Packet team will investigate
* module.master.packet_device.masters[2]: 1 error(s) occurred:

* packet_device.masters.2: provisioning time limit exceeded; the Packet team will investigate

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.



real    27m28.548s
user    0m12.564s
sys 0m3.680s
Uploading artifacts...
./data/: found 8 matching files                    
Uploading artifacts to coordinator... ok            id=112330 responseStatus=201 Created token=jbEWumUM
ERROR: Job failed: exit code 1

Screenshot:

screenshot 2018-11-01 15 08 13

@lixuna
Copy link
Contributor Author

lixuna commented Nov 1, 2018

Possibly related to #171

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant