-
Notifications
You must be signed in to change notification settings - Fork 345
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
Default installation way - problem with installing sonobuoy using go get #941
Comments
May this be related to this change in dependency handling: #935 ? |
Same issue here via offical getting started docs: |
Thanks for reporting this and providing the script to reproduce the issue, @DamianKusz! In general, we do recommend using the latest binary release: https://github.com/vmware-tanzu/sonobuoy/releases/tag/v0.16.1. Either @johnSchnake or I will take a look at this today to fix the issue. Thanks for your patience! |
I think we should (1) change our README to just download the most recent release. I'll update the README accordingly. I agree with @ttarczynski that this has to do with the change to go mod. Using |
Go get has a number of issues with it since it requires go, grabs master instead of a release, builds using the local go settings/version, etc. We'd like to just show people how to download a release in a terminal. Fixes #941 Signed-off-by: John Schnake <[email protected]>
I just treated this as a documentation issue. I provided an example of how to download/use a release. This way:
|
Hello, yesterday I reported an issue #939 . 2 hours before the issue was closed I ran commands as specified in docs - I put them in a script:
and it worked!
Today I was trying to upgrade another cluster (and after this on the cluster I tested day earlier) and after doing steps described above, script exits with errors during executing go get command and with exit code in bash = "1"(output placed below). After second execution of script, go get command ends and exits the script without any notification about errors or exit codes printed on the screen (output placed below). I checked it on the other cluster and the go get exit code to the shell is equal "2".
If I try to run the script again on the same node (after exiting without error shown), the output is different, but doesn't say much for me (output below).
What did you expect to happen:
Could you please recommend me the steps to use the stable and fresh version of sonobuoy? As far as I understood @johnSchnake comment it is not your desired way of using sonobuoy.
Output of script during first run
Output of script during second run
Output of script during third and subsequent runs
Environment:
kubectl version
): 1.15.4, 1.14.5/etc/os-release
): CentOS Linux release 7.5.1804 (Core)The text was updated successfully, but these errors were encountered: