apb failed to create project

[tj13]

This form is for bug reports and feature requests. Major features will go through a spec process.

Feature:

Bug:

What happened:

--
  |  
  | PLAY [my-test-apb playbook to provision the application] ***********************
  |  
  | TASK [my-test-apb : test] ******************************************************
  | changed: [localhost]
  |  
  | TASK [test] ********************************************************************
  | fatal: [localhost]: FAILED! => {"changed": true, "cmd": "oc new-project test", "delta": "0:00:00.242205", "end": "2018-09-20 02:02:51.097463", "msg": "non-zero return code", "rc": 1, "start": "2018-09-20 02:02:50.855258", "stderr": "Error from server (Forbidden): You may not request a new project via this API.", "stderr_lines": ["Error from server (Forbidden): You may not request a new project via this API."], "stdout": "", "stdout_lines": []}
  |  
  | PLAY RECAP *********************************************************************
  | localhost : ok=1 changed=1 unreachable=0 failed=1

What you expected to happen:
project test can be created successfully.

How to reproduce it:
cat playbooks/provision.yml

• name: my-test-apb playbook to provision the application
  hosts: localhost
  gather_facts: false
  connection: local
  vars:
  apb_action: provision
  roles:

  • role: my-test-apb

  tasks:

  • name: test
    shell: oc new-project test

[eriknelson]

This is expected and by design, although it does block use cases that require cluster scoped privileges. I re-opened #715 to continue the discussion around this feature.