[magnum][queens] issues
I am trying patches you just released for magnum (git fetch git:// git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group Regards Ignazio
I think that the script used to write /etc/sysconfig/heat-parms should insert an export for any variable initialized. Any case resourcegroup worked fine before applying last patch. What is changed ? Thanks in Advance for any help. Regards Ignazio Il giorno Lun 21 Gen 2019 12:42 Ignazio Cassano <ignaziocassano@gmail.com> ha scritto:
I am trying patches you just released for magnum (git fetch git:// git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group
Regards Ignazio
Hi Ignazio, I'm jumping in to help. But I'd like to understand the issue correctly. You mentioned using explicitly 'export' you can workaround it before with old Magnum versions. Does it still work for you now? And what's your current Magnum version? Thanks. On 22/01/19 6:32 AM, Ignazio Cassano wrote:
I think that the script used to write /etc/sysconfig/heat-parms should insert an export for any variable initialized. Any case resourcegroup worked fine before applying last patch. What is changed ? Thanks in Advance for any help. Regards Ignazio
Il giorno Lun 21 Gen 2019 12:42 Ignazio Cassano <ignaziocassano@gmail.com <mailto:ignaziocassano@gmail.com>> ha scritto:
I am trying patches you just released for magnum (git fetch git://git.openstack.org/openstack/magnum <http://git.openstack.org/openstack/magnum> refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/ <http://docker.io/openstackmagnum/>} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group
Regards Ignazio
-- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
Hello Feilong, I need the workaround on old and and patched version of magnum. The old version I installed with apt is: oot@tst2-magnum-ubu:~# dpkg -l|grep magnum ii magnum-api 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service ii magnum-common 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - API server ii magnum-conductor 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - conductor ii python-magnum 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - Python library ii python-magnumclient 2.8.0-0ubuntu1~cloud0 all client library for Magnum API - Python 2.x Then I pached magnum with the following commands: cd /tmp git clone git://git.openstack.org/openstack/magnum cd magnum git fetch git://git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD mv /usr/lib/python2.7/dist-packages/magnum /usr/lib/python2.7/dist-packages/magnum.orig cp -rp magnum /usr/lib/python2.7/dist-packages/ Then I applyed again my workaround because my external network used by magnum needs a proxy for accessing internet. But on pre-patched version magnum heat stacks work fine. Magnum patched stacks hang creating kube master Resource Group. Thanks Ignazio Il giorno lun 28 gen 2019 alle ore 10:25 feilong <feilong@catalyst.net.nz> ha scritto:
Hi Ignazio,
I'm jumping in to help. But I'd like to understand the issue correctly. You mentioned using explicitly 'export' you can workaround it before with old Magnum versions. Does it still work for you now? And what's your current Magnum version? Thanks.
On 22/01/19 6:32 AM, Ignazio Cassano wrote:
I think that the script used to write /etc/sysconfig/heat-parms should insert an export for any variable initialized. Any case resourcegroup worked fine before applying last patch. What is changed ? Thanks in Advance for any help. Regards Ignazio
Il giorno Lun 21 Gen 2019 12:42 Ignazio Cassano <ignaziocassano@gmail.com> ha scritto:
I am trying patches you just released for magnum (git fetch git:// git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group
Regards Ignazio
-- Cheers & Best regards, Feilong Wang (王飞龙)
Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
Is the heat stack creation stuck ? Can you see any error from Heat log? It would be nice if you can pop up into #openstack-containers IRC channel so that we can discuss more details? Thanks. On 28/01/19 10:42 PM, Ignazio Cassano wrote:
Hello Feilong, I need the workaround on old and and patched version of magnum.
The old version I installed with apt is:
oot@tst2-magnum-ubu:~# dpkg -l|grep magnum ii magnum-api 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service ii magnum-common 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - API server ii magnum-conductor 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - conductor ii python-magnum 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - Python library ii python-magnumclient 2.8.0-0ubuntu1~cloud0 all client library for Magnum API - Python 2.x
Then I pached magnum with the following commands:
cd /tmp git clone git://git.openstack.org/openstack/magnum <http://git.openstack.org/openstack/magnum> cd magnum git fetch git://git.openstack.org/openstack/magnum <http://git.openstack.org/openstack/magnum> refs/changes/30/629130/9 && git checkout FETCH_HEAD mv /usr/lib/python2.7/dist-packages/magnum /usr/lib/python2.7/dist-packages/magnum.orig cp -rp magnum /usr/lib/python2.7/dist-packages/
Then I applyed again my workaround because my external network used by magnum needs a proxy for accessing internet. But on pre-patched version magnum heat stacks work fine. Magnum patched stacks hang creating kube master Resource Group. Thanks Ignazio
Il giorno lun 28 gen 2019 alle ore 10:25 feilong <feilong@catalyst.net.nz <mailto:feilong@catalyst.net.nz>> ha scritto:
Hi Ignazio,
I'm jumping in to help. But I'd like to understand the issue correctly. You mentioned using explicitly 'export' you can workaround it before with old Magnum versions. Does it still work for you now? And what's your current Magnum version? Thanks.
On 22/01/19 6:32 AM, Ignazio Cassano wrote:
I think that the script used to write /etc/sysconfig/heat-parms should insert an export for any variable initialized. Any case resourcegroup worked fine before applying last patch. What is changed ? Thanks in Advance for any help. Regards Ignazio
Il giorno Lun 21 Gen 2019 12:42 Ignazio Cassano <ignaziocassano@gmail.com <mailto:ignaziocassano@gmail.com>> ha scritto:
I am trying patches you just released for magnum (git fetch git://git.openstack.org/openstack/magnum <http://git.openstack.org/openstack/magnum> refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/ <http://docker.io/openstackmagnum/>} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group
Regards Ignazio
-- 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 ------------------------------------------------------
-- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
OK Give me 5 minutes to reapply the patch and I'll connect to IRC Thanks Il giorno lun 28 gen 2019 alle ore 10:47 feilong <feilong@catalyst.net.nz> ha scritto:
Is the heat stack creation stuck ? Can you see any error from Heat log? It would be nice if you can pop up into #openstack-containers IRC channel so that we can discuss more details? Thanks.
On 28/01/19 10:42 PM, Ignazio Cassano wrote:
Hello Feilong, I need the workaround on old and and patched version of magnum.
The old version I installed with apt is:
oot@tst2-magnum-ubu:~# dpkg -l|grep magnum ii magnum-api 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service ii magnum-common 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - API server ii magnum-conductor 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - conductor ii python-magnum 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - Python library ii python-magnumclient 2.8.0-0ubuntu1~cloud0 all client library for Magnum API - Python 2.x
Then I pached magnum with the following commands:
cd /tmp git clone git://git.openstack.org/openstack/magnum cd magnum git fetch git://git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD mv /usr/lib/python2.7/dist-packages/magnum /usr/lib/python2.7/dist-packages/magnum.orig cp -rp magnum /usr/lib/python2.7/dist-packages/
Then I applyed again my workaround because my external network used by magnum needs a proxy for accessing internet. But on pre-patched version magnum heat stacks work fine. Magnum patched stacks hang creating kube master Resource Group. Thanks Ignazio
Il giorno lun 28 gen 2019 alle ore 10:25 feilong <feilong@catalyst.net.nz> ha scritto:
Hi Ignazio,
I'm jumping in to help. But I'd like to understand the issue correctly. You mentioned using explicitly 'export' you can workaround it before with old Magnum versions. Does it still work for you now? And what's your current Magnum version? Thanks.
On 22/01/19 6:32 AM, Ignazio Cassano wrote:
I think that the script used to write /etc/sysconfig/heat-parms should insert an export for any variable initialized. Any case resourcegroup worked fine before applying last patch. What is changed ? Thanks in Advance for any help. Regards Ignazio
Il giorno Lun 21 Gen 2019 12:42 Ignazio Cassano <ignaziocassano@gmail.com> ha scritto:
I am trying patches you just released for magnum (git fetch git:// git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group
Regards Ignazio
-- Cheers & Best regards, Feilong Wang (王飞龙)
Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
-- Cheers & Best regards, Feilong Wang (王飞龙)
Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
I am on #openstack-containers IRC Il giorno lun 28 gen 2019 alle ore 10:47 feilong <feilong@catalyst.net.nz> ha scritto:
Is the heat stack creation stuck ? Can you see any error from Heat log? It would be nice if you can pop up into #openstack-containers IRC channel so that we can discuss more details? Thanks.
On 28/01/19 10:42 PM, Ignazio Cassano wrote:
Hello Feilong, I need the workaround on old and and patched version of magnum.
The old version I installed with apt is:
oot@tst2-magnum-ubu:~# dpkg -l|grep magnum ii magnum-api 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service ii magnum-common 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - API server ii magnum-conductor 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - conductor ii python-magnum 6.1.0-0ubuntu1~cloud0 all OpenStack containers as a service - Python library ii python-magnumclient 2.8.0-0ubuntu1~cloud0 all client library for Magnum API - Python 2.x
Then I pached magnum with the following commands:
cd /tmp git clone git://git.openstack.org/openstack/magnum cd magnum git fetch git://git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD mv /usr/lib/python2.7/dist-packages/magnum /usr/lib/python2.7/dist-packages/magnum.orig cp -rp magnum /usr/lib/python2.7/dist-packages/
Then I applyed again my workaround because my external network used by magnum needs a proxy for accessing internet. But on pre-patched version magnum heat stacks work fine. Magnum patched stacks hang creating kube master Resource Group. Thanks Ignazio
Il giorno lun 28 gen 2019 alle ore 10:25 feilong <feilong@catalyst.net.nz> ha scritto:
Hi Ignazio,
I'm jumping in to help. But I'd like to understand the issue correctly. You mentioned using explicitly 'export' you can workaround it before with old Magnum versions. Does it still work for you now? And what's your current Magnum version? Thanks.
On 22/01/19 6:32 AM, Ignazio Cassano wrote:
I think that the script used to write /etc/sysconfig/heat-parms should insert an export for any variable initialized. Any case resourcegroup worked fine before applying last patch. What is changed ? Thanks in Advance for any help. Regards Ignazio
Il giorno Lun 21 Gen 2019 12:42 Ignazio Cassano <ignaziocassano@gmail.com> ha scritto:
I am trying patches you just released for magnum (git fetch git:// git.openstack.org/openstack/magnum refs/changes/30/629130/9 && git checkout FETCH_HEAD) I got same issues on proxy. In the old version I modified with the help of spyros the scripts under /usr/lib/python2.7/dist-packages/magnum/drivers/common/templates/kubernetes/fragments because PROXY variables are not inherited in /etc/sysconfig/heat-params PROXY E NO PROXY variables are present but we must modify configure-kubernetes-master.sh to force them . /etc/sysconfig/heat-params echo "configuring kubernetes (master)" _prefix=${CONTAINER_INFRA_PREFIX:-docker.io/openstackmagnum/} export HTTP_PROXY=${HTTP_PROXY} export HTTPS_PROXY=${HTTPS_PROXY} export NO_PROXY=${NO_PROXY} echo "HTTP_PROXY IS ${HTTP_PROXY}" exporting the above variables when external network has a proxy, the master is installed but stack hangs creating kube master Resource Group
Regards Ignazio
-- Cheers & Best regards, Feilong Wang (王飞龙)
Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
-- Cheers & Best regards, Feilong Wang (王飞龙)
Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------
participants (2)
-
feilong
-
Ignazio Cassano