kubevirt.io build issues

47 views
Skip to first unread message

Alexander Gallego

unread,
Oct 4, 2018, 4:29:56 PM10/4/18
to kubevirt-dev
Hi Guys, 

I was able to track down dependency issues with kubevirt.io/* packages as a consumer (from go source code) 

Was prototyping the hooks api. 

The gist of the issue is this

when you do 

`dep ensure` via go dep

it fails to resolve correctly the  kubevit.io/containerized-data-importer because it has non-matching verstion tags/releases that matches the main kubevirt.

i.e.: 


and



So the fetcher/dependency solver will look at the main /root dependency and 
see that kubevirt.io* will be at version 0.9.0 but the subrepo of containerized-data-importer is at version v1.2.0 at the latest. 

Other build issues that *do not* happen w/ go-get is this: 

Solving failure: No versions of github.com/kubevirt/kubevirt met constraints:                                                                                                                    
        v0.9.0: unable to deduce repository and source type for "kubevirt.io/kubevirt/pkg/api/v1": unable to read metadata: go-import metadata not found                                         
        v0.8.0: unable to deduce repository and source type for "kubevirt.io/kubevirt/pkg/api/v1": unable to read metadata: go-import metadata not found

go getting the github.com URL works fine but something is happening with kubevirt.io 



How to reproduce:


1) Take the examples hooks and put it on a separate folder 

and call `dep ensure`


Here are a few `dep ensure ` traces


Not sure if anyone has seen this. 

I'm happy to push a prototype repo. but the default example reproduces it. 



err.txt
err2.txt

Alexander Gallego

unread,
Oct 4, 2018, 4:41:31 PM10/4/18
to kubevirt-dev
i forgot to add. this happens only when i add kubevirt.io deps. 

i can build admission controllers in the same repo just fine. 

Sent from my mobile, please excuse my handwriting.

--
You received this message because you are subscribed to a topic in the Google Groups "kubevirt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubevirt-dev/a3y9tjSB3Z4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubevirt-dev...@googlegroups.com.
To post to this group, send email to kubevi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/4ad41d70-90a2-4b2e-9b85-a0f53fb29e8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fabian Deutsch

unread,
Oct 5, 2018, 10:22:47 AM10/5/18
to Alexander Gallego, Adam Litke, David Vossel, Michael Henriksen, kubevirt-dev
Hey Alex,

thanks for raising this! I'm adding a few folks who might be able to help with this.

David, Adam, Michael - Can you help Alex?

- fabian

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.

Alexander Gallego

unread,
Oct 5, 2018, 10:57:23 AM10/5/18
to kubevirt-dev

Here is an (i think) incorrect dependency graph which at least resolves with no conflicts:


I think it is incorrect because: 

go generate ./pkg/... ./cmd/...
go fmt ./pkg/... ./cmd/...
go vet ./pkg/... ./cmd/...

vendor/kubevirt.io/kubevirt/pkg/log/log.go:66:25: undefined: log.Context

Makefile:39: recipe for target 'vet' failed

Alexander Gallego

unread,
Oct 5, 2018, 12:13:10 PM10/5/18
to kubevirt-dev
Here is a gopkg.toml that works w/ godep 

manually bisecting commits sorta worked. 

Reply all
Reply to author
Forward
0 new messages