juju 2.8-beta1 from snap fails to bootstrap controller

Bug #1871197 reported by Facundo Batista
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Harry Pidcock

Bug Description

Installed juju from edge channel, got 2.8-beta1.

Tried to bootstrap a new controller, it failed:

$ juju bootstrap localhost testingcharms
...
/bin/bash: line 439: /var/lib/juju/tools/2.8-beta1.1-bionic-amd64/jujud: No such file or directory
ERROR failed to bootstrap model: subprocess encountered error code 127

(full log attached)

If I run the same with `--keep-broken`, and then get into the "broken" machine, I see that that file *is* there:

# ls -l /var/lib/juju/tools/2.8-beta1.1-bionic-amd64/jujud
-rwxr-xr-x 1 ubuntu ubuntu 156113392 Apr 6 17:55 /var/lib/juju/tools/2.8-beta1.1-bionic-amd64/jujud
# file /var/lib/juju/tools/2.8-beta1.1-bionic-amd64/jujud
/var/lib/juju/tools/2.8-beta1.1-bionic-amd64/jujud: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /snap/co, for GNU/Linux 3.2.0, BuildID[sha1]=51c3cc98ecc06540ded75e4ecffd2ada8dc901aa, not stripped

That part "interpreter /snap/co" is very suspicious.

Revision history for this message
Facundo Batista (facundo) wrote :
Changed in juju:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 2.9-beta1
milestone: 2.9-beta1 → 2.8-beta1
Harry Pidcock (hpidcock)
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Harry Pidcock (hpidcock)
Revision history for this message
Harry Pidcock (hpidcock) wrote :
Harry Pidcock (hpidcock)
Changed in juju:
status: In Progress → Fix Committed
Revision history for this message
John A Meinel (jameinel) wrote :

Marking this Fix Released as it only existed as a bug in the Edge channel, and I have confirmed that you can bootstrap as expected.

Changed in juju:
status: Fix Committed → Fix Released
Revision history for this message
John A Meinel (jameinel) wrote :

BTW, thanks for the fast turnaround on the fix.

Revision history for this message
Facundo Batista (facundo) wrote :

This indeed was fixed! Thank you very much for the speedy response!!

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.