dep problem on centos 7

[jmccormick2001]

in trying to build operator-sdk I ran into dep issues on my centos7 dev box...basically
dep would hang after prompting me for my github userid...

after several tries of fixing this with no luck, I tried exactly the same steps using a
Ubuntu VM and 'dep ensure' worked (after removing the examples directory).

I suspect perhaps a version/package is causing this on centos 7...would be curious if anyone else builds or has run into this issue on centos 7.

@fanminshi pointed out this dep Issue while debugging this:
golang/dep#1726

none of the fixes in that Issue worked for me on centos 7.

[fanminshi]

@jmccormick2001 Thanks for pointing this out. @hasbro17 and I take a deeper look into this 'dep ensure' worked (after removing the examples directory).

We found out that https://github.com/coreos/operator-sdk/blob/master/example/memcached-operator/handler.go has an extension of .go, and it is causing the building of operator-sdk to fail since the build tool can't find dependencies exists in the handler.go. This file is meant to be an example text and not part of the operator-sdk code based.

A quick fix is like what you said (after removing the examples directory).. We are working on a fix to rename example/memcached-operator/handler.go to example/memcached-operator/handler.go so that the go install can compile the operator-sdk.

[hasbro17]

@jmccormick2001 Can you retry building the operator-sdk from the v0.0.3 tag.

$ git checkout tags/v0.0.3
$ dep ensure
$ go install github.com/coreos/operator-sdk/commands/operator-sdk

[jmccormick2001]

good news, the 0.0.3 version appears to work on centos 7.

[xenserverarmy]

With 0.0.4 I ran into dep ensure hanging also during operator-sdk new after prompting for my GitHub username. After debugging dep with pstree, I found dep hung on the following command: git ls-remote https://github.com/coreos/operator-sdk. My theory was dep was waiting on a github password, so I enabled password caching within git, issued the git ls-remote https://github.com/coreos/operator-sdk command to prompt and cache the password, then re-ran the operator-sdk new.

For others experiencing a similar issue, pstree -sa [pid] may help identify where things get blocked.