June 2024 - openstack-discuss - lists.openstack.org

Regarding Cinder- Volume error in OpenStack-ansible
by Adivya Singh 24 Jun '24

24 Jun '24

Hi Team, I am trying to configure the Cinder Volume service with NFS server as a backend and this is my user_variables File cinder_backends: default: volume_backend_name: nfs volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_shares_config: /etc/cinder/nfs_shares nfs_qcow2_volumes: true nfs_mount_options: vers=4,nfsvers=4,noatime,rw,bg,intr,async,timeo=60 nfs_snapshot_support: true shares: - ip: 172.29.244.103 share: /cinder/volume My NFS server Configuration is Like this /img/glance 172.29.244.0/22(rw,insecure,sync,no_subtree_check,no_root_squash) /cinder/volume 172.29.244.0/22(vrw,insecure,sync,no_subtree_check,no_root_squash) now what i am seeing is below error 2024-06-24 08:11:42.892 4807 ERROR cinder.volume.drivers.remotefs [None req-85e0d72a-f403-4c8e-8880-1ced0413f760 - - - - - -] Exception during mounting NFS mount failed for share 172.29.244.103:/cinder/volume. Error - {'nfs': "Unexpected error while running command.\nCommand: sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs -o vers=4,nfsvers=4,noatime,rw,bg,intr,async,timeo=60 172.29.244.103:/cinder/volume /var/lib/cinder/mnt/cd53d1ffa6d608fee908e8f1668ce63d\nExit code: 32\nStdout: ''\nStderr: 'mount.nfs: multiple version options not permitted\\n'"}: cinder.exception.NfsException: NFS mount failed for share 172.29.244.103:/cinder/volume. Error - {'nfs': "Unexpected error while running command.\nCommand: sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs -o vers=4,nfsvers=4,noatime,rw,bg,intr,async,timeo=60 172.29.244.103:/cinder/volume /var/lib/cinder/mnt/cd53d1ffa6d608fee908e8f1668ce63d\nExit code: 32\nStdout: ''\nStderr: 'mount.nfs: multiple version options not permitted\\n'"} Any clue on this, How to fix it Regards Adivya Singh

2 1

PTG October 2024 Team Signup
by Kendall Nelson 24 Jun '24

24 Jun '24

Hello Everyone, Hopefully you have seen by now, the next OpenInfra PTG[1] which will take place October 21-25, 2024 virtually! Registration is now open[2]! To sign up your team, you must complete the survey[3] by August 30th at 7:00 UTC. We NEED accurate contact information (email and IRC nickname ideally) for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[4] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.dev! Information about signing up for time slots will be sent to moderators after the team signup deadline. Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] PTG Registration: http://ptg.openinfra.dev/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2024_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

[CloudKitty] query regarding ElasticSearch usage
by Rafael Weingärtner 21 Jun '24

21 Jun '24

Hello OpenStack community and users of CloudKitty! There have been some discussions in our bi-weekly meetings and vPTG meetings regarding the deprecation and removal of ElasticSearch support as a storage backend. Therefore, this e-mail is to consult/query users regarding ElasticSearch users. If there are no people using it anymore with CloudKitty, we are considering the alternative of removing it and maintaining only the OpenSearch support. We would like to hear back from you guys. Let me know if you are using ElasticSearch, and if you intend to stick with it. Also, do you guys feel the need to improve something in its support in CloudKitty. Thanks in advance for your feedback! -- Rafael Weingärtner

4 4

[kuryr][tc] Final call for Kuryr PTL/DPL liaisons
by Ghanshyam Mann 21 Jun '24

21 Jun '24

Hello Everyone, Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945 If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945. [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… -gmann

3 6

[barbican][openstack-helm][tacker] Request to Include Barbican Installation Guide in OpenStack-Helm Documentation
by JUSO WATARU(十楚　航) 21 Jun '24

21 Jun '24

Hello, We are presently in the process of enhancing the official OpenStack-Helm documentation by including a procedural guide for deploying Tacker using helmchart. Through discussions with members of the openstack-helm community, it has been emphasized that Barbican is an indispensable component for Tacker. Hence, it would be highly beneficial for users to have comprehensive instructions for installing Barbican with helmchart included in the official OpenStack-Helm documentation [1]. Consequently, we suggest that the Barbican community integrate the installation guide for the Barbican component into the official OpenStack-Helm documentation. This addition is poised to significantly enhance the clarity and accessibility of deployment procedures for users. We eagerly welcome your opinions and feedback on this proposal, as we aim to ensure that the documentation for openstack deployment with helmchart meets the needs of our community. [1] https://docs.openstack.org/openstack-helm/latest/install/openstack.html Regards, Wataru

2 2

[nova] Cannot (live)migrate due to host mismatch?
by sinan86polat＠gmail.com 20 Jun '24

20 Jun '24

Hello, When I try to live migrate a VM and specify a target host, I am getting the following: $ openstack server migrate <id> --live --os-compute-api-version 2.30 --host hypervisor-05 No valid host was found. There are not enough hosts available. (HTTP 400) (Request-ID: req-bee8f8b1-7218-4ae7-aa71-c4e5a3a84ba5) And the following is logged in nova-scheduler: No hosts matched due to not matching requested destination (hypervisor-05, hypervisor-05.sub.domain.com) When I do "openstack hypervisor list" I see my hypervisors with its fqdn (hypervisor-05.sub.domain.com). So, it might be a mismatch in the nova database? How do I verify and correct it?

2 2

[qa] Cancel office hour on odd weeks
by Martin Kopec 20 Jun '24

20 Jun '24

Hi everyone, I'm going to cancel office hours every odd week, at least during the summer, due to a small attendance. Office hours will be held biweekly every Tuesday (even weeks) at 15:00 UTC. The other time slot we had, Wednesday biweekly at 17:00 UTC (odd weeks), is cancelled for now. Thank you, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[swift][ceph][radosgw] Swift container create error
by Jaime Ibar 20 Jun '24

20 Jun '24

Hi all, I'm setting up swift support but using radosgw dropin replacement. I have configured the following in ceph.conf rgw keystone api version = 3 rgw keystone url = https://keystone/v3 rgw keystone admin project = service rgw keystone admin domain = default rgw keystone service token enabled = true rgw keystone accepted roles = member, _member_, admin, swiftoperator rgw keystone implicit tenants = true rgw enable apis = swift, s3 rgw s3 auth use keystone = true but I'm getting the following error when creating a container > openstack container create test Unauthorized (HTTP 401) Does anyone what I'm missing? TIA Jaime -- salu2 Jaime

2 2

[openstack-ansible] [masakari]
by Budai Laszlo 19 Jun '24

19 Jun '24

Dear All, I'm evaluating Masakari for instance HA and I need to install it using openstack-ansible. I'm doing it initially in a small test cluster (3 controller, and 3 compute). The install went trough and now when I'm checking the status of the corosync cluster I see the following: root@worker1:~# crm_mon -1 Cluster Summary: * Stack: corosync * Current DC: worker2 (version 2.1.2-ada5c3b36e2) - partition with quorum * Last updated: Wed Jun 19 16:02:01 2024 * Last change: Wed Jun 19 15:29:37 2024 by hacluster via crmd on worker2 * 3 nodes configured * 0 resource instances configured Node List: * Online: [ worker1 worker2 worker3 ] Active Resources: * No active resources root@worker1:~# is it normal that there are no resources configured? What about the fencing, how should I configure it? Are you aware of any documentation where I could find mori info about configuring fencing (especially in the context of openstack-ansible)? Thank you for any advice. Kind regards, Laszlo

3 5

Re: [neutron] ovs: multiple rows in Manager patch
by Brian Haley 19 Jun '24

19 Jun '24

Just sending response to the list in case anyone else has the same issue. On 6/17/24 1:09 PM, stream_unpicked390(a)simplelogin.com wrote: > Hi, > > On 6/13/24 21:38, Brian Haley - haleyb.dev(a)gmail.com wrote: >> Hi, >> >> On 6/13/24 4:53 AM, stream_unpicked390(a)simplelogin.com wrote: >>> Hi Brian, >>> On 6/12/24 23:04, Brian Haley - haleyb.dev(a)gmail.com wrote: >>>> Hi, >>>> >>>> On 6/12/24 12:43 PM, stream_unpicked390(a)simplelogin.com wrote: >>>>> Hi everyone! >>>>> >>>>> this is my first time on a mailing list, so please excuse any >>>>> "obvious" mistakes and feel free to correct me :) >>>>> >>>>> I'm currently setting up a minimal OpenStack system manually on one >>>>> server. The setup is nearly complete but I'm running into issues >>>>> with neutron. After fully completing the neutron setup as mentioned >>>>> in the docs, the neutron-ovs-service refuses to start, showing the >>>>> error message >>>> >>>> Sorry, but I have to ask which "docs" are you using? >>> >>> thanks for your quick answer! I followed the OpenStack install guide >>> under https://docs.openstack.org/2024.1/install/. For neutron >>> specifically, I used the document linked under >>> https://docs.openstack.org/neutron/2024.1/install/install-ubuntu.html. >>> >>> As I mentioned, I'm currently setting up everything on just one >>> server, the documentations scenario describes two servers. This is >>> the only intentional diversion I made from the docs. I've been trying >>> to setup a self-service network. >>> >>>> I don't see ptcp used in any of the examples here for ovsdb_connection: >>>> >>>> https://docs.openstack.org/neutron/latest/install/ >>> >>> I couldn't find any example of the ovsdb_connection and I don't >>> remember modifying any value like that either. The problem existed >>> "right out of the box". Can you point me to the part of the linked >>> documentation where the ovsdb_connection config is discussed? >> >> Instead of trying to go through the details of anything that might be >> wrong, if you are just trying to get a single-node Openstack running >> have you tried using devstack [0]? It would be much simpler if this is >> just for testing purposes. > This is a production setup so devstack was out of the question. Because > of our very tight constraints, we first have to set up a single node, > before being able to add additional servers. Definitely not ideal.. Your > hint about ovsdb_connection helped me out! While I couldn't find any > setting with the name ovsdb_connection already set to an, apparently > wrong, string, I set ovsdb_connection to the value mentioned by you. > This probably overwrote something I couldn't find, because after > restarting neutron, my issues were gone! Thanks again for looking into > my issue and guiding me on the right path! Glad it worked out, thanks for responding. -Brian >> [0] https://github.com/openstack-dev/devstack.git >> >>>>> multiple rows in Manager patch "ptcp:6640:127.0.0.0" >>>> >>>> Two things look wrong here, both the IP address and port. Typically >>>> this string would be "ptcp:127.0.0.1:6640" or "ptcp:0.0.0.0:6640" in >>>> ml2_conf.ini. >>> >>> Thanks! I will try to take a look at the aforementioned config as >>> soon as possible and report back! >>> >>>> >>>> -Brian >>>> >>>>> I dumped the ovs database which only shows one row in the Manager >>>>> table. After many days of debugging and googleing I'm out of ideas >>>>> how this could be solved.. >>>>> I already posted this issue on serverfault >>>>> (https://serverfault.com/questions/1160418/openstack-ovs-multiple-rows-in-ma…), only after that post finding this mailing list! >>>>> >>>>> Best regards >>>>> Talooola >>>>> >>>> >>

1 0