Skip to content
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

Error while executing juju bootstrap microk8s: juju "3.3.1" can only work with strictly confined microk8s #70

Open
bobadair opened this issue Feb 23, 2024 · 1 comment

Comments

@bobadair
Copy link

Hi. In the "Bootstrap controller" step I'm getting the error:
ERROR "/var/snap/juju/25912/microk8s/credentials/client.config" does not exist: juju "3.3.1" can only work with strictly confined microk8s

Here is the related step from the action:

       - name: Setup operator environment
        uses: charmed-kubernetes/actions-operator@main
        with:
          provider: microk8s

The full section of the log is:

Bootstrap controller
  /usr/bin/sg microk8s -c juju bootstrap --debug --verbose microk8s github-pr-ede0d-microk8s --model-default test-mode=true --model-default automatically-retry-hooks=false --model-default logging-config="<root>=DEBUG"  --bootstrap-constraints=""
  01:12:56 INFO  juju.cmd supercommand.go:56 running juju [3.3.1 92a5cac53c51249b21ae0905710625725b4defe9 gc go1.21.5]
  01:12:56 DEBUG juju.cmd supercommand.go:57   args: []string{"/snap/juju/25912/bin/juju", "bootstrap", "--debug", "--verbose", "microk8s", "github-pr-ede0d-microk8s", "--model-default", "test-mode=true", "--model-default", "automatically-retry-hooks=false", "--model-default", "logging-config=<root>=DEBUG", "--bootstrap-constraints="}
  01:12:56 DEBUG juju.environs.tools build.go:123 looking for: /snap/juju/25912/bin/juju
  01:12:59 DEBUG juju.environs.tools versionfile.go:54 looking for sha256 8879a099e75efa81dc6a2abf1c1c80aea8d4804b9665cb664c9ea6ea7a0410a4
  ERROR "/var/snap/juju/25912/microk8s/credentials/client.config" does not exist: juju "3.3.1" can only work with strictly confined microk8s
  01:12:59 DEBUG cmd supercommand.go:549 error stack: 
  juju "3.3.1" can only work with strictly confined microk8s
  github.com/juju/juju/caas/kubernetes/provider.getLocalMicroK8sConfig:114: "/var/snap/juju/25912/microk8s/credentials/client.config" does not exist
  github.com/juju/juju/caas/kubernetes/provider.kubernetesEnvironProvider.DetectCloud:58: 
  github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).detectCloud:1287: 
  github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).cloud:1226: 
  github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).Run:708: 
  Error: The process '/usr/bin/sg' failed with exit code 1

You can see it in situ here: https://github.com/catalogicsoftware/cloudcasa-charm/actions/runs/7982420569/job/21795912102?pr=6

I'd suspect something set up wrong in my environment, but I don't really see anything obvious.

@addyess
Copy link
Member

addyess commented Sep 20, 2024

@bobadair i happened across your situation here and wondered if you found that you can specify the strict version of microk8s here? juju 3.3 and beyond (i recommend using 3/stable) needs a strict channel version of microk8s

   with:
      provider: microk8s
      channel: 1.31-strict/stable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants