-
Notifications
You must be signed in to change notification settings - Fork 41
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
Test agent connect via ControllerAddress #741
Test agent connect via ControllerAddress #741
Conversation
08e478a
to
1e88c8f
Compare
...s/tests/tier0/bluechi-agent-connect-via-manager-address/config/ManagerAddress=127.0.0.1.conf
Outdated
Show resolved
Hide resolved
tests/tests/tier0/bluechi-agent-connect-via-manager-address/main.fmf
Outdated
Show resolved
Hide resolved
1e88c8f
to
dae2e84
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
a8c9320
to
15a53f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test doesn't really test that an agent can connect via the ControllerAddress
option as it is suggested in the summary of main.fmf
. It tests that it fails, but doesn't verify the reason.
I'd suggest setting up a bluechi-agent and bluechi-controller on the same machine/container and try to make this work. The ControllerAddress
was intended to work with systemd sockets, so unix sockets, for example. You can have a look at how it is used in the getting started guide:
https://bluechi.readthedocs.io/en/latest/getting_started/securing_multi_node/#haproxy-as-a-reverse-proxy
tests/tests/tier0/bluechi-agent-connect-via-manager-address/config/Invalid-ManagerAddress.conf
Outdated
Show resolved
Hide resolved
83af363
to
10533ad
Compare
.../bluechi-agent-connect-via-manager-address/test_bluechi_agent_connect_via_manager_address.py
Outdated
Show resolved
Hide resolved
.../bluechi-agent-connect-via-manager-address/test_bluechi_agent_connect_via_manager_address.py
Outdated
Show resolved
Hide resolved
697aec7
to
5544fa9
Compare
...hi-agent-connect-via-controller-address/test_bluechi_agent_connect_via_controller_address.py
Outdated
Show resolved
Hide resolved
...hi-agent-connect-via-controller-address/test_bluechi_agent_connect_via_controller_address.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments, but other than that LGTM
7980550
to
c4519b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Small NIT. As soon as you update the branch we can merge @ArtiomDivak
...sts/tier0/bluechi-agent-connect-via-controller-address/config/Invalid-ControllerAddress.conf
Outdated
Show resolved
Hide resolved
c4519b7
to
4f39e65
Compare
4f39e65
to
205dcd7
Compare
Added a test for agent to test if it connectes via ControllerAddress. This test will run an agent and controller. The agent configuration will be change to invalid ControllerAdress and then to valid one. The valid configuration will get an IP the the controller is listenning to and the invalid one will get an unlistened IP. Related: eclipse-bluechi#668 Signed-off-by: Artiom Divak <adivak@redhat.com>
205dcd7
to
bebca9a
Compare
Added a test for agent to test if it connectes via ControllerAddress. This test will run an agent and change its configuration to use localhost instead of the real valid IP address in ControllerAddress and expect the agent to be failed because the controller is not listening on this IP.
Related: #668