juju status results in unexpected fault address on arm64 using/ local provider

[Sean Feole]

JuJu Version:
juju-core:
  Installed: 1.17.7-0ubuntu1
  Candidate: 1.17.7-0ubuntu1

After running juju bootstrap against the local provider, The bootstrap appeared to complete successfully. I did not see any lxc containers available after the bootstrap, nor did /var/log/lxc contain any logs. The /var/log/juju-machine directory did contain a log of machine 0 and it appears to be somewhat in order. (see attached log)

Steps to reproduce on arm64:

1.) Install juju-local
2.) juju init
3.) juju switch local
4.) juju bootstrap --show-log --debug (wait for completion)
5.) juju status

sfeole@am1:~$ juju status
unexpected fault address 0x1
fatal error: fault
goroutine 7 [running]:
panic during panic

followed by,

sfeole@am1:~$ juju status
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0]

goroutine 7 [running]:

goroutine 7 [running]:

goroutine 7 [running]:

goroutine 7 [running]:
created by launchpad.net_juju_core_utils_parallel.loop.pN42_launchpad.net_juju_core_utils_parallel.Try
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/utils/parallel/try.go:86

goroutine 1 [chan receive]:
launchpad.net_tomb.Wait.pN23_launchpad.net_tomb.Tomb
        /build/buildd/juju-core-1.17.7/src/launchpad.net/tomb/tomb.go:110
launchpad.net_juju_core_utils_parallel.Result.pN42_launchpad.net_juju_core_utils_parallel.Try
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/utils/parallel/try.go:192
juju.newAPIFromStore
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/juju/api.go:185
juju.newAPIClient
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/juju/api.go:115
launchpad.net_juju_core_juju.NewAPIClientFromName
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/juju/api.go:86
main.Run.pN18_main.StatusCommand
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/juju/status.go:86
main.Run.N18_main.envCmdWrapper
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/juju/main.go:158
launchpad.net_juju_core_cmd.Run.pN40_launchpad.net_juju_core_cmd.SuperCommand
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/supercommand.go:298
launchpad.net_juju_core_cmd.Main
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/cmd.go:244
main.Main
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/juju/main.go:131
main.main
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/juju/main.go:173

goroutine 3 [syscall]:
        goroutine in C code; stack unavailable

goroutine 6 [select]:
launchpad.net_juju_core_utils_parallel.loop.pN42_launchpad.net_juju_core_utils_parallel.Try
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/utils/parallel/try.go:83
parallel.$nested3
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/utils/parallel/try.go:62
created by launchpad.net_juju_core_utils_parallel.NewTry
        /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/utils/parallel/try.go:60

goroutine 11 [finalizer wait]:

[Ian Booth (wallyworld)]

This isn't actually a bug in Juju. The gcc Go compiler has issues on ARM which are actively being worked on.

eg
- autoconf is incorrectly turning on the -fsplit-stack option for gccgo
- the stack size is set too small

Marking as Invalid since the root cause lies outside Juju.