July 2021 - openstack-discuss - lists.openstack.org

cannot import name greenpool
by Pete Zhang 09 Jul '21

09 Jul '21

We are seeing this error in /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync] from eventlet import greenpool ImportError: cannot import name greenpool *glance/greenlet version* sh-4.2# yum list installed | grep -i "eventlet\|glance" openstack-glance.noarch 1:19.0.4-1.el7 @local_openstack-tnrp python2-eventlet.noarch 0.25.1-1.el7 @local_openstack-tnrp python2-glance.noarch 1:19.0.4-1.el7 @local_openstack-tnrp python2-glance-store.noarch 1.0.1-1.el7 @local_openstack-tnrp python2-glanceclient.noarch 1:2.17.1-1.el7 @local_openstack-tnrp *Log* Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: Traceback (most recent call last): Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/bin/glance-manage", line 6, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.cmd.manage import main Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/cmd/manage.py", line 54, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.db.sqlalchemy import alembic_migrations Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/alembic_migrations/__init__.py", line 28, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.db.sqlalchemy import api as db_api Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/api.py", line 46, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.common import utils Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/common/utils.py", line 29, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from eventlet.green import socket Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/eventlet/__init__.py", line 10, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from eventlet import convenience Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/eventlet/convenience.py", line 4, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from eventlet import greenpool Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: ImportError: cannot import name greenpool Error: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]: Failed to call refresh: 'glance-manage db_sync' returned 1 instead of one of [0] Error: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]: 'glance-manage db_sync' returned 1 instead of one of [0] -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[cinder] I have a question about openstack cinder zonemanager driver
by aaaa bbbb 09 Jul '21

09 Jul '21

I am using Brocade FC switch in my OpenStack environment. I have a question about OpenStack cinder zonemanger driver. I find that [fc-zone-manager] can only configure one zone driver. If I want to use two FC switches from different vendors at the same time. One is Brocade FC switch, the other one is Cisco FC switch. Is there a method or solution configure two FC switch zone driver in one cinder.conf ? I want them both to support Zone Manager.

2 1

[kolla] Clean shutdown for guest VMs when host shutdown
by J-P Methot 09 Jul '21

09 Jul '21

Hi, I'm about ready to go into production with kolla, but one small issue remains. On regular Openstack deployments, I would use the libvirt-guests service to ensure that VMs on hosts always shutdown cleanly when the host shuts down. This is to prevent database issues which may happen on guests during forced, unclean shutdowns. At first glance, Kolla doesn't seem to install this service or anything similar that would ensure clean shutdown of guests when the host shuts down. I have found in the github source, in the tools folder, a systemd script that is supposed to do that, but it tries to execute /usr/libexec/libvirt-guests.sh shutdown in the libvirt container, which doesn't exist there. Does Kolla already ensure clean shutdown automatically, or is there a script I'm missing that could make this work?

4 6

[kolla] [kolla-ansible] Multiple external ceph clusters
by Alexandros Soumplis 09 Jul '21

09 Jul '21

Hi all, I am trying to connect Cinder and Manila with a second CEPH cluster and cannot find an "elegant" way to copy a second pair of ceph.conf/ceph_keyring to the running images. I can do it manually or by changing the playbook code, but I was wondering if there is a clean solution that will allow me to do this without touching the base code of kolla-ansible. Thank you in advance for any suggestions! Best, Alexandros

1 0

bird rpm for Openstack Release Train
by Pete Zhang 09 Jul '21

09 Jul '21

Does anyone know which version of bird rpm used by Openstack Release Train and where I can download it? thx. -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[TripleO] Abandoning all open stable/stein and stable/queens patches for EOL
by Marios Andreou 09 Jul '21

09 Jul '21

Hello folks As brought to my attention this morning, we still have some open reviews against stein [1] and queens [2]. Since we have agreed to EOL those branches we should not be merging any new code there (if this is news to you (!) see [3] - EOL patches at [4][5]). I am going to go through and abandon all the patches in [1][2]. If this causes problems for you then please reach out to me ASAP so we can work something out if possible (may be harder for stein, e.g. we'd have to address some broken jobs first). For example, we can try and merge your patch and then resend the EOL patches at [4][5]. Once the patches at [4][5] merge (which is looking pretty close, they have at least one +2 from the release team) then all bets are off we can't merge anything else there. regards, marios [1] https://review.opendev.org/q/(project:%255Eopenstack/.*tripleo.*)AND(status… [2] https://review.opendev.org/q/(project:%255Eopenstack/.*tripleo.*)AND(status… [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023409.html [4] https://review.opendev.org/c/openstack/releases/+/798924 [5] https://review.opendev.org/c/openstack/releases/+/798925

2 3

Increase image upload limit
by open infra 09 Jul '21

09 Jul '21

Hi In a Kubernetes based OpenStack deployment, how to set the value for image_size_cap? Regards Danishka

1 0

[keystone] which CADF events are considered audit logs?
by Bence Romsics 08 Jul '21

08 Jul '21

Hi All, My colleagues working downstream asked me about audit logging, however I did not know enough about it to answer their questions. So let me please phrase their question here: For all other OpenStack components but Keystone they see audit logs in CADF format with event types 'audit.http.request' and 'audit.http.response'. Always separate logs for requests and responses. However from Keystone they also encountered CADF events with event_types like 'identity.user.created', 'identity.user.deleted' or 'identity.authenticate'. Please see an example at the end of my mail. And I guess all examples from https://docs.openstack.org/keystone/latest/admin/event_notifications.html also apply here. They were a bit surprised that these events do not one-by-one correspond to request-responses. So I believe their question is: Do you consider these Keystone events audit logs? Or do you consider them just event logs in CADF format? Or does the answer to this question depend on the object of auditing? Thanks in advance, Bence Romsics keystone/keystone-main.log:188003:<14>2021-06-15T12:51:27.323753+02:00 cic-1.domain.tld keystone-main[14531]: INFO oslo.messaging.notification.identity.user.created [req-8c3fed70-db9c-4f37-a9c5-517491d55246 034a3ac87804494a8d89d32987ff6696 e2fa6412da584f7ebb439d108e1a1185 - default default] {"event_type": "identity.user.created", "timestamp": "2021-06-15 10:51:27.321921", "payload": {"typeURI": http://schemas.dmtf.org/cloud/audit/1.0/event<http://schemas.dmtf.org/cloud/audit/1.0/event>, "initiator": {"typeURI": "service/security/account/user", "host": {"agent": "python-keystoneclient", "address": "192.168.2.124"}, "project_id": "e2fa6412da584f7ebb439d108e1a1185", "user_id": "034a3ac87804494a8d89d32987ff6696", "id": "034a3ac87804494a8d89d32987ff6696"}, "target": {"typeURI": "data/security/account/user", "id": "3dac4a1acaaa4d5598d03b9970d13ce5"}, "observer": {"typeURI": "service/security", "id": "6c15158d525643ea9e40e26b88489b82"}, "eventType": "activity", "eventTime": "2021-06-15T10:51:27.211457+0000", "action": "created.user", "outcome": "success", "id": "c0723c47-f806-54c6-b8b1-14d4e5fdd456", "resource_info": "3dac4a1acaaa4d5598d03b9970d13ce5"}, "priority": "INFO", "publisher_id": "identity.cic-1.domain.tld", "message_id": "2a2adc06-710d-4b11-abdf-2b588a2b8440"}

1 0

[all][tc] OpenStack next release name is final- "OpenStack Yoga"
by Ghanshyam Mann 08 Jul '21

08 Jul '21

Hello Everyone, We have the final name selected for the OpenStack next release name. Its "OpenStack Yoga". As per the release name criteria[1], selection of release name is gone through three steps: Step1: Name nomination from community members[2]. Step2: TC voted on the nominated names[3]. Step3: Trademark checks by Foundation on winners from TC votes. In trademark check, “Yoga” is finalized as the best bet for this release. Thanks community members to participating in name nomination, TC to vote and Foundation for performing the trademark checks. "Yoga" is now good signal to extend our exercise and be more fit in Yoga cycle :) [1] https://governance.openstack.org/tc/reference/release-naming.html#release-n… [2] https://wiki.openstack.org/wiki/Release_Naming/Y_Proposals [3] https://civs1.civs.us/cgi-bin/results.pl?id=E_f065453ffd2537cb -gmann

4 6

[kolla] Date for the release of 10.2.1 ussuri (stable)
by KIM 1 Guy 08 Jul '21

08 Jul '21

Dear all, We are using the ansible kolla with the release 10.2.0. We are planning to upgrade it. So I would like to know when the stable 10.2.1 is released. On 10.2.1 "ussuri" : kolla-ansible (launchpad.net)<https://launchpad.net/kolla-ansible/+milestone/10.2.1>, the release date is not mentioned. Thank you in advance for your answer. Kind regards, Guy KIM This message and any attachments (the "message") is intended solely for the intended addressees and is confidential. If you receive this message in error,or are not the intended recipient(s), please delete it and any copies from your systems and immediately notify the sender. Any unauthorized view, use that does not comply with its purpose, dissemination or disclosure, either whole or partial, is prohibited. Since the internet cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS (and its subsidiaries) shall not be liable for the message if modified, changed or falsified. Do not print this message unless it is necessary, consider the environment. ---------------------------------------------------------------------------------------------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur ou s'il ne vous est pas destine, merci de le detruire ainsi que toute copie de votre systeme et d'en avertir immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de ce message qui n'est pas conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer l'integrite de ce message electronique susceptible d'alteration, BNP Paribas (et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese ou il aurait ete modifie, deforme ou falsifie. N'imprimez ce message que si necessaire, pensez a l'environnement.

2 1