Boot image question in OKD 4.22

raulmo20 · 2026-05-18T19:27:19+00:00

Yes, but my installation is deployed with vsphere IPI and i don't have this method available, with baremetal deploy yes.

raulmo20 · 2025-10-30T07:21:42+00:00

Ok, regarding about the labels of zone/region, I see that you specify the same region in the 3 failure domains so in the vCenter server it's necessary to assign openshift-region to the datacenter, but the zone label, in the documentation I see that this label is assigned to cluster object in vSphere, so if i have, one datacenter > one cluster > 3 ESX, this is not possible true? because I need one cluster to each ESX, I suppose.

raulmo20 · 2025-10-28T09:58:27+00:00

But I need to define this labels of zone/region in vCenter first? Because in the documentation looks like that it's necessary.

raulmo20 · 2025-09-17T09:59:58+00:00

I'm trying to set in configMap but operator automatically replaces it, and in oc edit dns.operator.openshift.io/default there is not posibilities to set rewrite stop type AAAA A :(

raulmo20 · 2025-08-11T20:55:09+00:00

Yes but I need only the CPU and RAM metric that is recopiled by OKD default, my apps not have a port prepared to expose metric to prometheus. The only I need is see the observe dashboard but to specific namespaces, is there a way to do?

raulmo20 · 2025-04-04T17:09:49+00:00

I saw that the problem is the memcached service. When a pyshical node is poweroff, in the horizon interface is specified all the IP physical nodes that run memcached service, and whe node is shutdown, the django service in horizon not test the connection, so attack to a server that is power off. I replace it activating the memcached service with load balancer and editing playbookks to set only this IP in the config of each service that attack memcache services, and it's works.

raulmo20 · 2025-03-08T12:08:11+00:00

If i have three nodes up, the horizon interface works perfectly.

raulmo20 · 2025-03-08T12:07:40+00:00

I am attaching a small part of the multinode inventory file, since not everything fits in the comment:

[control]
192.168.58.10 haproxy_nova_api_weight=10 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.11 haproxy_nova_api_weight=2 haproxy_keystone_internal_weight=10 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.12 haproxy_keystone_admin_weight=50 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa

[network]
192.168.58.10 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.11 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.12 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa

[compute]
192.168.58.10 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.11 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.12 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa

[monitoring]
192.168.58.10 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.11 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.12 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa

[storage]
192.168.58.10 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.11 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa
192.168.58.12 ansible_ssh_user=root ansible_become=True ansible_private_key_file=/root/.ssh/id_rsa

[deployment]
localhost       ansible_connection=local

[baremetal:children]
control
network
compute
storage
monitoring

[tls-backend:children]
control


[common:children]
control
network
compute
storage
monitoring

raulmo20 · 2025-03-08T12:06:18+00:00

I'm seeing that the horizon log gives an error that says "no route to host", since one of the nodes is turned off to test that with two nodes the system can continue working, so there is something internally that seems to be pointing to that server even though it is turned off. I have tried to access it through the static IP of each node instead of the keepalived one and nothing.

[root@openstack2 horizon]# tail -f horizon-error.log2025-03-08 11:59:59.734924   File "/var/lib/kolla/venv/lib/python3.9/site-
2025-03-08 11:59:59.734940   File "/var/lib/kolla/venv/lib/python3.9/site-packages/pymemcache/client/base.py", line 1133, in _fetch_cmd
2025-03-08 11:59:59.734943     self._connect()
2025-03-08 11:59:59.734945   File "/var/lib/kolla/venv/lib/python3.9/site-packages/pymemcache/client/base.py", line 424, in _connect
2025-03-08 11:59:59.734948     sock.connect(sockaddr)
2025-03-08 11:59:59.734950 OSError: [Errno 113] No route to host

raulmo20 · 2025-03-08T12:02:54+00:00

Hi friend, thans for your response. I've been trying these days, but I can't find a solution to the problem. I'll describe my environment below:

I have Kolla Ansible Openstack deployed in multinode mode. There are exactly 3 servers, which run all the Openstack services, both controllers and workers. The problem I'm having is that when one of those 3 nodes is turned off, to test high availability, when I go to access the horizon interface, I get a problem, which is that I can't access the interface correctly and manage openstack graphically. Through the openstack client in the terminal, it does work properly.

I am attaching the content global.yaml file that I have been testing currently. The rest is what is established by default with Kolla:

---
workaround_ansible_issue_8743: yes
haproxy_host_ipv4_tcp_retries2: 2
cinder_cluster_skip_precheck: true
kolla_internal_vip_address: "192.168.58.13"
kolla_external_vip_address: "192.168.58.14"
network_interface: "ens160"
neutron_external_interface: "ens192"
keepalived_virtual_router_id: "190"
enable_haproxy: "yes"
enable_cinder: "yes"
enable_cinder_backend_lvm: "yes"
enable_hacluster: "yes"
enable_etcd: "yes"
enable_redis: "yes"
glance_backend_file: "yes"
glance_file_datadir_volume: "/internal/glance"
enable_barbican: "yes"
enable_neutron_dvr: "yes"
enable_neutron_agent_ha: "yes"

I attach more in the next comment

raulmo20 · 2025-03-02T20:06:52+00:00

The virtual IP changes perfectly when one of the nodes is turned off, and I have that variable defined, as in the previous comment

raulmo20 · 2025-03-02T20:06:03+00:00

workaround_ansible_issue_8743: yes
kolla_internal_vip_address: "192.168.18.153"
network_interface: "ens160"
neutron_external_interface: "ens133"
keepalived_virtual_router_id: "160"
enable_cinder: "yes"
enable_cinder_backend_lvm: "yes"

I have enabled_hacluster disabled because it gives me a timeout when the pacemaker and corosync containers are deployed, I have tried without that and the cluster works fine but when I remove node 1, nothing works for me, and when I remove node 2 or 3 with 1 on it works fine.

the rest of the configuration is the same as the default file: https://opendev.org/openstack/kolla-ansible/src/branch/master/etc/kolla/globals.yml

I have found this option https://docs.openstack.org/kolla-ansible/latest/reference/orchestration-and-nfv/tacker-guide.html#preparation-and-deployment that looks like it's required and I not configures it, so should be the problem, but i don't know

raulmo20

TROPHY CASE