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

Fix naming of isolated network if the network name contains an underscore #361

Merged

Conversation

vishesh92
Copy link
Member

@vishesh92 vishesh92 commented May 31, 2024

Issue #, if available:
Fixes #295
Description of changes:
We replace special characters with - for cloudstackisolatednetworks crd resource name.

Testing performed:
Created a cluster with name capc-cluster and network name set as Guest_net-work (Network). A network with name Guest_net-work (Network) was created on ACS and the cloudstackisolatednetworks CRD object was created with the name capc-cluster-guest-net-work-network on k8s.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@vishesh92 vishesh92 added this to the v0.5.0 milestone May 31, 2024
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label May 31, 2024
@k8s-ci-robot k8s-ci-robot requested review from dims and g-gaston May 31, 2024 20:56
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 31, 2024
Copy link

netlify bot commented May 31, 2024

Deploy Preview for kubernetes-sigs-cluster-api-cloudstack ready!

Name Link
🔨 Latest commit bc73be4
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-cluster-api-cloudstack/deploys/665db09bc7022a0008a1c24b
😎 Deploy Preview https://deploy-preview-361--kubernetes-sigs-cluster-api-cloudstack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@vishesh92 vishesh92 removed the request for review from dims May 31, 2024 21:12
@blueorangutan
Copy link

Test Results : (tid-467)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version: v1.27.2
Kubernetes Version upgrade from: v1.26.5
Kubernetes Version upgrade to: v1.27.2
CloudStack Version: 4.19
Template: ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr361-sl-467.zip



Summarizing 2 Failures:
 [FAIL] When testing affinity group [It] Should have host affinity group when affinity is pro
 /jenkins/workspace/capc-e2e-new/test/e2e/common.go:348
 [FAIL] When testing project [AfterEach] Should create a cluster in a project
 /jenkins/workspace/capc-e2e-new/test/e2e/project.go:103

Ran 29 of 30 Specs in 8910.854 seconds
FAIL! -- 27 Passed | 2 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (8910.86s)
FAIL

@vishesh92 vishesh92 force-pushed the fix-network-name-generation branch from 347d21b to 73687b9 Compare June 3, 2024 11:37
@vishesh92 vishesh92 force-pushed the fix-network-name-generation branch from 73687b9 to bc73be4 Compare June 3, 2024 12:01
@blueorangutan
Copy link

Test Results : (tid-469)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version: v1.27.2
Kubernetes Version upgrade from: v1.26.5
Kubernetes Version upgrade to: v1.27.2
CloudStack Version: 4.19
Template: ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr361-sl-469.zip



Summarizing 4 Failures:
 [FAIL] When testing affinity group [It] Should have host affinity group when affinity is pro
 /jenkins/workspace/capc-e2e-new/test/e2e/common.go:348
 [FAIL] When testing resource cleanup [It] Should create a new network when the specified network does not exist
 /root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.4.8/framework/clusterctl/clusterctl_helpers.go:345
 [FAIL] When testing project [AfterEach] Should create a cluster in a project
 /jenkins/workspace/capc-e2e-new/test/e2e/project.go:103
 [FAIL] When testing app deployment to the workload cluster with slow network [ToxiProxy] [It] Should be able to download an HTML from the app deployed to the workload cluster
 /jenkins/workspace/capc-e2e-new/test/e2e/deploy_app_toxi.go:133

Ran 29 of 30 Specs in 10175.296 seconds
FAIL! -- 25 Passed | 4 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (10175.30s)
FAIL

@blueorangutan
Copy link

Test Results : (tid-471)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version: v1.27.2
Kubernetes Version upgrade from: v1.26.5
Kubernetes Version upgrade to: v1.27.2
CloudStack Version: 4.19
Template: ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr361-sl-471.zip



Summarizing 5 Failures:
 [FAIL] When testing project [AfterEach] Should create a cluster in a project
 /jenkins/workspace/capc-e2e-new/test/e2e/project.go:103
 [FAIL] When testing affinity group [It] Should have host affinity group when affinity is pro
 /jenkins/workspace/capc-e2e-new/test/e2e/common.go:348
 [FAIL] When testing node drain timeout [It] A node should be forcefully removed if it cannot be drained in time
 /root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.4.8/framework/deployment_helpers.go:88
 [FAIL] When testing Kubernetes version upgrades [It] Should successfully upgrade kubernetes versions when there is a change in relevant fields
 /root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.4.8/framework/machinedeployment_helpers.go:127
 [TIMEDOUT] When testing subdomain [It] Should create a cluster in a subdomain
 /jenkins/workspace/capc-e2e-new/test/e2e/subdomain.go:60

Ran 29 of 30 Specs in 10818.416 seconds
FAIL! - Suite Timeout Elapsed -- 24 Passed | 5 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (10818.42s)
FAIL

@rohityadavcloud
Copy link
Member

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 4, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rohityadavcloud, vishesh92

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [rohityadavcloud,vishesh92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit d1a6ad9 into kubernetes-sigs:main Jun 4, 2024
10 checks passed
hrak added a commit to Leaseweb/cluster-api-provider-cloudstack that referenced this pull request Jul 10, 2024
hrak added a commit to Leaseweb/cluster-api-provider-cloudstack that referenced this pull request Jul 11, 2024
hrak added a commit to Leaseweb/cluster-api-provider-cloudstack that referenced this pull request Jul 12, 2024
hrak added a commit to Leaseweb/cluster-api-provider-cloudstack that referenced this pull request Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ClusterAPI Provider does not translate existing CS network name into Kubernetes safe name
4 participants