Bug 1227096 - NetworkingNew test fails
Summary: NetworkingNew test fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Atomic
Classification: Retired
Component: docker-io
Version: unspecified
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Eric Paris
QA Contact:
URL:
Whiteboard:
Depends On: 1165982 1193590 1214810
Blocks: 1222060
TreeView+ depends on / blocked
 
Reported: 2015-06-01 22:46 UTC by Jay Vyas
Modified: 2015-08-07 11:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1214810
Environment:
Last Closed: 2015-08-07 11:53:02 UTC
RHEL 7.3 requirements from Atomic Host:
Embargoed:


Attachments (Terms of Use)

Description Jay Vyas 2015-06-01 22:46:46 UTC
The newer nettest (tag 1.4) **fails** because the /var/run/servrets/kubernetes.io/serviceaccount/token isnt avaialable to docker images which run in atomic.

I'm not sure why from tag1.3 -> tag1.4 this service account token became a requirement, but it did.  

I guess we will have to dig into the recent changes.

For now, running the ginko.focus to ignore "NetworkingNew" is sufficient so that you can run the networking tests without testing this feature.  

But we should figure out what needs to be done to support the serviceaccount/token file so that all the networking e2es run cleanly.

Comment 2 Jay Vyas 2015-06-01 22:59:13 UTC
Ah. okay more info on this :  

For kubernetes 0.18.0 you need "SERVICE ACCOUNTS" for doing things in containers etc...   

I dont think this is really is installed, it seems, in any of our deployments (yet)?

Comment 3 Daniel Walsh 2015-06-03 12:03:23 UTC
Should atomic have a kubernetes option?  How do I change alex larson as default owner of docker-io?  How do I remove docker-io and change it to docker.

Comment 4 Jay Vyas 2015-08-06 18:59:31 UTC
folks this is obsolete most likely for current kube versions.  NetworkingNew was a transitional thing that got cleaned up a few days after it was introduced.


Note You need to log in before you can comment on or make changes to this bug.