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

Configuring slbs stopped working with 32.0.0 #119

Closed
friegger opened this issue Dec 16, 2020 · 8 comments
Closed

Configuring slbs stopped working with 32.0.0 #119

friegger opened this issue Dec 16, 2020 · 8 comments

Comments

@friegger
Copy link
Contributor

With 32.0.0 using load balancer via VM extension does not work anymore. It works fine with 31.0.0. Potentially this is caused by #115 and/or #114.

Also see docs https://bosh.io/docs/alicloud-cpi/#resource-pools. The formatting is broken by the way.

@chushenmeshile
Copy link
Contributor

@friegger What problems do you encounter with 32.0.0 and why do you think 114 or 115 pr has problems

@shaoyongfeng
Copy link

shaoyongfeng commented Dec 29, 2020

Hi ,
following is a very simple code to reproduce this issue
in cloud config, you define vm_extensions as below
vm_extensions:

  • name: landscape_credhub_lb
    cloud_properties:
    slbs:
    • (( .terraform.credhub_lb_id ))
  • name: landscape_uaa_lb
    cloud_properties:
    slbs:
    • (( .terraform.uaa_lb_id ))
      The lb_ids are the output from terraform of a alicloud_slb resource:
      output "credhub_lb_id" {
      value = alicloud_slb.credhub-lb.id
      }

in your deployment manifest, just use above extension for your VM

  • name: vmname
    instances: ((instancesno))
    vm_type: ((instance_type))
    vm_extensions:
    • landscape_credhub_lb
      stemcell: default

@chushenmeshile
Copy link
Contributor

What are the errors you encountered during deployment

@shaoyongfeng
Copy link

image
the symptom is VM is not attached to LB as above

@chushenmeshile
Copy link
Contributor

I'm sorry, I can't see the image content information, but I think it may be a parameter type conversion error. Maybe you need to convert the parameter type from string to int.

@shaoyongfeng
Copy link

Hi @chushenmeshile
I don't understand what you mean. This issue only happens in new cpi version. there should be some changes in CPI which causes this issue. Do you try to reproduce it?

@chushenmeshile
Copy link
Contributor

The parameter type has changed from string to int, and the default value has been cancelled. Therefore, I think there may be a problem with the data type you passed in the configuration file.

@xiaozhu36
Copy link
Contributor

HI @friegger I am sorry for the late reply. This issue has been fixed by #120 and it has been published in the release v33.0.0. Please have a check.

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

4 participants