Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receptor can be run with nonexistent config specified #225

Open
lhellebr opened this issue May 20, 2020 · 1 comment
Open

Receptor can be run with nonexistent config specified #225

lhellebr opened this issue May 20, 2020 · 1 comment

Comments

@lhellebr
Copy link

# systemctl start receptor@DUMMY
# systemctl status receptor@*
● [email protected] - Receptor Node for DUMMY
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2020-05-20 08:09:38 EDT; 7s ago
 Main PID: 11328 (receptor)
   CGroup: /system.slice/system-receptor.slice/[email protected]
           └─11328 /usr/bin/python3 /usr/bin/receptor -c /etc/receptor/DUMMY/receptor.conf -d /var/data/receptor/DUMMY node

May 20 08:09:38 dhcp-2-50.vms.sat.rdu2.redhat.com systemd[1]: Started Receptor Node for DUMMY.

The same happens when invoking the receptor command directly. I'd expect an error message and failure here.

@zedr
Copy link

zedr commented May 21, 2021

Confirmed when installing the Receptor Plugin (receptor-0.6.3-2.el7) for Ansible Tower 3.8.1

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

No branches or pull requests

2 participants