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.

Sign up for GitHub

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

sdn: miscellaneous fixes after the CNI merge #11613

Merged
merged 5 commits into from
Nov 2, 2016
Merged

sdn: miscellaneous fixes after the CNI merge #11613

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d861f06
sdn: start pod manager before trying to update if VNIDs have changed
dcbw Oct 27, 2016
75252d7
sdn: wait for kubelet network plugin init before processing pods
dcbw Oct 27, 2016
500af6b
sdn: run pod manager server forever
dcbw Oct 28, 2016
162c0be
sdn: fix network-already-set-up detection
dcbw Oct 28, 2016
a311f01
dind: make /run a shared mount
dcbw Nov 1, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions pkg/sdn/plugin/node.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,9 @@ func (node *OsdnNode) Start() error {
if err != nil {
return err
}
if err := node.podManager.Start(cniserver.CNIServerSocketPath); err != nil {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the listener always ready once this returns?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, processCNIRequests() will be running in a goroutine at this point, handling subsequent requests from UpdatePod and kubelet.

But there's one more part to this bug that I'll push as a second commit and get another round of LGTM. @DirectXMan12 found the issues yesterday when running a combined process master and node that this PR should fix.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the listener established synchronously before the goroutine is spawned?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup, found l, err := net.Listen("unix", s.path) in CNIServer#Start before the Serve goroutine is kicked off

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if go s.Serve(l) returns an error, nothing will log/handle/restart/exit... if it panics, the process will exit. Do we need to put handling around the Serve call inside the goroutine?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@liggitt in this specific case, the CNI listener/server isn't actually in the hot path, since the Update request that this PR fixes doesn't go through the listener. We just need to make sure that processCNIRequests() is running.

return err
}

if networkChanged {
var pods []kapi.Pod
Expand All @@ -223,10 +226,6 @@ func (node *OsdnNode) Start() error {
}
}

if err := node.podManager.Start(cniserver.CNIServerSocketPath); err != nil {
return err
}

node.markPodNetworkReady()

return nil
Expand Down