Reading calico-early configuration only loads first node

Bug #2042585 reported by Adam Dyess
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charm Calico Enterprise
Fix Released
Medium
Unassigned

Bug Description

the _early_service_cfg(..) [0] method reads the first node out of the calico-early config and assumes that each host only has the calico-early configuration for itself stored locally. Rather than rely on the first node information, instead look through the calico-early configuration for interfaces which exist on this machine.

[0] https://github.com/charmed-kubernetes/charm-calico-enterprise/blob/5fa828e0fb43ef58093c29a19bd2354b497a239b/src/peer.py#L106

Adam Dyess (addyess)
Changed in charm-calico-enterprise:
milestone: none → 1.29
status: New → Confirmed
Revision history for this message
Peter Jose De Sousa (pjds) wrote :

workaround here is to use bgp_parameters to override. This is confirmed working:

                                                                                                                     │...
Ran 353 of 7207 Specs in 365.374 seconds │...
SUCCESS! -- 353 Passed | 0 Failed | 0 Pending | 6854 Skipped

Revision history for this message
Adam Dyess (addyess) wrote :
Changed in charm-calico-enterprise:
milestone: 1.29 → 1.29+ck1
status: Confirmed → Triaged
importance: Undecided → Medium
Changed in charm-calico-enterprise:
status: Triaged → Fix Committed
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :
Changed in charm-calico-enterprise:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.