slack notification module error

[hundredblocks]

I'm getting a 404 not found error using the slack notification module as follows:

failed: [104.131.219.13 -> 127.0.0.1] => {"failed": true}
msg: failed to send payload={"username": "webhookbot", "text": "104.131.219.13 completed", "icon_emoji": ":ghost:", "channel": "#general", "link_names": 1} to https://cloudmode.slack.com/services/hooks/incoming-webhook?token=[obscured]: HTTP Error 404: Not Found

FATAL: all hosts have already failed -- aborting

the yml setup is:

- name: Send notification message via Slack all options
  local_action:
    module: slack
    domain: cloudmode.slack.com
    token: <my_token>
    msg: "{{ inventory_hostname }} completed"
    channel: "#general"
    username: "webhookbot"
    icon_emoji: ":ghost:"

the equivalent CURL command works from the host upon which the ansible script is executing. I've also verified my token using CURL to successfully post to a slack channel

Any ideas?

Ansible template below:

Issue Type:

Bug report

Ansible Version:

ansible 1.7.1

Environment:

Ubuntu 14.04

Summary:

I'm getting a 404 not found error using the slack notification module as follows:

failed: [104.131.219.13 -> 127.0.0.1] => {"failed": true}
msg: failed to send payload={"username": "webhookbot", "text": "104.131.219.13 completed", "icon_emoji": ":ghost:", "channel": "#general", "link_names": 1} to https://cloudmode.slack.com/services/hooks/incoming-webhook?token=[obscured]: HTTP Error 404: Not Found

Steps To Reproduce:

the yml setup is:

- name: Send notification message via Slack all options
  local_action:
    module: slack
    domain: cloudmode.slack.com
    token: <my_token>
    msg: "{{ inventory_hostname }} completed"
    channel: "#general"
    username: "webhookbot"
    icon_emoji: ":ghost:"

with an incoming webhook setup on slack

Expected Results:

A message to the general channel of cloudmode.slack.com when ansible-playbook is called

Actual Results:

failed: [104.131.219.13 -> 127.0.0.1] => {"failed": true}
msg: failed to send payload={"username": "webhookbot", "text": "104.131.219.13 completed", "icon_emoji": ":ghost:", "channel": "#general", "link_names": 1} to https://cloudmode.slack.com/services/hooks/incoming-webhook?token=[obscured]: HTTP Error 404: Not Found

[gmotruk]

I have same problem... any solution/workaround?
Thanks

[mpdehaan]

Hi!

Thanks very much for your interest in Ansible. It sincerely means a lot to us.

On September 26, 2014, due to enormous levels of contribution to the project Ansible decided to reorganize module repos, making it easier
for developers to work on the project and for us to more easily manage new contributions and tickets.

We split modules from the main project off into two repos, http://github.com/ansible/ansible-modules-core and http://github.com/ansible/ansible-modules-extras

If you would still like this ticket attended to, we will need your help in having it reopened in one of the two new repos, and instructions are provided below.

We apologize that we are not able to make this transition happen seamlessly, though this is a one-time change and your help is greatly appreciated --
this will greatly improve velocity going forward.

Both sets of modules will ship with Ansible, though they'll receive slightly different ticket handling.

To locate where a module lives between 'core' and 'extras'

• Find the module at http://docs.ansible.com/list_of_all_modules.html
• Open the documentation page for that module
• If the bottom of the docs say "This is an extras module", submit your ticket to https://github.com/ansible/ansible-modules-extras
• Otherwise, submit your pull request to update the existing module to https://github.com/ansible/ansible-modules-core
• action_plugins (modules with server side components) still live in the main repo. If your ticket affects both, open the ticket
  on the module repo just the same.

Additionally, should you need more help with this, you can ask questions on:

• the ansible-project mailing list: https://groups.google.com/forum/#!forum/ansible-project

Thank you very much!

[mpdehaan]

Hi!

Thanks very much for your interest in Ansible. It sincerely means a lot to us.

On September 26, 2014, due to enormous levels of contribution to the project Ansible decided to reorganize module repos, making it easier
for developers to work on the project and for us to more easily manage new contributions and tickets.

We split modules from the main project off into two repos, http://github.com/ansible/ansible-modules-core and http://github.com/ansible/ansible-modules-extras

If you would still like this ticket attended to, we will need your help in having it reopened in one of the two new repos, and instructions are provided below.

We apologize that we are not able to make this transition happen seamlessly, though this is a one-time change and your help is greatly appreciated --
this will greatly improve velocity going forward.

Both sets of modules will ship with Ansible, though they'll receive slightly different ticket handling.

To locate where a module lives between 'core' and 'extras'

• Find the module at http://docs.ansible.com/list_of_all_modules.html
• Open the documentation page for that module
• If the bottom of the docs say "This is an extras module", submit your ticket to https://github.com/ansible/ansible-modules-extras
• Otherwise, submit your pull request to update the existing module to https://github.com/ansible/ansible-modules-core
• action_plugins (modules with server side components) still live in the main repo. If your ticket affects both, open the ticket
  on the module repo just the same.

Additionally, should you need more help with this, you can ask questions on:

• the ansible-project mailing list: https://groups.google.com/forum/#!forum/ansible-project

Thank you very much!

[lucidaeon]

For what it's worth, you'll get the exact same 404 response if the integration was created and subsequently disabled.