github.com/juju/juju/cmd/juju/application/deployer.(*deployBundle).checkExplicitSeries(0xc00071c240, 0xc0005a7f00)

Bug #2016903 reported by Felipe Reyes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Committed
High
Nicolas Vinuesa

Bug Description

When trying to deploy a bundle (see attachment) the client crashes with the following stacktrace:

$ juju deploy ./bundles/lpar/jammy-antelope-ovn-edge.yaml --map-machines=existing --force
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1d00108]

goroutine 1 [running]:
github.com/juju/juju/cmd/juju/application/deployer.(*deployBundle).checkExplicitSeries(0xc00071c240, 0xc0005a7f00)
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/application/deployer/bundle.go:189 +0x2c8
github.com/juju/juju/cmd/juju/application/deployer.(*deployBundle).deploy(0xc00071c240, 0xc00003d080, {0x51109f8?, 0xc000207360}, {0x50ccd00?, 0xc0005fc318})
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/application/deployer/bundle.go:102 +0x3ed
github.com/juju/juju/cmd/juju/application/deployer.(*localBundle).PrepareAndDeploy(0x0?, 0x0?, {0x51109f8?, 0xc000207360?}, {0x50ccd00?, 0xc0005fc318?})
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/application/deployer/bundle.go:308 +0x2f
github.com/juju/juju/cmd/juju/application.(*DeployCommand).Run(0xc0002f9400, 0x510a301?)
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/application/deploy.go:855 +0xa86
github.com/juju/juju/cmd/modelcmd.(*modelCommandWrapper).Run(0xc0008d6b10, 0xc000c651a0?)
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/modelcmd/modelcommand.go:663 +0x123
github.com/juju/juju/cmd/modelcmd.(*baseCommandWrapper).Run(0xc000943650, 0x400000006?)
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/modelcmd/base.go:554 +0xaf
github.com/juju/cmd/v3.(*SuperCommand).Run(0xc0007357c0, 0xc00003d080)
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/vendor/github.com/juju/cmd/v3/supercommand.go:534 +0x378
github.com/juju/cmd/v3.Main({0x50e5ff8, 0xc0007357c0}, 0xc00003d080, {0xc0005d2f80, 0x4, 0x4})
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/vendor/github.com/juju/cmd/v3/cmd.go:419 +0x25d
github.com/juju/juju/cmd/juju/commands.jujuMain.Run({0xc0000d8140?}, {0xc0000720a0, 0x5, 0x5})
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/commands/main.go:202 +0x8a5
github.com/juju/juju/cmd/juju/commands.Main(...)
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/commands/main.go:125
main.main()
        /build/snapcraft-juju-fe13d84e0a35d6d9a725f8dde56329e8/parts/juju/build/cmd/juju/main.go:27 +0x72

$ snap info juju | grep installed
installed: 3.2-beta2 (22890) 80MB -
$ juju --version
3.2-beta2-genericlinux-amd64
$ juju status -m controller
Model Controller Cloud/Region Version SLA Timestamp
controller juju-controller-s390x manual 3.2-beta1 unsupported 15:35:04Z

App Version Status Scale Charm Channel Rev Exposed Message
controller active 1 juju-controller 3.2/stable 14 no

Unit Workload Agent Machine Public address Ports Message
controller/0* active idle 0 10.13.3.12

Machine State Address Inst id Base AZ Message
0 started 10.13.3.12 manual: ubuntu@20.04 Manually provisioned machine

Revision history for this message
Felipe Reyes (freyes) wrote :

Reverting the client to beta1 solved the issue.

$ sudo snap revert juju
juju reverted to 3.2-beta1
$ juju deploy ./bundles/lpar/jammy-antelope-ovn-edge.yaml --map-machines=existing --force
Located charm "ceph-mon" in charm-hub, channel quincy/stable
Located charm "ceph-osd" in charm-hub, channel quincy/stable
Located charm "ceph-radosgw" in charm-hub, channel quincy/stable
...

Revision history for this message
Felipe Reyes (freyes) wrote :
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 3.2-rc1
Changed in juju:
assignee: nobody → Nicolas Vinuesa (nvinuesa)
status: Triaged → In Progress
tags: added: cdo-qa cdo-release-blocker foundations-engine
Revision history for this message
Moises Emilio Benzan Mora (moisesbenzan) wrote :

Solutions QA team has also seen this bug occurring on several runs. One example of it is the following:

Run: https://solutions.qa.canonical.com/v2/testruns/401db13a-58e4-430d-bc57-d932cdf50e6c
Artifacts: https://oil-jenkins.canonical.com/artifacts/401db13a-58e4-430d-bc57-d932cdf50e6c/index.html

All other occurrences can be seen at: https://solutions.qa.canonical.com/bugs/bugs/bug/2016903

Revision history for this message
Simon Richardson (simonrichardson) wrote :
Changed in juju:
status: In Progress → Fix Committed
Ian Booth (wallyworld)
Changed in juju:
milestone: 3.2-rc1 → 3.2-beta3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.