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

Nodes can not be initialized by packet CCM #750

Closed
kron4eg opened this issue Dec 3, 2019 · 0 comments · Fixed by #884
Closed

Nodes can not be initialized by packet CCM #750

kron4eg opened this issue Dec 3, 2019 · 0 comments · Fixed by #884
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/normal Not that urgent, but is important
Milestone

Comments

@kron4eg
Copy link
Member

kron4eg commented Dec 3, 2019

Packet CCM logging errors:

ERROR: logging before flag.Parse: E1203 13:36:21.266478       1 node_controller.go:417] NodeAddress: Error fetching by providerID: providerID cannot be empty string Error fetching by NodeName: instance not found
@kron4eg kron4eg added the kind/bug Categorizes issue or PR as related to a bug. label Dec 3, 2019
@kron4eg kron4eg added this to the v0.11 milestone Dec 3, 2019
@xmudrii xmudrii modified the milestones: v0.11, v0.12 Mar 6, 2020
@kdomanski kdomanski added the priority/normal Not that urgent, but is important label Mar 26, 2020
@kron4eg kron4eg removed this from the v0.12 milestone Mar 27, 2020
@xmudrii xmudrii added this to the v1.0 milestone Apr 3, 2020
@xmudrii xmudrii self-assigned this Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/normal Not that urgent, but is important
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants