- openstack-discuss - lists.openstack.org

beginning with [masakari]
by Shubham Kumar Yadav 04 Jan '24

04 Jan '24

Hi, i have recently started working on Masakari (kubernetes in openstack) so i wanted some help with it please i was trying to test the masakari-instance-monitor & masakari-host-monitor but having trouble with it. i have created a pacemaker remote cluster (with pacemaker & corosync on controller nodes and pacemaker remote on compute node). *pcs statusCluster name: lab-clusterCluster Summary: * Stack: corosync * Current DC: lab-11053-26006-ceph-2 (version 2.1.2-ada5c3b36e2) - partition with quorum * Last updated: Thu Dec 14 08:41:41 2023 * Last change: Thu Dec 14 08:41:22 2023 by root via cibadmin on lab-11053-26006-ceph-1 * 6 nodes configured * 3 resource instances configuredNode List: * Online: [ lab-11053-26006-ceph-1 lab-11053-26006-ceph-2 lab-11053-26006-ceph-3 ] * RemoteOnline: [ lab-11053-26006-comp-1.cluster.local lab-11053-26006-comp-2.cluster.local lab-11053-26006-comp-3.cluster.local ]Full List of Resources: * lab-11053-26006-comp-1.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-1 * lab-11053-26006-comp-2.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-2 * lab-11053-26006-comp-3.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-3Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled* i have also created segment and added segment hosts(computes) in it. when i tried to test the masakari host monitor by manually powering off the compute node, masakari should move the vms from powered off computes to some running compute but after the compute is powered off vms still remains on the powered off compute. Am i missing some conf? is there any need to add some conf in nova and keystone too? *in masakari engine logs i see host_failure.evacuate_all_instances = Trueinstance_failure.process_all_instances = Falsehost_failure.add_reserved_host_to_aggregate = Falsehost_failure.ha_enabled_instance_metadata_key = HA_Enabled log_opt_valueshost_failure.ignore_instances_in_error_state = Falsehost_failure.service_disable_reason = Masakari detected host failed.* and i get below error when i turn off an instance on the compute, logs are from masakari-instance-monitor *2024-01-03 13:01:15.574 1 DEBUG openstack.resource [-] Attribute [] not found in [<openstack.resource._ComponentManager object at 0x7fa051f48730>]: ''. __getattribute__ /var/lib/openstack/lib/python3.8/site-packages/openstack/resource.py:6222024-01-03 13:01:15.595 1 WARNING masakarimonitors.ha.masakari [-] Retry sending a notification. (BadRequestException: 400: Client Error for url: http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4… <http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4…>, Host with name lab-11053-26006-cmp-1 could not be found.): openstack.exceptions.BadRequestException: BadRequestException: 400: Client Error for url: http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4… <http://masakari-api.openstack.svc.cluster.local:15868/v1/9db00e10af034fc6a4…>, Host with name lab-11053-26006-cmp-1 could not be found.* (do i need to create some masakari notifications for it to work in openstack? if yes how may i do it) below i have attached the logs from masakari-hostmonitor and masakari-engine and also some components which i created in openstack about masakari do you have any suggestion please let me know! Thank You

2 1

[magnum][cluster-api] Why magnum creating bunch of users
by Satish Patel 04 Jan '24

04 Jan '24

Folks, I have deployed Magnum-CAPI for testing and things working fine but just noticed magnum creating a bunch of users and have no idea what they are those for? This list is small in real I have 100s of them. is this normal? # openstack user list +----------------------------------+-----------------------------------------------------------------------+ | ID | Name | +----------------------------------+-----------------------------------------------------------------------+ | 01ff85efed43419486558864e35f39cf | 90e763f2-c566-4c1f-92f0-e36be5933538_08cae850a5bb47d998da180a7f0e2660 | | bd8c2337df0a451da92732aae1fe5f68 | abf42808-d67c-450e-88e0-a20e65f35232_08cae850a5bb47d998da180a7f0e2660 | | 81d6c4c23bd84d62ab3422f109ced3d5 | ee1b8a35-d23b-42eb-9574-edb6562b4147_08cae850a5bb47d998da180a7f0e2660 | | 988550004ee3413eba2bb20f73f24013 | 8eaf2db3-d13c-4849-a517-5528219fc32f_08cae850a5bb47d998da180a7f0e2660 | | a50a0b596a024edb8c4a9bae05d1844c | e7194788-4ae5-4e17-9c48-fa3bf4e65016_08cae850a5bb47d998da180a7f0e2660 | | 664e7708f64f4b9d8071dac8d9fc580f | ea999930-8d10-42b2-ae31-2236fffb07a1_08cae850a5bb47d998da180a7f0e2660 | | 67de8c5761564fdbba998cc7c2a14948 | 0ef17525-9ee5-4416-b3bc-f6ccd5a1f3b0_08cae850a5bb47d998da180a7f0e2660 |

2 2

[magnum] magnum-capi management cluster controle plane in HA
by Satish Patel 04 Jan '24

04 Jan '24

Folks, In the lab I have deployed a magnum-capi driver with a single node kind cluster and it works great. Now I want to take it to production and make sure my capi management cluster runs on a HA environment of k8s and survives all kinds of failure. I have deployed 3 node k8s using kubespray and deployed CAPI applications on top of it using clusterctl init command but it default created a replica of 1/1 for all pods. How do I tell clusterctl to create a replica with 3 for HA and how does data replication work? How do I take backup/restore of data in k8s cluster using clusterctl for disaster recovery? I have checked official documents but it's a little confusing so I'm asking question here to clear my doubts. Cheers! ~S

3 6

Re: [kolla-ansible][magnum] question
by Oliver Weinmann 03 Jan '24

03 Jan '24

Hi Franck, Great. Glad it works. That is the k8s version and the url where magnum will pull the container from. The official docs are quite helpful. In the latest Openstack release bobcat there is already some support for CAPI. It is not 100% working out of the Box but it looks very promising. I have taken my blog post offline since I didn’t manage to get it working. But I will look into it again in the next couple of days. Cheers, Oliver Von meinem iPhone gesendet > Am 03.01.2024 um 12:21 schrieb Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr>: > > Hi Oliver, > and thanks a lot for your help. > I followed the instructions on the blog and indeed, with [trust] it works. > I'm trying to understand everything. what are the parameters for: > > --labels kube_tag=v1.21.11-rancher1,hyperkube_prefix=docker.io/rancher/ > > Thanks in advance > > Franck > > > >> Le 25 déc. 2023 à 19:26, Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr> a écrit : >> >> Hi Oliver and thanks you for this help. >> >> I was wrong in my explications. >> I had seen this article (roksblog.de ) and I did what it said: >> I first tried: >> enable_cluster_user_trust = True in globals.yml >> It didn't work. >> >> I then made the modification in /etc/kolla/config/magnum.conf: >> cluster_user_trust = True >> >> Same problem. >> >> That's why I asked the question. Is this really the way to do it? >> If so, I will have to restart the containers (keystone?) >> >> Franck >> >> >> >>> Le 25 déc. 2023 à 18:40, Oliver Weinmann <oliver.weinmann(a)me.com> a écrit : >>> >>> Hi Frank, >>> >>> According to the official kolla docs the option needs to be in globals.yml >>> >>> Ensure that you understand the consequences before enabling this option. Inglobals.yml: >>> >>> In case this also doesn’t work, you can try: >>> >>> yoga) [vagrant@seed ~]$ cat /etc/kolla/config/magnum.conf >>> [trust] >>> cluster_user_trust = True >>> >>> *www.roksblog.de >>> >>> Cheers, >>> Oliver >>> >>> Von meinem iPhone gesendet >>> >>>> Am 25.12.2023 um 18:10 schrieb Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr>: >>>> >>>> enable_cluster_user_trust = True >> >

1 0

New OpenStack machine on new node not responding
by kjme001＠gmail.com 02 Jan '24

02 Jan '24

hello, I added a new node to OpeStack. I can create a new instance on it. The instance creates itself without error, its IP address is assigned. But however, the connection over ssh to this new machine does not work for me, nor does ping. I have the network traffic passed, what else can I check why the new machine is not responding to me network-wise regards

1 0

[neutron] Bug deputy report (last week of 2023)
by Bernard Cafarelli 02 Jan '24

02 Jan '24

Hey neutrinos, and happy new year! Here is the bug reported between 2023-12-25 and 2023-12-31 (as per tradition, it was a quiet week) The firewall group is ACTIVE without associate with a router or any firewall policies - https://bugs.launchpad.net/neutron/+bug/2047325 neutron-fwaas bug, patch proposed: https://review.opendev.org/c/openstack/neutron-fwaas/+/904317 Best wishes -- Bernard Cafarelli

1 0

ceilometer cli client install help
by garcetto 31 Dec '23

31 Dec '23

good afternoon, i have a running kolla-ansible openstack all-in-one cluster, so far so good (zed version based on ubuntu). i have installed ceilometer, and then i am trying to use this command to show metrics, but seems i cannot find the right command option, what am i missing? " (my-virt-env) marcello@mg-ostack-119:~$ openstack metric resource list openstack: 'metric resource list' is not an openstack command. See 'openstack --help'. Did you mean one of these? service create service delete service list service provider create service provider delete service provider list service provider set service provider show service set service show " thank you.

3 2

[kolla] ceilometer and nova compute agent
by garcetto 31 Dec '23

31 Dec '23

good morning, i would like to measure instances metrics but i cannot understand if i need to add this package on nova containers or the apt package is already installed (or do i need to create a custom nova container?) https://docs.openstack.org/ceilometer/latest/install/install-compute-ubuntu… thank you.

3 2

Trove installation filed
by Tamim Wasif 31 Dec '23

31 Dec '23

Hello openstack team I can not install openstack database service Trove. its some times showing this error "No valid host was found" "polling request timed out" "can not create volume for instance ..." what can be the solution? from Tamim Wasif Software Engineer Teton Private limited

3 2

[trove][victoria] can't connect to trove DB from outside - although ssh to the trove instance works
by ddorra＠t-online.de 31 Dec '23

31 Dec '23

Hello, I can't connect to to my trove mysql DB from an instance in a selfservice network. Strange thing is I CAN connect to the trove instance via ssh: ubuntu@dozbox2:~$ telnet 192.168.0.176 22 Trying 192.168.0.176... Connected to 192.168.0.176. Escape character is '^]'. SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.7 But I CANNOT reach the DB port from on the troave instance: ubuntu@box2:~$ telnet 192.168.0.176 3306 Trying 192.168.0.176... telnet: Unable to connect to remote host: No route to host Within the Trove instance I CAN work with the client... root@ms3:/var/log/trove# mysql -h 192.168.0.176 -u dbadmin -p -P 3306 Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 331 The security group for that trove instance allows ssh AND 3306 (see additional infos/rules below). Any help is really appreciated! ------- Additional Infos ------------------ root@voscontrol:~# openstack server show 534fe146-0d51-4848-98ed-95dc9aaf89b1 +-------------------------------------+------------------------------------------------------------------+ | Field | Value | +-------------------------------------+------------------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | voscompute2 | | OS-EXT-SRV-ATTR:hypervisor_hostname | voscompute2 | | OS-EXT-SRV-ATTR:instance_name | instance-000000d0 | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2023-12-18T23:05:15.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | doznet=192.168.0.176; trovemgmt=10.10.10.134 | | config_drive | True | | created | 2023-12-18T23:04:59Z | | flavor | m1.large (72a7e41e-e0e9-48fe-abc2-8c64838e9e4a) | | hostId | 618af9a8f27a256f291621d611d30ae2186de8c2e8fa03e5a5ba2081 | | id | 534fe146-0d51-4848-98ed-95dc9aaf89b1 | | image | trove-guest-ubuntu-bionic (773aeec6-9caa-48a3-a80a-f9bf440b0d9e) | | key_name | trovekey | | name | ms3 | | progress | 0 | | project_id | d2e35c5479c441dc9ba4dba8e9b914bc | | properties | | | security_groups | name='trove_sg-27547af3-9bb0-4df5-b4ff-e85daa72c6ef' | | | name='default' | | status | ACTIVE | | updated | 2023-12-18T23:05:15Z | | user_id | a72e578837da479895fe4207107ca2fa | | volumes_attached | id='bff9037e-2831-473b-b6ae-8027ee4053dc' | +-------------------------------------+------------------------------------------------------------------+ root@voscontrol:~# openstack security group show trove_sg-27547af3-9bb0-4df5-b4ff-e85daa72c6ef +-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-----------------+----------------------------------------------------------------------------------- | created_at | 2023-12-18T23:04:51Z | description | Security group for trove instance 27547af3-9bb0-4df5-b4ff-e85daa72c6ef | id | d73ff24a-5288-486b-b10b-fe9902f80e15 | name | trove_sg-27547af3-9bb0-4df5-b4ff-e85daa72c6ef | project_id | d2e35c5479c441dc9ba4dba8e9b914bc | revision_number | 3 | rules | created_at='2023-12-18T23:04:52Z', direction='ingress', ethertype='IPv4', id='0484ddff-c945-45d0-b271-7d30e7fbf619', port_range_max='3306', port_range_min='3306', protocol='tcp', remote_ip_prefix='0.0.0.0/0', updated_at='2023-12-18T23:04:52Z' | | | created_at='2023-12-18T23:04:51Z', direction='egress', ethertype='IPv6', id='27ed1225-984a-454e-86da-656de3669038', updated_at='2023-12-18T23:04:51Z' | | | created_at='2023-12-18T23:10:33Z', direction='ingress', ethertype='IPv4', id='c2c7c390-8b13-4b00-ab7c-0a8a7687ac08', port_range_max='22', port_range_min='22', protocol='tcp', remote_ip_prefix='0.0.0.0/0', updated_at='2023-12-18T23:10:33Z' | | | created_at='2023-12-18T23:04:51Z', direction='egress', ethertype='IPv4', id='d1fdc662-fc24-46bd-80db-3aca725f96aa', updated_at='2023-12-18T23:04:51Z' | | stateful | True | tags | [] | updated_at | 2023-12-18T23:10:33Z +---------------------------------------------------------------------------------------------+

4 8