-
Notifications
You must be signed in to change notification settings - Fork 170
rubygems undefined method `activate' for nil:NilClass #411
Comments
yes, am also facing same issue. |
There's a Chef DK 0.7.0 RC that has the knife-windows RC in it. I'm curious if it would reproduce this issue as well. |
@btm - Also tried to build chef-dk using |
@btm -
Note- chef-dk v0.7.rc.0 doesn't contains knife-windows RC, it contains 0.8.5 |
@btm @adamedx -
Please let us know if you guys have any idea about these dependency issues. Thank you ! |
@siddheshwar-more the dependency issues are a separate bug. I think they're resolve by the pull requests @btm just linked. This bug is specifically for errors like
And
|
I've been trying to get more information about what's going on in rubygems here by doing ad-hoc Ci builds with a patched rubygems. See the last 2 commits on this: danielsdeleo/rubygems#1 |
On a fresh install of a chefdk 0.7 nightly, running |
edit, this message was from using 0.7.0rc, which was a different issue, filed as #443. |
For google, this is the error you get with ChefDK 0.6.2, after you install knife-windows 1.0.0.rc.1 but you have not removed knife-windows 0.8.5:
Then after I uninstall knife-windows 0.8.5 I get this which was the original error:
|
I guess find_by_name doesn't like prereleases? maybe unless you have a "gem" line specifying the prerelease? rubygems/rubygems@84e8d9f
That nil for find_by_name is what's causing the exception. It doesn't seem like it's supposed to be expected behavior: rubygems/rubygems#988 |
Okay, this is all dependency issues, which one thing ChefDK 0.7.0 is meant to bump. To get knife-windows 1.0.0+ working on ChefDK 0.6.2:
Ultimately there's still some kind of rubygems bug, because this was a really non-obvious path. |
There is a bug in the ChefDK release installed on the build nodes that causes an exception when running the unit tests. Reference: - chef-boneyard/chef-dk#411 - rubygems/rubygems#1287 We think we can run unit phase again after ChefDK 0.7.0 (final release) is installed on the build nodes.
The text was updated successfully, but these errors were encountered: