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] v0.8.3 panicking error #704

Merged
merged 1 commit into from
Nov 1, 2021
Merged

[FIX] v0.8.3 panicking error #704

merged 1 commit into from
Nov 1, 2021

Conversation

kuritka
Copy link
Collaborator

@kuritka kuritka commented Oct 27, 2021

thx to @jkremser , @k0da
Fixing panicking error, the object was not properly initialized and nil returned.

Signed-off-by: kuritka [email protected]

Fixing panicking error, the object was not properly initialized and nil returned.

Signed-off-by: kuritka <[email protected]>
@k0da
Copy link
Collaborator

k0da commented Oct 27, 2021

@kuritka please hold on, I'll test it on real cluster

@ytsarev
Copy link
Member

ytsarev commented Nov 1, 2021

@kuritka looks like it is ready for the merge?

@kuritka
Copy link
Collaborator Author

kuritka commented Nov 1, 2021

@ytsarev , from my POW yes, @k0da asked me to postpone because of testing branch.
@k0da , WDYT ?

@k0da
Copy link
Collaborator

k0da commented Nov 1, 2021

Looks good, but I wasn't able to realize infoblox connection failure. Might be related to INFOBLOX secret rename

@kuritka kuritka merged commit c0bfaff into master Nov 1, 2021
@kuritka kuritka deleted the FIX-panicking-error branch November 1, 2021 11:16
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.

5 participants