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 SEGFAULT issue when buildmgr failed to update package #635

Merged
merged 2 commits into from Apr 21, 2018

Conversation

life1347
Copy link
Member

@life1347 life1347 commented Apr 19, 2018

This is the follow-up PR to PR #626 . Looks like the issue was not really fixed last time...
Test this PR locally and confirm the problem solved.


This change is Reviewable

@@ -131,12 +131,12 @@ func updatePackage(fissionClient *crd.FissionClient,
}

// update package spec
pkg, err := fissionClient.Packages(metav1.NamespaceDefault).Update(pkg)
Copy link
Member

Choose a reason for hiding this comment

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

Why is this necessary? I must be missing something but it looks like it doesn't really change anything...

Copy link
Member Author

Choose a reason for hiding this comment

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

No, this is not necessary. I can rollback to previous version.

@@ -88,7 +88,7 @@ func (pkgw *packageWatcher) build(buildCache *cache.Cache, srcpkg *crd.Package)
if err != nil {
e := fmt.Sprintf("Error setting package pending state: %v", err)
log.Println(e)
updatePackage(pkgw.fissionClient, pkg, fission.BuildStatusFailed, e, nil)
Copy link
Member

Choose a reason for hiding this comment

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

This makes sense.

@soamvasani
Copy link
Member

LGTM, thanks.

@life1347 life1347 merged commit 2d359f8 into master Apr 21, 2018
@life1347 life1347 deleted the fix-buildmgr-segfault-follow-up branch April 21, 2018 15:17
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

Successfully merging this pull request may close these issues.

None yet

2 participants