Skip to content
This repository has been archived by the owner on Feb 12, 2021. It is now read-only.

systemd oem.target doesn't seem to exist #110

Closed
mikemaccana opened this issue Feb 18, 2014 · 2 comments · Fixed by #111
Closed

systemd oem.target doesn't seem to exist #110

mikemaccana opened this issue Feb 18, 2014 · 2 comments · Fixed by #111

Comments

@mikemaccana
Copy link
Contributor

Per https://coreos.com/docs/sdk-distributors/distributors/notes-for-distributors/, additional systemd unit files are part of a target called oem.target.

On CoreOS 206.1.0:

systemctl start oem.target
Failed to issue method call: Unit oem.target failed to load: No such file or directory. See system logs and 'systemctl status oem.target' for details.

And:

find /usr /etc -name '*target' | grep oem

Is blank.

systemctl status oem.target
oem.target
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Other targets, ie default.target, work fine,

Is there something missing, either in CoreOS or the instructions, to create oem.target?

@philips
Copy link
Contributor

philips commented Feb 18, 2014

/cc @marineam ?

mikemaccana added a commit to mikemaccana/docs that referenced this issue Feb 18, 2014
 - Add missing oem.target file mentioned in OEM .service files
 - Also small spelling / grammar fixes

Fixes coreos#110. Alternatively, oem.target could be built into the CoreOS image instead.
@marineam
Copy link
Contributor

It's just missing instructions that if the OEM script wants to use oem.target it needs to create it along with any other units. The system doesn't provide anything beyond the the ability to add ssh keys or run a script.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants