I just moved to Fedora core OS image (fedora-coreos-31) to build my K8s Magnum cluster and cluster creation fails with ERROR: The Parameter (octavia_ingress_controller_tag) was not defined in template. I wonder why I need that tag. Any help please? --RamaK From: Feilong Wang [mailto:feilong@catalyst.net.nz] Sent: Monday, January 13, 2020 4:25 PM To: Donny Davis <donny@fortnebula.com> Cc: OpenStack Discuss <openstack-discuss@lists.openstack.org> Subject: Re: [magnum]: K8s cluster creation times out. OpenStack Train : [ERROR]: Unable to render networking. Network config is likely broken OK, if you're happy to stay on CoreOS, all good. If you're interested in migrating to Fedora CoreOS and have questions, then you're welcome to popup in #openstack-containers. Cheers. On 14/01/20 10:21 AM, Donny Davis wrote: Just Coreos - I tried them all and it was the only one that worked oob. On Mon, Jan 13, 2020 at 4:10 PM Feilong Wang <feilong@catalyst.net.nz<mailto:feilong@catalyst.net.nz>> wrote: Hi Donny, Do you mean Fedore CoreOS or just CoreOS? The current CoreOS driver is not actively maintained, I would suggest migrating to Fedora CoreOS and I'm happy to help if you have any question. Thanks. On 14/01/20 9:57 AM, Donny Davis wrote: FWIW I was only able to get the coreos image working with magnum oob.. the rest just didn't work. On Mon, Jan 13, 2020 at 2:31 PM feilong <feilong@catalyst.net.nz<mailto:feilong@catalyst.net.nz>> wrote: 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.. [cid:image001.png@01D5CAF2.D1A55F30] From: Feilong Wang [mailto:feilong@catalyst.net.nz] Sent: Thursday, January 9, 2020 6:12 PM To: openstack-discuss@lists.openstack.org<mailto:openstack-discuss@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@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@catalyst.net.nz<mailto:flwang@catalyst.net.nz> Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------ -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First" -- Cheers & Best regards, Feilong Wang (王飞龙) Head of R&D Catalyst Cloud - Cloud Native New Zealand -------------------------------------------------------------------------- Tel: +64-48032246 Email: flwang@catalyst.net.nz<mailto:flwang@catalyst.net.nz> Level 6, Catalyst House, 150 Willis Street, Wellington -------------------------------------------------------------------------- -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First" -- Cheers & Best regards, Feilong Wang (王飞龙) Head of R&D Catalyst Cloud - Cloud Native New Zealand -------------------------------------------------------------------------- Tel: +64-48032246 Email: flwang@catalyst.net.nz<mailto:flwang@catalyst.net.nz> Level 6, Catalyst House, 150 Willis Street, Wellington -------------------------------------------------------------------------- E-MAIL CONFIDENTIALITY NOTICE: 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.
