Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix vagrant config for libvirt #42

Merged
merged 1 commit into from
Jan 26, 2021
Merged

Conversation

detiber
Copy link
Contributor

@detiber detiber commented Jan 22, 2021

Description

Fixes the vagrant configuration when using libvirt

Why is this needed

Without this issue the vagrant provisioner fails when using libvirt with the following error:

Error occurred while creating new network: {:iface_type=>:private_network, :netmask=>"255.255.255.0", :dhcp_enabled=>false, :forward_mode=>"none", :virtualbox__intnet=>"tink_network", :libvirt__dhcp_enabled=>false, :libvirt__forward_mode=>"none", :auto_config=>false, :protocol=>"tcp", :id=>"18e6fc6d-41b8-40c9-814d-ffc476bfd920"}.

How Has This Been Tested?

Reran vagrant up after making the changes and the provisioner machine successfully was created

How are existing users impacted? What migration steps/scripts do we need?

Should not affect existing users unless they were trying to use vagrant/libvirt and were unsuccessful before.

No migration should be needed.

@gianarb
Copy link
Contributor

gianarb commented Jan 22, 2021

I have zero experience with that. @gauravgahlot somebody is can verify that from your end?! Or @thebsdbox do you use libvirt? :)

@detiber detiber changed the title Fix vagrant config for libvirt [WIP]Fix vagrant config for libvirt Jan 22, 2021
@detiber
Copy link
Contributor Author

detiber commented Jan 22, 2021

Working on additional changes to make this work with cluster-api-provider-tink

@gianarb gianarb removed their request for review January 22, 2021 16:58
@gianarb gianarb added ci-check/vagrant-setup This label trigger a GitHub action that tests the Vagrant Setup guide https://tinkerbell.org/setup/ and removed ci-check/vagrant-setup This label trigger a GitHub action that tests the Vagrant Setup guide https://tinkerbell.org/setup/ labels Jan 24, 2021
@detiber detiber changed the title [WIP]Fix vagrant config for libvirt Fix vagrant config for libvirt Jan 25, 2021
libvirt__dhcp_enabled: false,
libvirt__forward_mode: 'none',
libvirt__adapter: 1,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was needed to ensure that the private network isn't accidentally picked up as eth0 instead of eth1.

@@ -56,6 +60,8 @@ Vagrant.configure('2') do |config|
lv.cpus = 1
lv.boot 'network'
lv.mgmt_attach = false
lv.storage :file, :size => '40G'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without this, you cannot actually run a workflow that does something like install an OS to disk.

@detiber
Copy link
Contributor Author

detiber commented Jan 25, 2021

CI check seems to be failing on an issue unrelated to this PR.

@gianarb
Copy link
Contributor

gianarb commented Jan 25, 2021

Yep fixed via #44 , do you mind rebasing, please?
Thanks a lot!

@gianarb gianarb added the ready-to-merge Signal to Mergify to merge the PR. label Jan 26, 2021
@mergify mergify bot merged commit c67898e into tinkerbell:master Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Signal to Mergify to merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants