Network configurations check fail for RHEL7

[nZac]

OS: RHEL7
Vagrant: built from master to avoid #4438
Box: opscode/bento RHEL 7 (without chef.sh)
Possible duplicates of: #4259, #4195. #4078
Similar to: #2955

I am having one heck of a time getting a RHEL box up and running. The most recent of issues is:

==> dev: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth1 does not seem to be present, delaying initialization.

Stderr from the command:

The network configuration for this is:

  # Dev machine
  config.vm.define "dev" do |dev|
    dev.vm.network :private_network, ip: "192.168.20.90"
  end

I should note that the box does come up and I can vagrant ssh into it.

Any thoughts on the error?

[biemond]

I also got an error with centos 7.0 when adding a private network like this
admin.vm.network :private_network, ip: "10.10.10.10"

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/plugins/guests/redhat/cap/configure_networks.rb:23:in `configure_networks_rhel7': wrong number of arguments (1 for 2) (ArgumentError)
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/plugins/guests/redhat/cap/configure_networks.rb:17:in `configure_networks'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/capability_host.rb:111:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/capability_host.rb:111:in `capability'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/guest.rb:43:in `capability'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/plugins/providers/virtualbox/action/network.rb:132:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/action/warden.rb:34:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.4/lib/vagrant/action/warden.rb:34:in `call'

[andytson]

f4ee476#diff-c09c88e789bdb0c2c0ebc8d12cccf55dR26

Ruby stupidly treats a file like a directory in traversal (i.e. File.expand_path(".", __FILE__) == __FILE__), which this line is missing an extra ..

@biemond your specific error is from the 1.6.4 tag, which has had a fix for that in #4438, unrelated to the new issue @nZac is reporting

[andytson]

PR at #4461

Sorry for not going through testing the original fix for #4438 and finding this sooner. I've worked out how to use Vagrant as a gem so I can test this, and with this fix it succeeds in vagrant uping CentOS 7 (whereas similarly to RHEL7 it errored before)

[andytson]

hmm, actually @nZac's issue is different to the one I had (mine was just failing to attempt to load /path/to/gems/vagrant-1.6.4/plugins/guests/redhat/fedora/cap/configure_networks

[andytson]

I can confirm, there's two issues, one for each flavor:

• RHEL7 gets @nZac's error, and once fixed will get CentOS7's error
• CentOS7 gets the error Fixes #4450, add another expand_path ../ to get back to the guests directory #4461 fixes

[biemond]

Thanks

these 3 changes worked for me , now only got this issue #4352 over , it calls homenamectl and not hostnamectl plus does not set the new hostname in /etc/hosts

    def self.configure_networks(machine, networks)
      case machine.guest.capability("flavor")
      when :rhel_7
        configure_networks_rhel7(machine, networks)  <!------
      else
        configure_networks_default(machine, networks) <!------
      end
    end

    def self.configure_networks_rhel7(machine, networks)
      # This is kind of jank but the configure networks is the same
      # as Fedora at this point.
      require File.expand_path("../../../fedora/cap/configure_networks", __FILE__) <!------
      ::VagrantPlugins::GuestFedora::Cap::ConfigureNetworks.
        configure_networks(machine, networks)
    end

[andytson]

My RHEL 7 RC VM (not got a full release available due to 30 day trial expiring) has a /etc/redhat-release of:
Red Hat Enterprise Linux Server release 7.0 (Maipo)

[nZac]

@andytson, is this ready to test?

[andytson]

I believe more work is needed to support each RHEL flavor to match all supported /etc/redhat-release formats as this doesn't cover it: CentOS|Red Hat Enterprise) Linux release 7
https://github.com/mitchellh/vagrant/blob/master/plugins/guests/redhat/cap/flavor.rb#L14

[andytson]

perhaps (CentOS|Red Hat Enterprise) Linux.+release 7 (although RHEL 70 users will be cursing us in the future)

[nZac]

I am not nearly as familiar with Vagrant internals nor Ruby. If I can provide any additional information to assist in testing or debugging I am happy too!

[andytson]

I'm struggling to find the sources for each redhat-release rpm since they moved it all over to git.centos.org and not accurately said which project its in (they point to the CentOS source which isn't correct), but looking at their former ftp directory structure there are 4 RHEL variants that will have different /etc/redhat-release content:

http://ftp.redhat.com/pub/redhat/linux/enterprise/

[andytson]

I think Redhat merging CentOS into their organisation has gotten around the GPL issue by only referencing CentOS's source rather than RHEL's as they used to maybe.

[andytson]

@mitchellh please can you reopen this ticket, it turns out my fix is for CentOS7, although needed, isn't the issue RHEL7 is currently getting (though will be once this issue is fixed)

[mitchellh]

Yep, done :)

[andytson]

^ PR for the fix.

I've tested against both RHEL 7 Server and CentOS 7, but obviously not RHEL 7 Client/ComputeNode/Workstation

[kikitux]

@andytson What kind of information do you need from those channels?

I have a subscription to a lot of channels that cover Server/workstation, etc.

[andytson]

@kikitux I was thinking just checking the SRPMS for each RHEL7 flavour's redhat-release, to make sure the /etc/redhat-release they add all conform to the same regular expression as my PR. I expect they will.

i.e.

• download the SRPMS for redhat-release package for each flavor (RPMS would work as well)
• run rpm2cpio <myrpmfile.rpm> | cpio -idm to extract the source to the current folder
• check for output for it's https://git.centos.org/blob/rpms!centos-release/343ef8031fdee7fd8c17a85aeb0f457c423cd467/SPECS!centos-release.spec#L46
• or more easily for the compiled RPM version, check etc/redhat-release :)
• see if the resulting string matches the regex

[nZac]

@andytson, Thanks for all your work on this, it 1.6.5 works as expected!