<html><body><div><div>Hi,<br></div><div><br></div><div>just a quick update. I deployed a rocky 9 vm in my openstack kolla-ansible test environment, ran bootstrap and deployed it as a compute node but there is one container that is listed as unhealthy:<br></div><div><br></div><div>(yoga) [vagrant@seed ~]$ ssh compute05 -l vagrant "sudo docker ps -a"<br></div></div><div>vagrant@compute05's password:<br></div><div>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES<br></div><div>3701de0c77e7 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-openvswitch-vswitchd:yoga">openstack.kolla/centos-source-openvswitch-vswitchd:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours (healthy) openvswitch_vswitchd<br></div><div>083e04ae0fcb 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-openvswitch-db-server:yoga">openstack.kolla/centos-source-openvswitch-db-server:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours (unhealthy) openvswitch_db<br></div><div>17a156ff5352 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-nova-compute:yoga">openstack.kolla/centos-source-nova-compute:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours (healthy) nova_compute<br></div><div>12d308adf9ce 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-nova-libvirt:yoga">openstack.kolla/centos-source-nova-libvirt:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours (healthy) nova_libvirt<br></div><div>cc35631ec420 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-nova-ssh:yoga">openstack.kolla/centos-source-nova-ssh:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours (healthy) nova_ssh<br></div><div>ad688dec24c8 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-prometheus-libvirt-exporter:yoga">openstack.kolla/centos-source-prometheus-libvirt-exporter:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours prometheus_libvirt_exporter<br></div><div>02e52983458c 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-prometheus-cadvisor:yoga">openstack.kolla/centos-source-prometheus-cadvisor:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours prometheus_cadvisor<br></div><div>878a6eb1bb42 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-prometheus-node-exporter:yoga">openstack.kolla/centos-source-prometheus-node-exporter:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours prometheus_node_exporter<br></div><div>25faaf319f8a 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-cron:yoga">openstack.kolla/centos-source-cron:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours cron<br></div><div>efd1cc64967c 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-kolla-toolbox:yoga">openstack.kolla/centos-source-kolla-toolbox:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours kolla_toolbox<br></div><div>822876acf7c2 172.28.7.140:4000/<a rel="noopener noreferrer" href="http://openstack.kolla/centos-source-fluentd:yoga">openstack.kolla/centos-source-fluentd:yoga</a> "dumb-init --single-…" 46 hours ago Up 46 hours fluentd<br></div><div><br></div><div>To rule out that there is a general issue I deployed another rocky 8 and this worked just fine.<br></div><div><br></div><div>Also the compute services look just fine:<br></div><div><br></div><div>(yoga) [vagrant@seed ~]$ openstack compute service list<br></div><div>+--------------------------------------+----------------+-----------+----------+---------+-------+----------------------------+<br></div><div>| ID | Binary | Host | Zone | Status | State | Updated At |<br></div><div>+--------------------------------------+----------------+-----------+----------+---------+-------+----------------------------+<br></div><div>| 3acd5340-4c79-4844-a321-ef3ac73602c5 | nova-scheduler | control01 | internal | enabled | up | 2023-01-13T14:46:10.000000 |<br></div><div>| e289aef6-a3fa-402f-80e3-6bbd7807ae43 | nova-scheduler | control03 | internal | enabled | up | 2023-01-13T14:46:12.000000 |<br></div><div>| 06d6ce7f-907d-4fe1-92bc-611511d7ce01 | nova-scheduler | control02 | internal | enabled | up | 2023-01-13T14:46:08.000000 |<br></div><div>| b5051a46-ca04-4dbb-9067-75091fe26cfe | nova-conductor | control01 | internal | enabled | up | 2023-01-13T14:46:08.000000 |<br></div><div>| e3e0a17f-b445-44b7-8355-972754ab397f | nova-conductor | control02 | internal | enabled | up | 2023-01-13T14:46:09.000000 |<br></div><div>| 293b8e26-48de-4656-97a6-2c7020d19e44 | nova-conductor | control03 | internal | enabled | up | 2023-01-13T14:46:04.000000 |<br></div><div>| c007e4a5-bee9-4428-8494-5f2cdddaec91 | nova-compute | compute01 | nova | enabled | up | 2023-01-13T14:46:08.000000 |<br></div><div>| 62615300-dbee-4337-bc81-c956377abee9 | nova-compute | compute02 | nova | enabled | up | 2023-01-13T14:46:07.000000 |<br></div><div>| a497d03a-6de8-418f-94a2-8b610babf48b | nova-compute | compute03 | nova | enabled | up | 2023-01-13T14:46:12.000000 |<br></div><div>| cbdbd319-77e2-4d98-aeee-f3e65d7d8d00 | nova-compute | compute04 | nova | enabled | up | 2023-01-13T14:46:10.000000 |<br></div><div>| 56e126e5-ddd5-4b4d-94d6-dff2cf850ddb | nova-compute | compute05 | nova | enabled | up | 2023-01-13T14:46:06.000000 |<br></div><div>+--------------------------------------+----------------+-----------+----------+---------+-------+----------------------------+<br></div><div><br></div><div>I manually restarted the unhealthy container but it stays unhealthy. So I just spun up a couple cirros instances. Then I associated a FIP to the one that was scheduled on the rocky 9 compute node and tried to ping it and it doesn't work.<br></div><div><br></div><div>Would be good to get some info on how to perform the upgrade.<br></div><div><br></div><div>Cheers,<br></div><div>Oliver<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><div><br></div><blockquote type="cite"><div>On Jan 8, 2023, at 9:56 PM, Oliver Weinmann <oliver.weinmann@me.com> wrote:<br></div><div><br></div><div><br></div><div><div><div>Hi,<br></div><div><br></div><div>That is a good question. I’m also running yoga on rocky 8 and due to some problems with yoga I would like to upgrade to zed too soon. I have created a very simple staging deployment on a single ESXi host with 3 controllers and 2 compute nodes with the same config that I use in the production cluster. This lets me try the upgrade path. I assume while there is the possibility to upgrade from rocky 8 to 9, I wouldn’t do that. Instead I would do a fresh install of rocky9. I can only think of the docs not being 100% accurate and you can run yoga on rocky9 too. I will give it a try.<br></div><div><br></div><div>Cheers,<br></div><div>Oliver<br></div><div><br></div><div>Von meinem iPhone gesendet<br></div><div><br></div><blockquote type="cite"><div>Am 08.01.2023 um 10:25 schrieb wodel youchi <wodel.youchi@gmail.com>:<br></div><div><br></div><div><br></div><div>Hi,<br></div><div><br></div><div>Reading the kolla documentation, I saw that Yoga is supported on Rocky 8 only and Zed is supported on Rokcy 9 only, how to do the upgrade from Yoga to Zed since we have to do OS upgrade also???<br></div><div><br></div><div>Regards.<br></div></blockquote></div></div></blockquote></div><div><br></div></body></html>