7 Commits (9793b194b98951c2b752c99b2bc08a9664cf12cb)

Author	SHA1	Message	Date
Jordan Borean	18c35b69fb	setup_rabbitmq - fix erlang pinned dependencies (#51048)	6 years ago
hyperized	64bacb0e02	Setup TLS integration test for RabbitMQ (#50363) ... * Make TLS available for RabbitMQ * Use correct path * Include cleanup * Also remove unused package * Don't generate a TLS cert every time if one already has been generated * Add newlines, clean up repository and clarify block purpose * One too many new lines :) * Make TLS certs static	6 years ago
Jon Bergli Heier	9c02ade536	rabbitmq_binding: Add support for state=absent (#48599) ... * rabbitmq_binding: Add support for state=absent * Add integration tests for rabbitmq_binding * Update testcases * Add changelog fragment	6 years ago
Matt Clay	17b3171917	Get rabbitmq and erlang GPG keys from S3 in tests.	6 years ago
Pilou	955579cd72	rabbitmq_user: 'node' parameter: add default value (#38156) ... * Remove unnecessary workaround * add test: set RABBITMQ_NODENAME environment variable The following error occurs: TASK [rabbitmq_user : Add user] *** fatal: [testhost]: FAILED! => { "changed": false, "cmd": "/usr/sbin/rabbitmqctl -q list_users", "rc": 69, "msg": "Error:********@c65c2bc59398'. Please see diagnostics information and suggestions below.\n\nMost common reasons for this are:\n\n * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)\n * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)\n * Target node is not running\n\nIn addition to the diagnostics info below:\n\n * See the CLI, clustering and networking guides on http://rabbitmq.com/documentation.html to learn more\n * Consult server logs on node test@c65c2bc59398\n\nDIAGNOSTICS\n===========\n\nattempted to contact:********@c65c2bc59398\n * effective user's home directory: /var/lib/rabbitmq\n * Erlang cookie hash: 3MxcYFrJzfhEL+FlUfLlQw==", "stderr": [...], "stderr_lines": [ "Error: unable to perform an operation on node 'test@c65c2bc59398'. Please see diagnostics information and suggestions below.", "", "Most common reasons for this are:", "", " * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)", " * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)", " * Target node is not running", "", "In addition to the diagnostics info below:", "", " * See the CLI, clustering and networking guides on http://rabbitmq.com/documentation.html to learn more", " * Consult server logs on node test@c65c2bc59398", "", "DIAGNOSTICS", "===========", "", "attempted to contact: [test@c65c2bc59398]", "", "test@c65c2bc59398:", " * connected to epmd (port 4369) on c65c2bc59398", " * epmd reports: node 'test' not running at all", " other nodes on c65c2bc59398: [rabbit]", " * suggestion: start the node", "", "Current node details:", " * node name: rabbitmqcli2@c65c2bc59398", " * effective user's home directory: /var/lib/rabbitmq", " * Erlang cookie hash: 3MxcYFrJzfhEL+FlUfLlQw==", "" ], "stdout": "", "stdout_lines": [] } * node parameter: fix default value 'rabbit' is the default value mentioned in the module documentation.	6 years ago
Martin Krizek	a8d4bf8642	Fix rabbitmq_* integration tests (#41836)	6 years ago
Artem Zinenko	b9571eb4bf	Integration tests for rabbitmq_user module (#35421)	7 years ago