Hi all,

Just updating my issues with Pod Sandbox - Srini - you was right, these errors were caused by using non-default namespace in demo chart.
I've troubleshooted this issue a little and it turned out it was caused by NetworkAttachmentDefinition for ovn missing on non-default namespaces (in default one it is installed during KUD spinup). I've corrected demo charts to provide their own NetworkAttachmentDefinition regardless of namespace (also with different name not to collide on default namespace with existing one) so that this issue was fixed.
I've run my test suite over it and it looks fine, so please take a look at https://gerrit.onap.org/r/#/c/multicloud/k8s/+/91864/.
With this change applied, I'm able to spin up all pods (and other resources) of vFW demo by k8splugin on custom namespace.

 

--------- Original Message ---------

Sender : Łukasz Rajewski <[email protected]>

Date : 2019-07-23 13:22 (GMT+2)

Title : Re: Re: Re: K8s in ONAP - DDF follow up

 

Hi,

 

I have reported another bug - maybe already known to you. I can create an Instance object but pod created with virtlet fail to start.

 

https://jira.onap.org/browse/MULTICLOUD-733

 

Regards,

Lukasz

 

 

 

On Tue, Jul 23, 2019 at 2:41 AM Sood, Ritu <[email protected]> wrote:

For Dublin release there is a workaround for providing OVN address in the configmap for the K8sPlugin. Updated the wiki with this information. Also copied here. The master branch for k8sPlugin is under active development and it is not tested. It would be better just to stick to the release version of the K8s plugin.

 Update K8sConfig

 Workaround for R4 Dublin. This step will not be needed in R5.

 Edit the configMap helm-release-name-multicloud-k8s for K8s plugin to make changes to the config like below to add ovn-central-address:

 {
"ca-file": "/opt/multicloud/k8splugin/certs/root_ca.cer",
"server-cert": "/opt/multicloud/k8splugin/certs/multicloud-k8s.pub",
"server-key": "/opt/multicloud/k8splugin/certs/
multicloud-k8s.pr",
"password": "c2VjcmV0bWFuYWdlbWVudHNlcnZpY2VzZWNyZXRwYXNzd29yZA==",
"database-type": "mongo",
"database-address": "multicloud-k8s-mongo",
"etcd-ip": "multicloud-k8s-etcd",
"plugin-dir": "/opt/multicloud/k8splugin/plugins",

  "ovn-central-address": "<IP address of the Kubernetes controller>:6641"
}

 (the configMap is based on  oom/kubernetes/multicloud/charts/multicloud-k8s/resources/config/k8sconfig.json )

 Restart the Multoclod-K8s Plugin for the changes to take effect.

-Ritu

From: Addepalli, Srinivasa R
 Sent: Monday, July 22, 2019 10:13 AM
 To: [email protected]; Lukasz Rajewski <[email protected]>
 Cc: Rajewski Lukasz - Korpo <[email protected]>; [email protected]; Kamineni, Kiran K <[email protected]>; Zhu, Libo <[email protected]>; Sood, Ritu <[email protected]>; Jayathirth, Pramod Raghavendra <[email protected]>; Multanen, Eric W <[email protected]>
 Subject: RE: Re: Re: K8s in ONAP - DDF follow up

 

Hi Ritu,

Can you check? Could this be due to not using default namespace in helm charts?

Srini

 

From: Konrad Banka [mailto:[email protected]]
 Sent: Monday, July 22, 2019 7:18 AM
 To: Łukasz Rajewski <[email protected]>; Konrad Banka <[email protected]>
 Cc: Rajewski Łukasz - Korpo <[email protected]>; [email protected]; Kamineni, Kiran K <[email protected]>; Addepalli, Srinivasa R <[email protected]>; Zhu, Libo <[email protected]>; Sood, Ritu <[email protected]>; Jayathirth, Pramod Raghavendra <[email protected]>; Multanen, Eric W <[email protected]>
 Subject: RE: Re: Re: K8s in ONAP - DDF follow up

 

Hi again,
 
I've managed to launch some more basic tests today and it looks like my change doesn't fix this issue completely. It fixes creating network resources and they are created correctly (please see log below), however pods are having issues with creating sandbox due to multus issues. Nevertheless I think that pod sandbox issue may have root cause anchored somewhere else, so probably additional fix may be needed.
 
``` k8plugin logs:
2019/07/22 14:14:42 Generate MAC address
2019/07/22 14:14:42 ovn4nfvk8s_protected-private-net created
2019/07/22 14:14:42 Processing Kind: Network
2019/07/22 14:14:42 Processing file: /tmp/helm-tmpl-522893518/firewall/templates/unprotected-private-net.yaml-0
2019/07/22 14:14:42 Reading YAML file
2019/07/22 14:14:42 Decoding deployment YAML
2019/07/22 14:14:42 Generate MAC address
2019/07/22 14:14:42 ovn4nfvk8s_unprotected-private-net created
::1 - - [22/Jul/2019:14:14:41 +0000] "POST /v1/instance HTTP/1.1" 201 844 

```
``` ovn ports status (previously logical switches were not created)
 vagrant@multicloud"~/multicloud-k8s/kud/tests [0]$ ovn-nbctl  --db tcp:$OVN_CENTRAL_ADDRESS lrp-list ovn4nfv-master
d5845420-25d9-4906-86c7-772cfee7abef (rtoj-ovn4nfv-master)
ccfd83e0-6b9f-43fb-aa54-1b7c5b462220 (rtos-onap-private-net)
9ad14ed7-ab33-479f-a336-cb9702e57daf (rtos-protected-private-net)
bee4790a-af0b-4f4f-9270-018e04e2a606 (rtos-unprotected-private-net) 
```
``` pods status

vagrant@multicloud"~/multicloud-k8s/kud/tests [0]$ kubectl describe -n vfw-test pods test-sink-5 | tail -n 3
  Normal   SandboxChanged          3m28s (x12 over 4m46s)  kubelet, minion02  Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  3m21s (x4 over 3m43s)   kubelet, minion02  (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "525b3aae9d1c2fe4b778ec4efa65460aa5d867ac2593ead1d71c30fd87f715dd" network for pod "test-sink-5456988b6c-qq754": NetworkPlugin cni failed to set up pod "test-sink-5456988b6c-qq754_vfw-test" network: Multus: Err in loading K8s Delegates k8s args: Multus: Err in getting k8s network from pod: GetPodNetwork: failed getting the delegate: getKubernetesDelegate: failed to get network resource, refer Multus README.md for the usage guide: the server could not find the requested resource
```

 

--------- Original Message ---------

Sender : Łukasz Rajewski <[email protected]>

Date : 2019-07-22 16:00 (GMT+2)

Title : Re: Re: K8s in ONAP - DDF follow up

 

So I have reported it in here

 

https://jira.onap.org/browse/MULTICLOUD-731

 

Lukasz

 

 

On Mon, Jul 22, 2019 at 3:54 PM Konrad Banka <[email protected]> wrote:

Hi Łukasz, All

I came across the same issue as you today. I think I've located culprit of this error and I've addressed it in review https://gerrit.onap.org/r/c/multicloud/k8s/+/91812.
Please note it's work in progress as I didn't manage today to thoroughly test it, but I expect to do it tomorrow morning.
 
With Regards,
Konrad Bańka 

 

 

  

 

 

With Regards,
Konrad Bańka 

 

 

  

 

 

With Regards,
Konrad Bańka 

 

  

_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#18255) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

Your Subscription | Contact Group Owner | Unsubscribe [[email protected]]

_._,_._,_

Reply via email to