[manual provider] add-machine fails due to juju.fetch.oci service

Bug #1876959 reported by Peter Jose De Sousa
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Tim Penhey

Bug Description

Hi,

Problem:

Juju is reporting machine as "already provisioned"

Detail:

When installing juju 2.8/edge a snap service snap.juju.fetch-oci is installed alongside. The result is that juju's manaul machine check fails due to the systemd command checking for juju units:

The sequence of commands is in effect running this:

systemctl list-unit-files --no-legend --no-page -t service | grep -o -P '^\w[\S]*(?=\.service)' | grep juju.

[1,2,3]

This is an issue in the case of the deployment where the machine running juju is the machine which is being run as the manual machine, causing juju to erroneously report the machine as already provisioned.

Workaround:

The current workaround I have is to dirty remove the service:

`rm /etc/systemd/system/snap.juju.fetch-oci.service`

[1] https://github.com/juju/juju/blob/a0d745913c35e47c33dc13f0230ee55d9a0e021a/service/systemd/cmdline.go#L38
[2] https://github.com/juju/juju/blob/e792553644bf09b1991d8c3ab5c9a7ab57f8eceb/service/service.go#L189
[3] https://github.com/juju/juju/blob/e792553644bf09b1991d8c3ab5c9a7ab57f8eceb/environs/manual/sshprovisioner/sshprovisioner.go#L166

Thanks!

Peter

Tim Penhey (thumper)
Changed in juju:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Tim Penhey (thumper)
milestone: none → 2.8-rc1
Revision history for this message
Tim Penhey (thumper) wrote :
Tim Penhey (thumper)
Changed in juju:
status: Triaged → In Progress
Tim Penhey (thumper)
Changed in juju:
status: In Progress → Fix Committed
Harry Pidcock (hpidcock)
Changed in juju:
status: Fix Committed → Fix Released
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.