conjure-up on ppc64el claims the utility is downloaded to ~/kubectl and this is a lie

[Steve Langasek]

After successfully upconjuring kubernetes core on a ppc64el system, conjure-up reports that

  The Kubernetes client utility is now available at '~/kubectl'

This is a lie, there is nothing there.

'juju status' also reports no machines on the local lxd, but conjure-up had no complaints.

$ juju status
Model Controller Cloud/Region Version
conjure-up mayfly localhost/localhost 2.0.2

App Version Status Scale Charm Store Rev OS Notes

Unit Workload Agent Machine Public address Ports Message

Machine State DNS Inst id Series AZ

$ juju list-models
Controller: mayfly

Model Cloud/Region Status Machines Cores Access Last connection
controller localhost/localhost available 1 - admin just now
conjure-up* localhost/localhost available 0 - admin 9 seconds ago

$

[Adam Stokes (adam-stokes)]

Tracking here: https://github.com/conjure-up/conjure-up/issues/594

[Mike McCracken (mikemc)]

copypaste from the github bug FYI:

OK, so this won't work on ppc64el: the kubernetes-core spell gets kubectl from the kubernetes-master charm, which only packages x86-64 binaries.
Our kubernetes guys are telling us this is from upstream - there are no current kubernetes builds for ppc64 or s390x.