juju 3.6.14 is incompatible with the current workflow

[beliaev-maksim]

Bug Description

We need to ensure we run on strictly confined microk8s (or even better switch to Canonical K8s as default option)

name: Integration tests

on:
  pull_request:

jobs:
  integration-tests:
    uses: canonical/operator-workflows/.github/workflows/integration_test.yaml@main
    secrets: inherit
    with:
      juju-channel: 3.6/stable

  /opt/pipx_bin/tox --version
  /usr/bin/sudo snap install juju --channel=3.6/stable
  4.47.3 from /opt/pipx/venvs/tox/lib/python3.12/site-packages/tox/__init__.py
  juju (3.6/stable) 3.6.14 from Canonical** installed
Install tools
/usr/bin/mkdir -p /home/runner/.local/share/juju
Install microk8s
Initialize microk8s
Bootstrap controller
  /usr/bin/sudo -g microk8s -E juju bootstrap --debug --verbose microk8s github-pr-a915d-microk8s --model-default test-mode=true --model-default automatically-retry-hooks=false --model-default logging-config=<root>=DEBUG --bootstrap-constraints=
  09:31:35 INFO  juju.cmd supercommand.go:56 running juju [3.6.14 b08ad63ae633a35dbfda995a757dcf9db4e11160 gc go1.25.6]
  09:31:35 DEBUG juju.cmd supercommand.go:57   args: []string{"/snap/juju/33784/bin/juju", "bootstrap", "--debug", "--verbose", "microk8s", "github-pr-a915d-microk8s", "--model-default", "test-mode=true", "--model-default", "automatically-retry-hooks=false", "--model-default", "logging-config=<root>=DEBUG", "--bootstrap-constraints="}
  09:31:35 DEBUG juju.environs.tools build.go:123 looking for: /snap/juju/33784/bin/juju
  09:31:41 DEBUG juju.environs.tools versionfile.go:54 looking for sha256 71ac48f691402da59c2bc7ffbc5e90f3146c4a0e094cfd4cdf136fe0b53ae029
  ERROR "/var/snap/juju/33784/microk8s/credentials/client.config" does not exist: juju "3.6.14" can only work with strictly confined microk8s
  09:31:41 DEBUG cmd supercommand.go:571 error stack: 
  juju "3.6.14" can only work with strictly confined microk8s
  github.com/juju/juju/internal/provider/kubernetes.getLocalMicroK8sConfig:114: "/var/snap/juju/33784/microk8s/credentials/client.config" does not exist
  github.com/juju/juju/internal/provider/kubernetes.kubernetesEnvironProvider.DetectCloud:58: 
  github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).detectCloud:1330: 
  github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).cloud:1269: 
  github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).Run:750: 
  Error: The process '/usr/bin/sudo' failed with exit code 1

Impact

High (major functionality broken, no workaround)

Impact Rationale

No response

Link to the failing workflow

https://github.com/canonical/roadmap.canonical.com/actions/runs/22663190437/job/65688328375?pr=5

Additional context

No response

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/ISD-5268.

This message was autogenerated

[javierdelapuente]

As a workaround, can you pass the microk8s channel (I do not know why it does not install strict by default):

    with:
      juju-channel: 3.6/stable
      channel: 1.34-strict/stable

Last track for strict strict (1.35-strict) has some changes in the ingress plugin that may break pipelines (I haven't tested it).

If instead you prefer to use k8s, there is support in operator-workflows. This is an example: https://github.com/canonical/haproxy-operator/blob/425c97b0971a8cc92ef8f649faa96a7975ad5672/.github/workflows/integration_test.yaml#L52