October 2020 - openstack-discuss - lists.openstack.org

vPTG Oct 2020 Registration & Schedule
by Kendall Nelson 09 Oct '20

09 Oct '20

Hey everyone, The October 2020 Project Teams Gathering is right around the corner! The official schedule has now been posted on the PTG website [1], the PTGbot has been updated[2], and we have also attached it to this email. Friendly reminder, if you have not already registered, please do so [3]. It is important that we get everyone to register for the event as this is how we will contact you about tooling information/passwords and other event details. Please let us know if you have any questions. Cheers, The Kendalls (diablo_rojo & wendallkaters) [1] PTG Website www.openstack.org/ptg [2] PTGbot: http://ptg.openstack.org/ptg.html [3] PTG Registration: https://october2020ptg.eventbrite.com

5 7

OpenStack Ironic Issue
by Akshay 346 09 Oct '20

09 Oct '20

Hello Team, I hope you all are good. I am using openstack ironic deployment and have some issues and some observations. These are: Issue: At the time of "openstack server create" for launching baremetal node, I came across the following multiple observations: - Sometimes when I launch baremetal node on openstack, after one time pxe booting, the baremetal node goes down again and then comes up and goes into second time booting and gets stuck there in "Probing" state ( Seen on node's console) BUT according to openstack horizon, it is up and running and according to "openstack baremetal node show", it is in "Active" state. - And sometimes when i launch baremetal node on openstack, after one time pxe booting, the baremetal node goes down again and then comes up, the "spawning" state on openstack horizon goes into ERROR. Error seen in "nova-compute-ironic-0" container is : "ERROR nova.compute.manager [instance: edd447c6-12ac-49ba-b0bc-f419aff4892a] nova.exception.InstanceDeployFailure: Failed to provision instance edd447c6-12ac-49ba-b0bc-f419aff4892a: Timeout reached while waiting for callback for node 75210cc4-ad98-442d-ace1-89ce69467580" - The baremetal node always takes near about 2 hours to be in "available" state from "cleaning" and "clean-wait". Is it correct behaviour ? Please guide me how to resolve this. Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

3 2

[tripleo][ptg] Wallaby PTG timezone - 1300-1700 UTC
by Marios Andreou 09 Oct '20

09 Oct '20

Hi folks, Unless there is disagreement and we can find a better time that suits all, the current plan is to use the same timezone as we had in the last virtual PTG - that is 1300-1700 UTC ( https://etherpad.opendev.org/p/tripleo-ptg-wallaby ). Please speak up if you would like to propose and discuss an alternative thanks, marios

1 0

[tripleo][ptg] PTG reminder please add topics this week
by Marios Andreou 09 Oct '20

09 Oct '20

Hi tripleo friends, reminder: PTG is coming 26th October - if you'd like to discuss something there please add topics at https://etherpad.opendev.org/p/tripleo-wallaby-topics - at the moment it doesn't look like we'll need more than the first day to cover what we have there. Ideally I'd like to socialise a tentative schedule at the end of next week so we can make changes depending on folks availability. thanks for your help, marios

1 0

[tempest][nova][interop] Deletion of test_reboot_server_soft from Tempest
by Martin Kopec 09 Oct '20

09 Oct '20

Hello, we'd like to inform you that we are going to remove the following compute test by this commit [1]: test_reboot_server_soft with id 4640e3ef-a5df-482e-95a1-ceeeb0faa84d The reasons are: - Nova has switched to hard reboot if the guest is not responding, there is no way to see the difference from the API - minimum scenario test uses soft reboot and the nova functional test also covers reboot - the test has been skipped on Tempest side for more than 6 years - the test is not part of any latest guideline of interop [2] [1] https://review.opendev.org/#/c/647718 [2] http://codesearch.openstack.org/?q=test_reboot_server_soft&i=nope&files=&re… Please let us know in case of any objection on this test removal. Regards, -- Martin Kopec Software Quality Engineer Red Hat EMEA <https://www.redhat.com> <https://red.ht/sig>

1 0

[cloudkitty] Core team cleanup
by Pierre Riteau 09 Oct '20

09 Oct '20

Hello, In the cloudkitty-core team there is zhangguoqing, whose email address (zhang.guoqing(a)99cloud.net) is bouncing with "551 5.1.1 recipient is not exist". I propose to remove them from the core team. zhangguoqing, if you read us and want to stay in the team, please contact me. Best wishes, Pierre Riteau (priteau)

2 5

help with Openstack magnum in train
by Robert Duncan 09 Oct '20

09 Oct '20

Hi, I have openstack train deployed by kolla-ansible and am trying to deploy a k8s cluster on Fedora Atomic 27 with magnum it seems there is no podman binary in the Atomic 27 image specifically, Fedora-Atomic-27-20180419.0.x86_64.qcow2 I have set the label use_podman=false however, the template seems to ignore that which results in this error in the heat agent log: WARNING Attempt 12: Trying to install kubectl. Sleeping 5s * i=12 * '[' 12 -gt 60 ']' * echo 'WARNING Attempt 12: Trying to install kubectl. Sleeping 5s' * sleep 5s * ssh -F /srv/magnum/.ssh/config root@localhost '/usr/bin/podman run --entrypoint /bin/bash --name install-kubectl --net host --privileged --rm --user root --volume /srv/magnum/bin:/host/srv/magnum/bin k8s.gcr.io/hyperkube:v1.15.7<http://k8s.gcr.io/hyperkube:v1.15.7> -c '''cp /usr/local/bin/kubectl /host/srv/magnum/bin/kubectl'''' bash: /usr/bin/podman: No such file or directory [fedora@test-quznqfqfa5ld-master-0 ~]$ which podman /usr/bin/which: no podman in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/fedora/.local/bin:/home/fedora/bin) I have tried a later version of atomic but the dependencies are closely coupled and it seems I must use version 27 - what am I missing? I'm following along with the Train documentation https://docs.openstack.org/magnum/train/install/launch-instance.html and was able to deploy a docker swarm cluster. thanks, Rob. ________________________________ The information contained and transmitted in this e-mail is confidential information, and is intended only for the named recipient to which it is addressed. The content of this e-mail may not have been sent with the authority of National College of Ireland. Any views or opinions presented are solely those of the author and do not necessarily represent those of National College of Ireland. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. If you have received this communication in error, please delete the e-mail and destroy all record of this communication. Thank you for your assistance. ________________________________

3 4

VIM in Pending issue for VNF Deployment.
by Raman Preet 09 Oct '20

09 Oct '20

Hey. I am facing exactly the same issue as mentioned in this link. but on stein version of openstack http://opendiscussione.blogspot.com/2018/08/re-openstack-tacker-vim-status-… Do you have any resolution for this.? Thanks. Regards

1 0

[Ussuri] [openstack-ansible] [cinder] Can't attach volumes to instances
by Oliver Wenz 09 Oct '20

09 Oct '20

Hi, I've deployed OpenStack successfully using openstack-ansible. I use cinder with LVM backend and can create volumes. However, when I attach them to an instance, they stay detached (though there's no Error Message) both using CLI and the Dashboard. Looking for a solution I read that the cinder logs might contain relevant information but in Ussuri they don't seem to be present under /var/log/cinder... Here's the part of my openstack_user_config.yml regarding Cinder: ``` storage_hosts: lvm-storage1: ip: 192.168.110.202 container_vars: cinder_backends: lvm: volume_backend_name: LVM_iSCSI volume_driver: cinder.volume.drivers.lvm.LVMVolumeDriver volume_group: cinder-volumes iscsi_ip_address: 10.0.3.202 limit_container_types: cinder_volume ``` I've created cinder-volumes with vgcreate before the installation and all cinder services are up: # openstack volume service list +------------------+--------------------------------------+------+---------+-------+----------------------------+ | Binary | Host | Zone | Status | State | Updated At | +------------------+--------------------------------------+------+---------+-------+----------------------------+ | cinder-backup | bc1bl10 | nova | enabled | up | 2020-10-07T11:24:10.000000 | | cinder-volume | bc1bl10@lvm | nova | enabled | up | 2020-10-07T11:24:05.000000 | | cinder-scheduler | infra1-cinder-api-container-1dacc920 | nova | enabled | up | 2020-10-07T11:24:05.000000 | +------------------+--------------------------------------+------+---------+-------+----------------------------+ Thanks in advance! Kind regards, Oliver

3 2

[ceilometer] How to install older version of gnocchi
by WALSH CHANG 09 Oct '20

09 Oct '20

I use Ubuntu 18.04 to install https://docs.openstack.org/ceilometer/stein/install/install-base-ubuntu.html (ceilometer) When I run service gnocchi-api restart, I get Failed to restart gnocchi-api.service: Unit gnocchi-api.service not found. I can't find any solution to address this issue. Someone said the new version doesn't include the gnocchi-api, so I am trying to install the previous version, but I don't know where I can find the old version of gnocchi-api https://stackoverflow.com/questions/47520779/service-gnocchi-api-not-found Can anyone help? Thanks

1 0