Hello Eric, or anyone else affected, Accepted sosreport into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sosreport/4.1-1ubuntu0.20.10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: sosreport (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-groovy ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1913583 Title: [plugin][k8s] Canonical Distribution of Kubernetes fixes Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Bionic: New Status in sosreport source package in Focal: Fix Committed Status in sosreport source package in Groovy: Fix Committed Status in sosreport source package in Hirsute: Fix Released Bug description: [Impact] Running sosreport in a CDK deployed environment won't collect as much information as the plugin could, this is because the kubectl calls are using the wrong paths for the kubeconfig files, this prevents from having more detailed sosreports on the state of the cluster which leads to a back and forth running extra commands to collect the rest of the data. [Test Case] * Deploy CDK: juju deploy charmed-kubernetes # https://ubuntu.com/kubernetes/docs/quickstart * ssh into the kubernetes-master/0 * Run sosreport Expected result: The sosreport contains a 'kubernetes' directory where all the commands executed successfully Actual result: The sosreport contains a 'kubernetes' directory where some of the commands contain "Forbidden" errors. find sosreport-*/ -type d -name kubernetes -exec grep -H -i forbidden {} \; [Where problems could occur] Any issues with this SRU should show themselves as failures in the execution of the kubernetes plugin and that can be verified in the sos.log file. [Other Info] Upstream: https://github.com/sosreport/sos/pull/2387 https://github.com/sosreport/sos/pull/2387/commits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913583/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
