[manual provider] add-machine fails due to juju.fetch.oci service
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]
[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/
[1] https:/
[2] https:/
[3] https:/
Thanks!
Peter
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Tim Penhey (thumper) |
milestone: | none → 2.8-rc1 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju/ juju/pull/ 11538