Open Stack

Hello,

Thank you very much for the reply! 

haproxy and keepalived both show status active on infra1 (my primary node).

Curl shows "503 Service Unavailable No server is available to handle this request”

(Also the URL is http not https….)

If I am using bonding on the infra nodes, should the haproxy_keepalived_external_interface be the device name (enp1s0) or bond0?

Earlier in the output I find the following error (showing for all 3 infra nodes):

------------

TASK [systemd_mount : Set the state of the mount] *****************************************************************************************************************************************
fatal: [infra3_repo_container-7ca5db88]: FAILED! => {"changed": false, "cmd": "systemctl reload-or-restart $(systemd-escape -p --suffix=\"mount\" \"/var/www/repo\")", "delta": "0:00:00.022275", "end": "2022-08-16 14:16:34.926861", "msg": "non-zero return code", "rc": 1, "start": "2022-08-16 14:16:34.904586", "stderr": "Job for var-www-repo.mount failed.\nSee \"systemctl status var-www-repo.mount\" and \"journalctl -xe\" for details.", "stderr_lines": ["Job for var-www-repo.mount failed.", "See \"systemctl status var-www-repo.mount\" and \"journalctl -xe\" for details."], "stdout": "", "stdout_lines": []}

——————

Running "systemctl status var-www-repo.mount” gives an output of “Unit var-www-repo.mount could not be found."

Thank you again!

Father Vlasie

> On Aug 16, 2022, at 6:32 AM, James Denton <james.denton at rackspace.com> wrote:
> 
> Hello,
>  
> That error means the repo server at 192.168.3.9:8181 is unavailable. The repo server sits behind haproxy, which should be listening on 192.168.3.9 port 8181 on the active (primary) node. You can verify this by issuing a ‘curl -v https://192.168.3.9:8181/’. You might check the haproxy service status and/or keepalived status to ensure they are operating properly. If the IP cannot be bound to the correct interface, keepalive may not start.
>  
> James Denton
> Rackspace Private Cloud
>  
> From: Father Vlasie <fv at spots.edu>
> Date: Tuesday, August 16, 2022 at 7:38 AM
> To: openstack-discuss at lists.openstack.org <openstack-discuss at lists.openstack.org>
> Subject: [openstack-ansible] [yoga] utility_container failure
> 
> CAUTION: This message originated externally, please use caution when clicking on links or opening attachments!
> 
> 
> Hello everyone,
> 
> I have happily progressed to the second step of running the playbooks, namely "openstack-ansible setup-infrastructure.yml"
> 
> Everything looks good except for just one error which is mystifying me:
> 
> ----------------
> 
> TASK [Get list of repo packages] **********************************************************************************************************************************************************
> fatal: [infra1_utility_container-5ec32cb5]: FAILED! => {"changed": false, "content": "", "elapsed": 30, "msg": "Status code was -1 and not [200]: Request failed: <urlopen error timed out>", "redirected": false, "status": -1, "url": "https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2F192.168.3.9%3A8181%2Fconstraints%2Fupper_constraints_cached.txt&data=05%7C01%7Cjames.denton%40rackspace.com%7Ca51d530625ae4bcaed1008da7f84329f%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C637962503012704928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=viIOEpR8sqc0TxoeDiYSMVEJeE%2FhkE7pxCubo49VsTQ%3D&reserved=0"}
> 
> ----------------
> 
> 192.168.3.9 is the IP listed in user_variables.yml under haproxy_keepalived_internal_vip_cidr
> 
> Any help or pointers would be very much appreciated!
> 
> Thank you,
> 
> Father Vlasie
>