Juju fails on deploy with error cloud service not found for microk8s

[Camille Rodriguez]

With the latest edge bundle (2.8-beta1-eoan-amd64), juju is unable to deploy a charm on microk8s. It prints out an error regarding a cloud service not found.

crodriguez@camille-hp:~/PycharmProjects/mssql-project/charm-mssql$ juju deploy .
ERROR cloud service a#0de04db5-248d-470d-884e-0e4bde6405ee not found (not found)
crodriguez@camille-hp:~/PycharmProjects/mssql-project/charm-mssql$ juju deploy . --debug
16:45:18 INFO juju.cmd supercommand.go:91 running juju [2.8-beta1 3436 a20b59ef4bd634805245ea198b4b3f1538a2e242 gc go1.14.1]
16:45:18 DEBUG juju.cmd supercommand.go:92 args: []string{"/snap/juju/11231/bin/juju", "deploy", ".", "--debug"}
16:45:18 INFO juju.juju api.go:67 connecting to API addresses: [10.152.183.4:17070]
16:45:18 DEBUG juju.api apiclient.go:1105 successfully dialed "wss://10.152.183.4:17070/api"
16:45:18 INFO juju.api apiclient.go:637 connection established to "wss://10.152.183.4:17070/api"
16:45:18 INFO juju.juju api.go:67 connecting to API addresses: [10.152.183.4:17070]
16:45:18 DEBUG juju.api apiclient.go:1105 successfully dialed "wss://10.152.183.4:17070/model/2985ab8c-e7bc-49e7-8110-68a5e83123a6/api"
16:45:18 INFO juju.api apiclient.go:637 connection established to "wss://10.152.183.4:17070/model/2985ab8c-e7bc-49e7-8110-68a5e83123a6/api"
ERROR cloud service a#0de04db5-248d-470d-884e-0e4bde6405ee not found (not found)
16:45:18 DEBUG cmd supercommand.go:537 error stack:
cloud service a#0de04db5-248d-470d-884e-0e4bde6405ee not found (not found)
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/rpc/client.go:178:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/api/apiclient.go:1200:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/api/state.go:66:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/api/apiclient.go:299:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/api/apiclient.go:269:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/juju/api.go:72:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/cmd/modelcmd/base.go:218:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/cmd/modelcmd/modelcommand.go:424:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/cmd/modelcmd/modelcommand.go:405:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/cmd/juju/application/deploy.go:289:
/build/snapcraft-juju-c52e7e/parts/juju/go/src/github.com/juju/juju/cmd/juju/application/deploy.go:1156:

However, if I bootstrap the same cluster with juju 2.7.5 stable, it runs without an issue.

crodriguez@camille-hp:~/PycharmProjects/mssql-project/charm-mssql$ juju controllers
Use --refresh option with this command to see the latest information.

Controller Model User Access Cloud/Region Models Nodes HA Version
mk8s m2 admin superuser microk8s/localhost 4 1 - 2.7.5
mk8s2* m3 admin superuser microk8s/localhost 2 1 - 2.8-beta1

crodriguez@camille-hp:~/PycharmProjects/mssql-project/charm-mssql$ juju switch mk8s
mk8s2:admin/m3 -> mk8s:admin/m2
crodriguez@camille-hp:~/PycharmProjects/mssql-project/charm-mssql$ juju deploy . --debug
16:49:08 INFO juju.cmd supercommand.go:91 running juju [2.8-beta1 3436 a20b59ef4bd634805245ea198b4b3f1538a2e242 gc go1.14.1]
16:49:08 DEBUG juju.cmd supercommand.go:92 args: []string{"/snap/juju/11231/bin/juju", "deploy", ".", "--debug"}
16:49:08 INFO juju.juju api.go:67 connecting to API addresses: [10.152.183.242:17070]
16:49:08 DEBUG juju.api apiclient.go:1105 successfully dialed "wss://10.152.183.242:17070/api"
16:49:08 INFO juju.api apiclient.go:637 connection established to "wss://10.152.183.242:17070/api"
16:49:08 INFO juju.juju api.go:67 connecting to API addresses: [10.152.183.242:17070]
16:49:08 DEBUG juju.api apiclient.go:1105 successfully dialed "wss://10.152.183.242:17070/model/8e114456-9606-4116-8d70-808b0c9eec52/api"
16:49:08 INFO juju.api apiclient.go:637 connection established to "wss://10.152.183.242:17070/model/8e114456-9606-4116-8d70-808b0c9eec52/api"
16:49:08 INFO juju.juju api.go:67 connecting to API addresses: [10.152.183.242:17070]
16:49:08 DEBUG juju.api apiclient.go:1105 successfully dialed "wss://10.152.183.242:17070/api"
16:49:08 INFO juju.api apiclient.go:637 connection established to "wss://10.152.183.242:17070/api"
16:49:08 DEBUG juju.cmd.juju.application bundle.go:320 model: &bundlechanges.Model{
    Applications: {
        "mssql": &bundlechanges.Application{
            Name: "mssql",
            Charm: "local:kubernetes/mssql-0",
            Scale: 1,
            Options: {
            },
            Annotations: {},
            Constraints: "",
            Exposed: false,
            SubordinateTo: {},
            Series: "kubernetes",
            Placement: "",
            Units: {
                {Name:"mssql/0", Machine:""},
            },
        },
    },
    Machines: {
    },
    Relations: nil,
    ConstraintsEqual: func(string, string) bool {...},
    Sequence: {"volume":1, "application-mssql":1, "charmrev-local:kubernetes/mssql":1, "filesystem":1, "stores":1},
    sequence: {},
    MachineMap: {},
    logger: nil,
}
16:49:08 DEBUG juju.cmd.juju.application bundle.go:359 mssql exists in model uses a local charm, replacing with "local:kubernetes/mssql-0"
16:49:08 INFO cmd bundle.go:442 No changes to apply.
16:49:08 DEBUG juju.api monitor.go:35 RPC connection died
16:49:08 INFO cmd supercommand.go:544 command finished
crodriguez@camille-hp:~/PycharmProjects/mssql-project/charm-mssql$

[Ian Booth (wallyworld)]

Marking as fix released since this only existed in the 2.8 beta and an unreleased version of 2.7

[Camille Rodriguez (camille.rodriguez)]

Hi Ian, do you mean that there is a version of 2.8 that has this fixed already?

[Richard Harding (rharding)]

Camille, what he's saying is that it was a break on 2.8 which isn't gone to GA yet so the edge snap has the fix and is "released" as far as this bug goes.

[Camille Rodriguez (camille.rodriguez)]

I get that 2.8 is beta and not GA yet, it's normal to face issues with it during the development cycle, no worries about that. It just sound weird to me to say a fix is released when it isn't (it will be eventually, but the edge snap is currently broken)

[Ian Booth (wallyworld)]

It was marked as Fix Released because the bug was targeted at 2.7.6 milestone and the commit to that branch landed. The fix to 2.8 branch has now also landed (just needed to do a forward port). Ideally we should have targeted the bug at both branches to the status could be updated independently. Sorry for any confusion.