Closed Bug 1276397 Opened 9 years ago Closed 9 years ago

hgweb container setup fails with "Destination directory /etc/systemd/system does not exist"

Categories

(MozReview Graveyard :: Testing / Development Environment, defect)

Unspecified
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mars, Assigned: mars)

Details

'mozreview start' fails to provision the hgweb container with ansible. This blocks dev environment setup and test runs. Here is the log for start-local-mozreview: ERROR hgweb> TASK: [hg-web | systemd service file for vcsreplicator] *********************** ERROR hgweb> ERROR hgweb> failed: [localhost] => {"checksum": "3c49c127c0316329beeef3f3abbb7f8bdb13c286", "failed": true} ERROR hgweb> msg: Destination directory /etc/systemd/system does not exist ERROR hgweb> ERROR hgweb> FATAL: all hosts have already failed -- aborting ... ERROR hgweb> localhost : ok=101 changed=85 unreachable=0 failed=1 The error stems from a mismatch between the OS targeted by the ansible scripts and the guest OS used for the mozreview development environment. mozreview deploys to CentOS 6, which doesn't have systemd. This part of the ansible scripts targets CentOS 7, which does use systemd. Running the ansible scripts with 'mozreview start' or 'start-local-mozreview' provisions a CentOS 6 box, and the ansible play fails.
Summary: hgweb container setup fails with Destination directory /etc/systemd/system does not exist → hgweb container setup fails with "Destination directory /etc/systemd/system does not exist"
This should be fixed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.