Skip to content

Commit

Permalink
Add static routes to netConfig to support scenario A
Browse files Browse the repository at this point in the history
Adopting a workload using scenario A (different subnet ranges between
wallaby CP and next-gen CP) wont succeed if netConfig doesn't have the
routes to reach old CP.

Relates: OSPRH-7544
  • Loading branch information
averdagu committed Jan 10, 2025
1 parent a17744c commit 24b9574
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions tests/roles/dataplane_adoption/defaults/main.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,9 @@ netconfig_networks:
start: 172.17.0.100
cidr: 172.17.0.0/24
vlan: 20
routes:
- destination: 172.17.1.0/24

Check failure on line 28 in tests/roles/dataplane_adoption/defaults/main.yaml

View workflow job for this annotation

GitHub Actions / pre-commit

yaml[indentation]

Wrong indentation: expected 10 but found 8
nexthop: 172.17.0.100
- name: External
dnsDomain: external.example.com
subnets:
Expand Down Expand Up @@ -60,6 +63,9 @@ netconfig_networks:
start: 172.19.0.100
cidr: 172.19.0.0/24
vlan: 22
routes:
- destination: 172.19.1.0/24

Check failure on line 67 in tests/roles/dataplane_adoption/defaults/main.yaml

View workflow job for this annotation

GitHub Actions / pre-commit

yaml[indentation]

Wrong indentation: expected 10 but found 8
nexthop: 172.19.0.100
registry_name: "quay.io"
registry_namespace: "podified-antelope-centos9"
image_tag: "current-podified"
Expand Down

0 comments on commit 24b9574

Please sign in to comment.