When attempting to run "DKP upgrade kommander" from certain versions to version 2.3.2, you might encounter failure output that resembles the following:
✓ Ensuring upgrading conditions are met
⠊⠁ Ensuring application definitions are updated panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x20fab82]
goroutine 1 [running]:
github.com/mesosphere/kommander-cli/v2/pkg/git/utils.CopyDirectoryToRepo.func1({0x29c5995, 0x1e}, {0x0, 0x0}, {0xc000054080?, 0xc001745920?})
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/git/utils/utils.go:94 +0x82
io/fs.WalkDir({0x2f36a00, 0x2f73b40}, {0x29c5995, 0x1e}, 0xc0012ab470)
io/fs/walk.go:112 +0x6a
github.com/mesosphere/kommander-cli/v2/pkg/git/utils.CopyDirectoryToRepo({0x2f36a00?, 0x2f73b40?}, {0x29c5995?, 0x2f55510?}, {0x2f5fce8?, 0xc00099e460?})
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/git/utils/utils.go:93 +0x8c
github.com/mesosphere/kommander-cli/v2/pkg/upgrade.(*AppRepoUpdater).Run.func3({0x2f5fce8, 0xc00099e460})
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/upgrade/app_repo_updater.go:172 +0x172
github.com/mesosphere/kommander-cli/v2/pkg/git/utils.CommitFilesToGitRepo({0xc000648cf0, 0x2f}, {0xc000ce9fe1?, 0x459bd6?}, {0xc000ffa100?, 0x22e?}, {0xc000f3a000?, 0xc000ce9fe1?, 0x9?}, {0x2a0855f, ...}, ...)
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/git/utils/utils.go:65 +0x2e2
github.com/mesosphere/kommander-cli/v2/pkg/upgrade.(*AppRepoUpdater).Run(0xc000139188, {0x2f55548?, 0xc000339860}, 0xc000a360e0)
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/upgrade/app_repo_updater.go:161 +0xb25
github.com/mesosphere/kommander-cli/v2/pkg/runner.(*Execution).run(0xc0012abb08, {0x2f55548, 0xc000339860}, {0x2f3d430, 0xc000139188})
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/runner/execution.go:84 +0x414
github.com/mesosphere/kommander-cli/v2/pkg/runner.(*Execution).FilterAndRun(0x2557a20?, {0x2f55548, 0xc000339860}, 0xc0012abb20, 0x2f27d04?, {0xc000936c60?, 0x11, 0x28?})
github.com/mesosphere/kommander-cli/v2@v2.3.2/pkg/runner/execution.go:68 +0x107
github.com/mesosphere/kommander-cli/v2/cmd/upgrade/kommander.(*Command).Run(0xc000b318c0, 0x0?, {0x0?, 0x0?, 0x0?})
github.com/mesosphere/kommander-cli/v2@v2.3.2/cmd/upgrade/kommander/kommander.go:97 +0x5ef
github.com/spf13/cobra.(*Command).execute(0xc00053d500, {0xc00056fdf0, 0x1, 0x1})
github.com/spf13/cobra@v1.6.1/command.go:916 +0x862
github.com/spf13/cobra.(*Command).ExecuteC(0xc0008d5200)
github.com/spf13/cobra@v1.6.1/command.go:1044 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
github.com/spf13/cobra@v1.6.1/command.go:968
github.com/mesosphere/kommander-cli/v2/cmd.Execute()
github.com/mesosphere/kommander-cli/v2@v2.3.2/cmd/root.go:89 +0x55
main.main()
github.com/mesosphere/kommander-cli/v2@v2.3.2/main.go:8 +0x17
This is related to a known issue in the DKP 2.3.2 binary that will be addressed in future releases of 2.3.
The suggested workaround, if this issue is encountered, is to instead upgrade to DKP 2.3.1 in the meantime.