Error during server creation

[54ja]

TASK [cloud-scaleway : Create a server] ***********************************************************************************************************************************
[WARNING]: https://cp-ams1.scaleway.com/servers?name=jesse-vpn&per_page=1
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error during server creation: (403) {'type': 'authorization_required', 'message': 'Authorization required'}"}
included: /Users/jesse/algo/playbooks/rescue.yml for localhost

TASK [debug] **************************************************************************************************************************************************************
ok: [localhost] => {
"fail_hint": [
"Sorry, but something went wrong!",
"Please check the troubleshooting guide.",
"https://trailofbits.github.io/algo/troubleshooting.html"
]
}

TASK [Fail the installation] **********************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed as requested from task"}

I don't know what is going wrong I'm trying to use scaleway and would like some help with fixing this error. Thanks.

[davidemyers]

I've never used Scaleway, but make sure you're entering the proper auth token as described here.

[54ja]

I've made sure and I'm pretty sure I got all of that part correct I'm just not sure why its not working.

[justjulian]

Same error here. Got it working by using the Project ID, not Organization ID. For testing, replace

algo/roles/cloud-scaleway/tasks/main.yml

Line 16 in 7203f33

organization_id: "{{ scaleway_org.scaleway_organization_info[0]['id'] }}"

with the following line
organization_id: "<your_project_id>"

This is in my opinion related to #14245

Tested with 7203f33

[gromain]

This worked for me. It's indeed related to the issue I opened.

[marco-m]

Stumbled upon the same problem.
I think that the explanation is historical: Scaleway used not to have projects, everything was "global" in the user account.
Probably the ansible role has been written in that period and I would assume that it worked.
Then Scaleway added projects, and the role broke...