January 2020 - openstack-discuss - lists.openstack.org

[mistral][core] Promoting Eyal Bar-Ilan to the Mistral core team
by Renat Akhmerov 15 Jan '20

15 Jan '20

Hi, I’d like to promote Eyal Bar-Ilan to the Mistral core team since he’s shown a great contribution performance in the recent months. Eyal always reacts on various CI issues timely and provides fixes very quickly. He’s also completed a number of useful functional Mistral features in Train and Ussuri. And his overall statistics for Ussuri ([1]) makes him a clear candidate for core membership. Core reviewers, please let me know if you have any objections. [1] https://www.stackalytics.com/?module=mistral-group&release=ussuri&user_id=e… Thanks Renat Akhmerov @Nokia

4 4

RE: Designate zone troubleshooting [designate]
by Albert Braden 15 Jan '20

15 Jan '20

1 0

[tripleo] rocky builds
by Wesley Hayutin 14 Jan '20

14 Jan '20

Greetings, I've confirmed that builds from the Rocky release will no longer be imported. Looking for input from the upstream folks with regards to maintaining the Rocky release for upstream. Can you please comment if you have any requirement to continue building, patching Rocky as I know there are active reviews [1]. I've added this topic to be discussed at the next meeting [2] Thank you! [1] https://review.opendev.org/#/q/status:open+tripleo+branch:stable/rocky [2] https://etherpad.openstack.org/p/tripleo-meeting-items

3 2

[cyborg] enable launchpad or storyboard for Cyborg
by Brin Zhang(张百林) 14 Jan '20

14 Jan '20

Hi Sundar and all: I think we should enable launchpad for the Cyborg project to record its reported bugs, submitted blueprints, etc., so that we can keep track of project updates and changes. Now I found there are some specifications in the cyborg-specs, and there has not been management by the Launchpad (https://launchpad.net/cyborg) or storyboard (https://storyboard.openstack.org/#!/project/openstack/cyborg) Personally recommend using Launchpad, it looks very intuitive. brinzhang

3 2

[all] DevStack jobs broken due to setuptools not available for Python 2
by Radosław Piliszek 14 Jan '20

14 Jan '20

Hi all, I noticed DevStack jobs fail all over the place [1] due to: UnsupportedPythonVersion: Package 'setuptools' requires a different Python: 2.7.17 not in '>=3.5' Bug reported in [2]. Notice USE_PYTHON3=True does not help as stack.sh is hardcoded to versionless Python. [1] https://zuul.opendev.org/t/openstack/builds?result=RETRY_LIMIT&result=FAILU… [2] https://bugs.launchpad.net/devstack/+bug/1859350 -yoctozepto

6 8

Designate zone troubleshooting
by Albert Braden 14 Jan '20

14 Jan '20

1 0

[ops] No ops meetup team meeting tomorrow (2020/1/14) on IRC
by Chris Morgan 14 Jan '20

14 Jan '20

We had a great OpenStack Ops meetup last week in London. Those involved now need to catch up on other work, so we'll resume regular meetings on Jan 21st. Our thanks to everyone who attended and/or helped make it one of the best meetups in a while. Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[blazar] No IRC meeting tomorrow
by Pierre Riteau 14 Jan '20

14 Jan '20

Hello, As announced in the last meeting, due to travel the weekly Blazar IRC meeting of January 14 is cancelled. The next meeting will be held on Jan 21. Thanks, Pierre Riteau (priteau)

1 0

Re: [magnum]: K8s cluster creation times out. OpenStack Train : [ERROR]: Unable to render networking. Network config is likely broken
by feilong 14 Jan '20

14 Jan '20

Hi Bhupathi, Firstly, I would suggest setting the use_podman=False when using fedora atomic image. And it would be nice to set the "kube_tag", e.g. v1.15.6 explicitly. Then please trigger a new cluster creation. Then if you still run into error. Here is the debug steps: 1. ssh into the master node, check log /var/log/cloud-init-output.log 2. If there is no error in above log file, then run journalctl -u heat-container-agent to check the heat-container-agent log. If above step is correct, then you must be able to see something useful here. On 11/01/20 12:15 AM, Bhupathi, Ramakrishna wrote: > > Wang, > > Here it is . I added the labels subsequently. My nova and neutron are > working all right as I installed various systems there working with no > issues.. > > > > > > *From:*Feilong Wang [mailto:feilong@catalyst.net.nz] > *Sent:* Thursday, January 9, 2020 6:12 PM > *To:* openstack-discuss(a)lists.openstack.org > *Subject:* Re: [magnum]: K8s cluster creation times out. OpenStack > Train : [ERROR]: Unable to render networking. Network config is likely > broken > > > > Hi Bhupathi, > > Could you please share your cluster template? And please make sure > your Nova/Neutron works. > > > > On 10/01/20 2:45 AM, Bhupathi, Ramakrishna wrote: > > Folks, > > I am building a Kubernetes Cluster( Openstack Train) and using > fedora atomic-29 image . The nodes come up fine ( I have a simple > 1 master and 1 node) , but the cluster creation times out, and > when I access the cloud-init logs I see this error . Wondering > what I am missing as this used to work before. I wonder if this > is image related . > > > > [ERROR]: Unable to render networking. Network config is likely > broken: No available network renderers found. Searched through > list: ['eni', 'sysconfig', 'netplan'] > > > > Essentially the stack creation fails in “kube_cluster_deploy” > > > > Can somebody help me debug this ? Any help is appreciated. > > > > --RamaK > > The contents of this e-mail message and > any attachments are intended solely for the > addressee(s) and may contain confidential > and/or legally privileged information. If you > are not the intended recipient of this message > or if this message has been addressed to you > in error, please immediately alert the sender > by reply e-mail and then delete this message > and any attachments. If you are not the > intended recipient, you are notified that > any use, dissemination, distribution, copying, > or storage of this message or any attachment > is strictly prohibited. > > -- > Cheers & Best regards, > Feilong Wang (王飞龙) > Head of R&D > Catalyst Cloud - Cloud Native New Zealand > -------------------------------------------------------------------------- > Tel: +64-48032246 > Email: flwang(a)catalyst.net.nz <mailto:flwang@catalyst.net.nz> > Level 6, Catalyst House, 150 Willis Street, Wellington > -------------------------------------------------------------------------- > The contents of this e-mail message and > any attachments are intended solely for the > addressee(s) and may contain confidential > and/or legally privileged information. If you > are not the intended recipient of this message > or if this message has been addressed to you > in error, please immediately alert the sender > by reply e-mail and then delete this message > and any attachments. If you are not the > intended recipient, you are notified that > any use, dissemination, distribution, copying, > or storage of this message or any attachment > is strictly prohibited. -- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang(a)catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------

1 0

[cinder] ussuri virtual mid-cycle next week
by Brian Rosmaita 13 Jan '20

13 Jan '20

The poll results are in. There was only one time when everyone can meet (apologies to the "if need be" people, but the need be). Session One of the Cinder Ussuri virtual mid-cycle will be held: DATE: 21 JANUARY 2020 TIME: 1300-1500 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the planning etherpad: https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning cheers, brian

1 0