Rocky 8.8: Create Project - Ascender Playbooks HTTP Error 500 (first try)

[adamhgriffith-uofu]

Hi,

First, thank you for putting this installer together. It is very much helping to cut through the clutter of getting Kubernetes and Ascender spooled up.

Today I encountered the following error on a clean Rocky 8.8 host after having checked out 7267e8e:

[root@ascender-test ascender-install]# ./setup.sh 
Using Inventory File: ./inventory
...
...
TASK [setup_playbooks : Create Inventory - Default Inventory] ******************************************************************************************************************
changed: [localhost]

TASK [setup_playbooks : Create Projects] ***************************************************************************************************************************************
included: /tmp/ascender-install/playbooks/roles/setup_playbooks/tasks/projects.yml for localhost => (item=Ascender Playbooks)
included: /tmp/ascender-install/playbooks/roles/setup_playbooks/tasks/projects.yml for localhost => (item=Ansible Lockdown - CIS - EL9)
included: /tmp/ascender-install/playbooks/roles/setup_playbooks/tasks/projects.yml for localhost => (item=Ansible Lockdown - CIS - EL8)
included: /tmp/ascender-install/playbooks/roles/setup_playbooks/tasks/projects.yml for localhost => (item=Ansible Lockdown - STIG - EL8)

TASK [setup_playbooks : Create Project - Ascender Playbooks] *******************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "The host sent back a server error (HTTP Error 500: Internal Server Error): /api/v2/projects/. Please check the logs and try again later"}

PLAY RECAP *********************************************************************************************************************************************************************
ascender_host              : ok=14   changed=3    unreachable=0    failed=0    skipped=4    rescued=0    ignored=0   
localhost                  : ok=38   changed=11   unreachable=0    failed=1    skipped=5    rescued=0    ignored=0   

ERROR OCCURRED DURING SETUP

Repeating the setup resulted in a success.

The configuration variables from default.config.yml are:

--
# ---Kubernetes-specific variables---

k8s_platform: k3s
DKP_CLUSTER_NAME: dkp-cluster
kube_install: true
k3s_master_node_ip: "127.0.0.1"
k8s_lb_protocol: https

# ---Local artifact variables---

tls_crt_path: "/etc/letsencrypt/live/ascender.our.domain/fullchain.pem"
tls_key_path: "/etc/letsencrypt/live/ascender.our.domain/privkey.pem"

use_etc_hosts: false

tmp_dir: "/tmp/ascender_install_artifacts"

# ---Ascender install variables---

ASCENDER_HOSTNAME: ascender.our.domain
ASCENDER_NAMESPACE: ascender
ASCENDER_ADMIN_USER: admin
ASCENDER_ADMIN_PASSWORD: "UPPERlower+["

ASCENDER_IMAGE: ghcr.io/ctrliq/ascender
ASCENDER_VERSION: 23.3.0
ANSIBLE_OPERATOR_VERSION: 2.7.0

ascender_garbage_collect_secrets: true

ascender_replicas: 1
ascender_image_pull_policy: Always


# ---Ledger install variables---

LEDGER_INSTALL: false

[cigamit]

Ok, I think the issue on this is we are still going a bit too fast and not waiting long enough. The previous tasks before this doesn't cause anything to utilize an execution environment. The bootstrap process, preloads the Demo data (which I just did a commit to stop most of it) and then it registers the EE's using these commands

awx-manage create_preload_data
awx-manage register_default_execution_environments

I believe the task above is attempting to sync a project while the EEs have yet to be registered. The quick fix would be to have it check if EEs are registered before proceeding instead of checking if the Org is created.

---

Did a Project Sync job get created in Ascender when the error occurred? And if so, what was its output?

[adamhgriffith-uofu]

Unfortunately, I re-ran the setup after the initial failure and won't be able to answer your questions. I do know that after the second run the example jobs and templates were successfully applied.

[cigamit]

Inside Ascender, if you go to Jobs, you can see if there is a failed one near the beginning. It really doesn't matter too much, I will be putting in a fix for this this afternoon to double check that an EE exists before continuing.

[adamhgriffith-uofu]

Gotcha. I see the following four successful jobs.

[cigamit]

Ok, so it failed to create the project also, thats good to know.