{"action":"created","issue":{"url":"https://api.github.com/repos/openshift/openshift-sdn/issues/297","repository_url":"https://api.github.com/repos/openshift/openshift-sdn","labels_url":"https://api.github.com/repos/openshift/openshift-sdn/issues/297/labels{/name}","comments_url":"https://api.github.com/repos/openshift/openshift-sdn/issues/297/comments","events_url":"https://api.github.com/repos/openshift/openshift-sdn/issues/297/events","html_url":"https://github.com/openshift/openshift-sdn/issues/297","id":150162031,"number":297,"title":"multitenant plugin fails on oadm pod-network join-projects","user":{"login":"allen13","id":99757,"avatar_url":"https://avatars.githubusercontent.com/u/99757?v=3","gravatar_id":"","url":"https://api.github.com/users/allen13","html_url":"https://github.com/allen13","followers_url":"https://api.github.com/users/allen13/followers","following_url":"https://api.github.com/users/allen13/following{/other_user}","gists_url":"https://api.github.com/users/allen13/gists{/gist_id}","starred_url":"https://api.github.com/users/allen13/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/allen13/subscriptions","organizations_url":"https://api.github.com/users/allen13/orgs","repos_url":"https://api.github.com/users/allen13/repos","events_url":"https://api.github.com/users/allen13/events{/privacy}","received_events_url":"https://api.github.com/users/allen13/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-04-21T18:59:13Z","updated_at":"2016-04-21T19:08:35Z","closed_at":"2016-04-21T19:04:38Z","body":"Steps to reproduce:\r\n\r\n- Set up an openshift cluster using the redhat/openshift-ovs-multitenant plugin for networking\r\n- Create pods in two different projects\r\n- Make sure those pods can't ping each other since they should be isolated\r\n- Run oadm pod-network join-projects --to=p1 p2\r\n- The two pods still can not ping each other\r\n\r\nError in openshift-node logs:\r\n\r\novs-vsctl[68003]: ovs|00002|vsctl|ERR|no row \"[]\" in table QoS\r\n\r\nFix:\r\n\r\nComment out line 106 in openshift-sdn-ovs https://github.com/openshift/openshift-sdn/blob/master/plugins/osdn/ovs/bin/openshift-sdn-ovs#L106\r\nRepeat the above process. The two pods can now ping each other and there is no error in the logs.\r\n\r\nConcerns:\r\n\r\nHow important is it that ovs-vsctl destroy qos ${qos} be run? I assume one day I may run into a case where this is an issue. Additionally, this could be conditionally skipped by checking for []. Maybe I am missing some other config? Should qos have stuff in it? I feel like it will always be empty since this command is run before it: ovs-vsctl clear port ${veth_host} qos\r\n\r\nThanks for your time!"},"comment":{"url":"https://api.github.com/repos/openshift/openshift-sdn/issues/comments/213073211","html_url":"https://github.com/openshift/openshift-sdn/issues/297#issuecomment-213073211","issue_url":"https://api.github.com/repos/openshift/openshift-sdn/issues/297","id":213073211,"user":{"login":"allen13","id":99757,"avatar_url":"https://avatars.githubusercontent.com/u/99757?v=3","gravatar_id":"","url":"https://api.github.com/users/allen13","html_url":"https://github.com/allen13","followers_url":"https://api.github.com/users/allen13/followers","following_url":"https://api.github.com/users/allen13/following{/other_user}","gists_url":"https://api.github.com/users/allen13/gists{/gist_id}","starred_url":"https://api.github.com/users/allen13/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/allen13/subscriptions","organizations_url":"https://api.github.com/users/allen13/orgs","repos_url":"https://api.github.com/users/allen13/repos","events_url":"https://api.github.com/users/allen13/events{/privacy}","received_events_url":"https://api.github.com/users/allen13/received_events","type":"User","site_admin":false},"created_at":"2016-04-21T19:08:35Z","updated_at":"2016-04-21T19:08:35Z","body":"Wow thanks! I was looking right at that and didn't notice when I marked the line for the issue."}}