-
Notifications
You must be signed in to change notification settings - Fork 16
Error downloading cdkv2 #15
Comments
Asking Andrew to take a peek, I won't have time for a few weeks. |
@ishuverma two things:
|
No response, so closing this down, open if help still needed. |
Below are the steps I took to get this working for KVM. I just followed the steps listed in the CDK Installation Guide. Apparently, there are few extra steps to get libvirt working. Enable Repossubscription-manager repos --enable rhel-server-rhscl-7-rpms yum groupinstall "Virtualization Host" Installing Vagrant, required packages and libvirt-pluginyum install sclo-vagrant1 sclo-vagrant1-vagrant-libvirt sclo-vagrant1-vagrant-libvirt-doc cp /opt/rh/sclo-vagrant1/root/usr/share/vagrant/gems/doc/vagrant-libvirt-*/polkit/10-vagrant-libvirt.rules /etc/polkit-1/rules.d Launching CDK As root: systemctl restart libvirtdsystemctl restart polkitLogout as root $ scl enable sclo-vagrant1 bash $ cd ~/cdk/components/rhel/misc/shared_folder/rhel-ose/ $ vagrant up |
@ishuverma, what Linux OS are you using? |
Rhel 7.2 On Oct 7, 2016 1:59 AM, "Eric D. Schabell" [email protected] wrote:
|
To be specific, I followed step by step instructions and didn't have any ishu On Fri, Oct 7, 2016 at 8:15 AM, Ishu Verma [email protected] wrote:
|
Ishu, Vagrant still thought your default provider was VBox instead of libvirt before the file open error. The installer states that in the screenshot above. I've ran into that problem before with RHEL + libvirt + Vagrant and traced it to 2 sources: the Vagrantfile itself (vm. settings) or your defaults (in ~/.vagrant.d). This installer checks for VBox / libvirt being available but I don't see it forcing a specific provider ("vagrant box add --name $CDK_BOX_VERSION $SRC_DIR/$LINUX_BOX" instead of --provider). So this may just be another untested use case. If I can find time I'll try that fix but you're working now anyways so just wanted to point out possible cause that I'd seen before incase it happens to another RHEL + libvirt user who can test the fix. Jp |
Also @ishuverma , can you try the newer version just released and let me know if you encounter problems as the VagrantFile is completely different with many updates now in 2.2. Thanks. |
@vap0rtranz , would a change in the vagrant check done in init.sh cover that? |
will do On Sat, Oct 8, 2016 at 4:20 AM, Eric D. Schabell [email protected]
|
I tried this again on a fresh system and immediately ran into the error (No Jp,
I had to manually follow the steps again to get this working. ishu On Sat, Oct 8, 2016 at 4:20 AM, Eric D. Schabell [email protected]
|
@ishuverma , you say the vagrant plugins are missing, but those are installed from the CDK unzip (source provided for plugins)? |
When I get to the step: "vagrant up", I'm getting an error:
The previous steps to setup the project went ok (see enclosed screenshot).
The text was updated successfully, but these errors were encountered: