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

When deploying Kubo to GCP the worker_node_tag was not applied to worker VMs #162

Closed
d4v3r opened this Issue Aug 16, 2017 · 4 comments

Comments

Projects
None yet
5 participants
@d4v3r

d4v3r commented Aug 16, 2017

This problem surfaced when I could not expose a deployment (make an app accessible).

After reviewing my config (director.yml) I could see that the value for worker_node_tag was not correctly set on the provisioned worker VMs. After adding the tag manually to the VMs, I could expose the deployment.

@cf-gitbot

This comment has been minimized.

Show comment
Hide comment
@cf-gitbot

cf-gitbot Aug 16, 2017

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

cf-gitbot commented Aug 16, 2017

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@making

This comment has been minimized.

Show comment
Hide comment
@making

making Aug 21, 2017

Contributor

I had the same issue with 34e334346a7801c874dede7441466a3ed70d794b . I could access the application using following workarround:

for vm in `gcloud compute instances list --filter labels.job=worker | grep RUNNING | awk '{print $1}'`;do
  gcloud compute instances add-tags $vm --tags ${prefix}bosh-kubo-worker;
done
Contributor

making commented Aug 21, 2017

I had the same issue with 34e334346a7801c874dede7441466a3ed70d794b . I could access the application using following workarround:

for vm in `gcloud compute instances list --filter labels.job=worker | grep RUNNING | awk '{print $1}'`;do
  gcloud compute instances add-tags $vm --tags ${prefix}bosh-kubo-worker;
done
@alex-slynko

This comment has been minimized.

Show comment
Hide comment
@alex-slynko

alex-slynko Aug 28, 2017

Member

We will ask the PMs to prioritise this story.

Member

alex-slynko commented Aug 28, 2017

We will ask the PMs to prioritise this story.

@jhvhs

This comment has been minimized.

Show comment
Hide comment
@jhvhs

jhvhs Nov 8, 2017

Contributor

Worker node tag has been completely removed. The BOSH autogenerated tag is used instead.

Contributor

jhvhs commented Nov 8, 2017

Worker node tag has been completely removed. The BOSH autogenerated tag is used instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment