sts-sponsors team mailing list archive

[Felipe Reyes <1913583@xxxxxxxxxxxxxxxxxx>]

On Sat, 2021-02-06 at 16:01 +0000, Eric Desrochers wrote:
> @freyes,
> 
> Can you please fill the SRU template ? And I'll proceed with the
> sponsoring along with all the other patches waiting for SRU.

done ;-)


** Description changed:

+ [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

-- 
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:
  New
Status in sosreport source package in Groovy:
  New
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