rdbreak / rhcsa8env Goto Github PK

When using "# vagrant up" command I came across an annoying message which I don't want others to encounter:

########################################################
==> server2: Clearing any previously set network interfaces...

The IP address configured for the host-only network is not within the
allowed ranges. Please update the address used to be within the allowed
ranges and run the command again.

Address: 192.168.55.151
Ranges: 192.168.51.0/21

Valid ranges can be modified in the /etc/vbox/networks.conf file. For
more information including valid format see:

https://www.virtualbox.org/manual/ch06.html#network_hostonly
######################################################

So, the way to tackle this problem in my case was to:
--> Create the directory: /etc/vbox/
--> Create the networks.conf file under it and put the above ip network address range inside:
"* 192.168.55.0/24"
Save and quit and then run "# vagrant up" again to see it taking off.
Hope it was helpful.
Follow this link to understand it as well: https://www.sitepoint.com/community/t/homestead-vagrant-ip-address-not-within-allowed-ranges/377751

After a system reboot when i try vagrant up, it returns the following error. What is the mistake I'm making?

_[emtiazae@foundation0 rhcsa8env]$ vagrant up
Bringing machine 'server2' up with 'virtualbox' provider...
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'server1' up with 'virtualbox' provider...
==> server2: Clearing any previously set forwarded ports...
==> server2: Clearing any previously set network interfaces...
==> server2: Preparing network interfaces based on configuration...
server2: Adapter 1: nat
server2: Adapter 2: hostonly
server2: Adapter 3: hostonly
server2: Adapter 4: hostonly
==> server2: Forwarding ports...
server2: 22 (guest) => 2222 (host) (adapter 1)
==> server2: Running 'pre-boot' VM customizations...
A customization command failed:

["storagectl", :id, "--name", "SATA Controller", "--add", "sata", "--portcount", 2]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["storagectl", "42bf69ca-999a-4267-b7a5-64d5aad4130a", "--name", "SATA Controller", "--add", "sata", "--portcount", "2"]

Stderr: VBoxManage: error: Storage controller named 'SATA Controller' already exists
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "AddStorageController(Bstr(pszCtl).raw(), StorageBus_SATA, ctl.asOutParam())" at line 1080 of file VBoxManageStorageController.cpp

Please fix this customization and try again.
[emtiazae@foundation0 rhcsa8env]$_

repo: Downloading Packages: repo: Running transaction check repo: Transaction check succeeded. repo: Running transaction test repo: Transaction test succeeded. repo: Running transaction repo: Preparing : 1/1 repo: repo: Installing : epel-release-7-12.noarch 1/1 repo: repo: Running scriptlet: epel-release-7-12.noarch 1/1 repo: repo: Verifying : epel-release-7-12.noarch 1/1 repo: repo: Installed products updated. repo: repo: Installed: repo: epel-release-7-12.noarch repo: Complete! repo: Updating Subscription Management repositories. repo: Unable to read consumer identity repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. repo: Extra Packages for Enterprise Linux 7 - x86_64 0.0 B/s | 0 B 00:01 repo: Failed to synchronize cache for repo 'epel', ignoring this repo. repo: Last metadata expiration check: 0:03:57 ago on Mon 19 Oct 2020 10:32:56 PM PDT. repo: No match for argument: sshpass repo: Package httpd-2.4.37-10.module+el8+2764+7127e69e.x86_64 is already installed. repo: No match for argument: sshpass repo: Error: Unable to find a match The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

The box 'rdbreak/rhel8node' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
vagrant login. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://vagrantcloud.com/rdbreak/rhel8node"]
Error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.

When creating the VM, I get the following error:
==> server2: Clearing any previously set network interfaces...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "ipconfig", "vboxnet0", "--ip", "192.168.55.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

This seems like a issue with the latest Virtualbox versions (I'm on 6.1.32).

Hello,

I'm using Windows 11 and I ran into this issue when I tried vagrant up :

`There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /cygdrive/d/rhcsa8env/
Guest path: /vagrant
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--chmod=ugo=rwX" "--no-perms" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i 'C:/Users/magri/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8repo/1.1/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" "*.vdi" "/cygdrive/d/rhcsa8env/" "[email protected]:/vagrant"
Error: rsync: write failed on "/vagrant/disk-0-2.vdi": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]`

httpd manual is present in the repo but not the service itself

Describe the bug
rdbreak/rhel8repo => it's creating a Big EMPTY file which using all the remaining space of VM. location of file is /EMPTY in Repo VM.

To Reproduce
Steps to reproduce the behavior:
create a fresh VM rdbreak/rhel8repo and you can see the file at /EMPTY

Expected behavior
it's using full space which causing issue to other command and VM/OS become unstable.

config.vm.define "repo" do |repo|
repo.vm.box = "rdbreak/rhel8repo"

Entire error output:

    repo: Unable to read consumer identity
    repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
    repo: Extra Packages for Enterprise Linux 7 - x86_64  0.0  B/s |   0  B     02:09
    repo: Failed to synchronize cache for repo 'epel', ignoring this repo.
    repo: Last metadata expiration check: 0:04:22 ago on Wed 28 Oct 2020 04:28:36 PM PDT.
    repo: No match for argument: sshpass
    repo: Package httpd-2.4.37-10.module+el8+2764+7127e69e.x86_64 is already installed.
    repo: No match for argument: sshpass
    repo: Error: Unable to find a match

Describe the bug
repo: ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device: '/tmp/pip-install-5n38sshq/ansible_7391cac23b3849dea69a623d71f26912/ansible_collections/ansible/windows/tests/integration/targets/setup_win_device/tasks'

To Reproduce
Steps to reproduce the behavior:

1. Follow the deployment procedure for Windows
2. Implement fix for issue#43
3. vagrant up
4. See error in description + The SSH command responded with a non-zero exit status. Vagrant
   assumes that this means the command failed. The output for this command
   should be in the log above. Please read the output to determine what
   went wrong.

Expected behavior
Deployment runs smoothly till the end

Desktop (please complete the following information):

• OS: Windows 10
• Version: whatever
• Vbox: 6.1.22

Additional context
Workaround:

1. vagrant plugin install vagrant-disksize
2. add the following at line 62 and 63 in the Vagrantfile
   repo.disksize.size = '50GB'
   repo.vm.provision :shell, :inline => "parted -s -a opt /dev/sda 'resizepart 2 100%' ; pvresize /dev/sda2 ; lvextend -l +100%FREE /dev/mapper/rhel_rhel8-root ; xfs_growfs /dev/mapper/rhel_rhel8-root", run: "always"

it's showing old epel 7 repo.
rhel8 (line 64 ) must be https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm

Hey is it possible to get a link for the slack group again?

Got my test on friday! :)

Thanks in advance

ran variant up and it only installed server 1 and the repo server. Did a variant destroy and tried it again. Still no server 1.

Getting this error:

repo: [MIRROR] epel-release-latest-7.noarch.rpm: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]
repo: [FAILED] epel-release-latest-7.noarch.rpm: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]
repo: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]

and this one at the end:

repo: No match for argument: sshpass
repo: Error: Unable to find a match
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Help ?

How can I completely clean the env ? I also have some other vm's setup in virtual box. Is there a limit as to how many I can have ? doc on Virtual box says I am only limited by mem and cpu of host system.

using Win10 env.

Describe the bug
Error: rsync: write failed on "/vagrant/disk-0-1.vdi": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]

server1: VM not created

To Reproduce
Steps to reproduce the behavior:

1. Go to 'cd .\RHCSA\rhcsa8env-master'
2. Click on 'vagrant up'
3. Scroll down to '....'
4. See error

PS C:\WINDOWS\system32> cd d:
PS D:> cd .\RHCSA
PS D:\RHCSA>
PS D:\RHCSA> cd .\rhcsa8env-master
PS D:\RHCSA\rhcsa8env-master> vagrant up
Bringing machine 'server2' up with 'virtualbox' provider...
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'server1' up with 'virtualbox' provider...
==> server2: Box 'rdbreak/rhel8node' could not be found. Attempting to find and install...
server2: Box Provider: virtualbox
server2: Box Version: >= 0
==> server2: Loading metadata for box 'rdbreak/rhel8node'
server2: URL: https://vagrantcloud.com/rdbreak/rhel8node
==> server2: Adding box 'rdbreak/rhel8node' (v1.0) for provider: virtualbox
server2: Downloading: https://vagrantcloud.com/rdbreak/boxes/rhel8node/versions/1.0/providers/virtualbox.box
==> server2: Box download is resuming from prior download progress
Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com
server2:
==> server2: Successfully added box 'rdbreak/rhel8node' (v1.0) for 'virtualbox'!
==> server2: Importing base box 'rdbreak/rhel8node'...
==> server2: Matching MAC address for NAT networking...
==> server2: Setting the name of the VM: rhcsa8env-master_server2_1616926384513_43393
==> server2: Clearing any previously set network interfaces...
==> server2: Preparing network interfaces based on configuration...
server2: Adapter 1: nat
server2: Adapter 2: hostonly
server2: Adapter 3: hostonly
server2: Adapter 4: hostonly
==> server2: Forwarding ports...
server2: 22 (guest) => 2222 (host) (adapter 1)
==> server2: Running 'pre-boot' VM customizations...
==> server2: Booting VM...
==> server2: Waiting for machine to boot. This may take a few minutes...
server2: SSH address: 127.0.0.1:2222
server2: SSH username: vagrant
server2: SSH auth method: private key
==> server2: Machine booted and ready!
==> server2: Checking for guest additions in VM...
server2: The guest additions on this VM do not match the installed version of
server2: VirtualBox! In most cases this is fine, but in rare cases it can
server2: prevent things such as shared folders from working properly. If you see
server2: shared folder errors, please make sure the guest additions within the
server2: virtual machine match the version of VirtualBox you have installed on
server2: your host and reload your VM.
server2:
server2: Guest Additions Version: 5.2.30 r130521
server2: VirtualBox Version: 6.1
==> server2: Configuring and enabling network interfaces...
==> server2: Rsyncing folder: /cygdrive/d/RHCSA/rhcsa8env-master/ => /vagrant
==> server2: - Exclude: [".vagrant/", ".git/"]
==> server2: Running provisioner: shell...
server2: Running: inline script
server2: mke2fs 1.44.3 (10-July-2018)
server2: Creating filesystem with 2097152 4k blocks and 524288 inodes
server2: Filesystem UUID: 033feaba-606e-4e03-a2fc-a9900a1964d7
server2: Superblock backups stored on blocks:
server2: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
server2:
server2: Allocating group tables: 0/64
server2: done
server2: Writing inode tables: done
server2: Creating journal (16384 blocks):
server2: done
server2: Writing superblocks and filesystem accounting information:
server2: 0/64
server2:
server2: done
==> server2: Running provisioner: shell...
server2: Running: inline script
==> server2: Running provisioner: shell...
server2: Running: inline script
server2: mke2fs 1.44.3 (10-July-2018)
server2: Creating filesystem with 2097152 4k blocks and 524288 inodes
server2: Filesystem UUID: 12e4264c-dabd-42ab-a18a-a99990964e60
server2: Superblock backups stored on blocks:
server2: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
server2:
server2: Allocating group tables: 0/64
server2:
server2: done
server2: Writing inode tables: done
server2: Creating journal (16384 blocks):
server2: done
server2: Writing superblocks and filesystem accounting information:
server2: 0/64
server2: 26/64
server2:
server2: done
==> server2: Running provisioner: shell...
server2: Running: inline script
==> server2: Running provisioner: ansible_local...
server2: Running ansible-playbook...

PLAY [Setting Up Server 2] *****************************************************

TASK [Setting Up Python] *******************************************************
changed: [server2.eight.example.com]

TASK [Setting Hostname] ********************************************************
changed: [server2.eight.example.com]

TASK [Configuring network] *****************************************************
changed: [server2.eight.example.com]

TASK [Reloading Network] *******************************************************
changed: [server2.eight.example.com]

TASK [Building Host File] ******************************************************
changed: [server2.eight.example.com]

TASK [Erasing Repos] ***********************************************************
changed: [server2.eight.example.com]

TASK [Creating Temporary Repo File] ********************************************
changed: [server2.eight.example.com]

TASK [Building Repo File] ******************************************************
changed: [server2.eight.example.com]

TASK [Environment Packages Installed.] *****************************************
ok: [server2.eight.example.com]

TASK [Starting services] *******************************************************
ok: [server2.eight.example.com] => (item=firewalld)
changed: [server2.eight.example.com] => (item=httpd)

TASK [Erasing Repos] ***********************************************************
changed: [server2.eight.example.com]

TASK [Changing User Password] **************************************************
changed: [server2.eight.example.com]

TASK [Changing Root Password] **************************************************
changed: [server2.eight.example.com]

TASK [Creating Welcome Message] ************************************************
changed: [server2.eight.example.com]

TASK [Building Welcome Message then rebooting] *********************************
changed: [server2.eight.example.com]

TASK [Adjusting Services and Rebooting] ****************************************
changed: [server2.eight.example.com]

PLAY RECAP *********************************************************************
server2.eight.example.com : ok=16 changed=15 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0

==> server2: Running provisioner: shell...
server2: Running: inline script
==> repo: Box 'rdbreak/rhel8repo' could not be found. Attempting to find and install...
repo: Box Provider: virtualbox
repo: Box Version: >= 0
==> repo: Loading metadata for box 'rdbreak/rhel8repo'
repo: URL: https://vagrantcloud.com/rdbreak/rhel8repo
==> repo: Adding box 'rdbreak/rhel8repo' (v1.1) for provider: virtualbox
repo: Downloading: https://vagrantcloud.com/rdbreak/boxes/rhel8repo/versions/1.1/providers/virtualbox.box
Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com
repo:
==> repo: Successfully added box 'rdbreak/rhel8repo' (v1.1) for 'virtualbox'!
==> repo: Importing base box 'rdbreak/rhel8repo'...
==> repo: Matching MAC address for NAT networking...
==> repo: Setting the name of the VM: rhcsa8env-master_repo_1616928884347_82773
==> repo: Fixed port collision for 22 => 2222. Now on port 2200.
==> repo: Clearing any previously set network interfaces...
==> repo: Preparing network interfaces based on configuration...
repo: Adapter 1: nat
repo: Adapter 2: hostonly
==> repo: Forwarding ports...
repo: 22 (guest) => 2200 (host) (adapter 1)
==> repo: Running 'pre-boot' VM customizations...
==> repo: Booting VM...
==> repo: Waiting for machine to boot. This may take a few minutes...
repo: SSH address: 127.0.0.1:2200
repo: SSH username: vagrant
repo: SSH auth method: private key
==> repo: Machine booted and ready!
==> repo: Checking for guest additions in VM...
==> repo: Configuring and enabling network interfaces...
==> repo: Installing rsync to the VM...
==> repo: Rsyncing folder: /cygdrive/d/RHCSA/rhcsa8env-master/ => /vagrant
==> repo: - Exclude: [".vagrant/", ".git/"]
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /cygdrive/d/RHCSA/rhcsa8env-master/
Guest path: /vagrant
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--chmod=ugo=rwX" "--no-perms" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i 'C:/Users/Marek/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8repo/1.1/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" ".git/" "/cygdrive/d/RHCSA/rhcsa8env-master/" "[email protected]:/vagrant"
Error: rsync: write failed on "/vagrant/disk-0-1.vdi": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]

Desktop :

• OS: [Windows 10 AMD Ryzen 7 3700X 8-Core Processor 3.60 GHz, RAM 16,0 GB]
• Browser [firefox]
• Version Edition
  Windows 10 Pro
  Version 20H2
  Installed on ‎23. ‎7. ‎2020
  OS build 19042.867
  Experience Windows Feature Experience Pack 120.2212.551.0

Additional context
same problem also on another PC

Thanks

local repo hosted on http://ipa.eight.example.com/rpms does not include packages:

vdo
kmod-kvdo
stratis-cli
stratisd

packages needed for studying per RHCSAv8 objectives

Can you please put an updated link to the Slack workspace in the About section? The current link has expired and without it I can't see the practice exam tasks.

I am new to Mac and am trying to install this on Mac. It all goes well but when I run it I have to run it with sudo from the command line. I already had virtual box installed but it does not see the VM's unless i run as sudo, and when I do then my other VM's don't appear.

What did I do wrong?

repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo: Last metadata expiration check: 0:01:42 ago on Mon 18 Jan 2021 10:25:16 PM PST.
repo: [MIRROR] epel-release-latest-7.noarch.rpm: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]
repo: [FAILED] epel-release-latest-7.noarch.rpm: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]
repo: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]
repo: Updating Subscription Management repositories.
repo: Unable to read consumer identity
repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo: Last metadata expiration check: 0:02:03 ago on Mon 18 Jan 2021 10:25:16 PM PST.
repo: No match for argument: sshpass
repo: Package httpd-2.4.37-10.module+el8+2764+7127e69e.x86_64 is already installed.
repo: No match for argument: sshpass
repo: Error: Unable to find a match
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
To Reproduce
Steps to reproduce the behavior:
run vagrant up

Expected behavior
doesnt complete fails to resolve Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
-windows 10

Additional context
i can get to both sites in the browser
ttps://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org]

VirtualBox version:
VirtualBox-6.1.x86_64

Vagrant Version:
Vagrant 2.2.7

OS:
Linux 5.4.19-200.fc31.x86_64

Error during vagrant up server2
Stderr: VBoxManage: error: Storage controller named 'SATA Controller' already exists VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee nsISupports

It is the first time that i use vagrant, but I fixed it in modifying Vagrantfile in this way

diff Vagrantfile Vagrantfile.ori 
24,27c24,25
<     if not File.exist?(file_to_disk1)
<       server2.customize ['storagectl', :id, '--name', 'SATA Controller', '--add', 'sata', '--portcount', 2]
<       server2.customize ['storageattach', :id,  '--storagectl', 'SATA Controller', '--port', 1, '--device', 0, '--type', 'hdd', '--medium', file_to_disk1]
<     end
-----------------------------
>     server2.customize ['storagectl', :id, '--name', 'SATA Controller', '--add', 'sata', '--portcount', 2]
>     server2.customize ['storageattach', :id,  '--storagectl', 'SATA Controller', '--port', 1, '--device', 0, '--type', 'hdd', '--medium', file_to_disk1]

I hope that this could be helpful.

Hi,
I'm getting this error when i try to run vagrant up from vagrant halt state.

PS C:\Users\Administrator\bin\rhcsa8env-master> vagrant up
Bringing machine 'server2' up with 'virtualbox' provider...
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'server1' up with 'virtualbox' provider...
==> server2: Clearing any previously set forwarded ports...
==> server2: Fixed port collision for 22 => 2222. Now on port 2201.
==> server2: Clearing any previously set network interfaces...
==> server2: Preparing network interfaces based on configuration...
server2: Adapter 1: nat
server2: Adapter 2: hostonly
server2: Adapter 3: hostonly
server2: Adapter 4: hostonly
==> server2: Forwarding ports...
server2: 22 (guest) => 2201 (host) (adapter 1)
==> server2: Running 'pre-boot' VM customizations...
A customization command failed:

["storagectl", :id, "--name", "SATA Controller", "--add", "sata", "--portcount", 2]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["storagectl", "b04c4829-42e5-4ba9-8049-dfa1b673613a", "--name", "SATA Controller", "--add", "sata", "--portcount", "2"]

Stderr: VBoxManage.exe: error: Storage controller named 'SATA Controller' already exists
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "AddStorageController(Bstr(pszCtl).raw(), StorageBus_SATA, ctl.asOutParam())" at line 1080 of file VBoxManageStorageController.cpp

Please fix this customization and try again.
PS C:\Users\Administrator\bin\rhcsa8env-master>

There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

==> repo: Installing rsync to the VM...
==> repo: Rsyncing folder: /Users/myuser/bin/rhcsa8env/ => /vagrant
==> repo: - Exclude: [".vagrant/", ".git/"]
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /Users/myuser/bin/rhcsa8env/
Guest path: /vagrant
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/var/folders/21/9wxrkpfn6jn_8g5k86ch_4c00000gn/T/vagrant-rsync-20210329-9387-zd7oz5 -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/Users/myuser/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8repo/1.1/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" ".git/" "/Users/myuser/bin/rhcsa8env/" "[email protected]:/vagrant"
Error: rsync: writefd_unbuffered failed to write 4110 bytes [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (168 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-55/rsync/io.c(453) [sender=2.6.9]

gabriels-macbook-pro:rhcsa8env myuser$ "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/var/folders/21/9wxrkpfn6jn_8g5k86ch_4c00000gn/T/vagrant-rsync-20210329-9387-zd7oz5 -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/Users/myuser/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8repo/1.1/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" ".git/" "/Users/myuser/bin/rhcsa8env/" "[email protected]:/vagrant"
libtsocks: Unresolved symbol: close
building file list ... done
./
disk-0-1.vdi
rsync: writefd_unbuffered failed to write 4112 bytes [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (36 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-55/rsync/io.c(453) [sender=2.6.9]

Hey!

Could you please update the repository. The current rpm version of podman that is on this server is 1.0.2-dev
This package is outdated and doesn't support creating systemd unit files what is needed for the exam.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

I've tried creating podman containers in my RHEL8 home lab a hundred times and always get error:
systemctl --user enable --now container-logserver.service Failed to connect to bus: No such file or directory
I'm setup using this vagrant network with the 3 vms and can't get podman containers to work. I'm doing it exactly how I was shown in Sander Van Vugt video course.

Local repo on ipa server not reachable on the system1 server -- FIXED

Unless VirtualBox 6 was installed on host machine, VirtualBox would not reliably spin up both the ipa server and system1 server -- FIXED

Virtualbox Version: 6.1.6_Ubuntu r137129
Vagrant Version: 2.2.9
OS: Ubuntu 20.04 LTS

When i run vagrant up command the following issue appears and it stops vagrant from continuing

A customization command failed:

["storagectl", :id, "--name", "SATA Controller", "--add", "sata", "--portcount", 2]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["storagectl", "bc0931a1-b0b1-4589-a847-a4d39685910e", "--name", "SATA Controller", "--add", "sata", "--portcount", "2"]

Stderr: VBoxManage: error: Storage controller named 'SATA Controller' already exists
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "AddStorageController(Bstr(pszCtl).raw(), StorageBus_SATA, ctl.asOutParam())" at line 1078 of file VBoxManageStorageController.cpp
>

Please fix this customization and try again.

Describe the bug
Can't start machines

PS E:\Education\MinimumVagrant\RGEL8\rhcsa8env> vagrant.exe --version
Vagrant 2.2.17

PS E:\Education\MinimumVagrant\RGEL8\rhcsa8env> dir


    Каталог: E:\Education\MinimumVagrant\RGEL8\rhcsa8env


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        29.07.2021     22:08                .github
d-----        03.08.2021     12:37                .vagrant
d-----        29.07.2021     22:08                playbooks
-a----        29.07.2021     22:08             42 .gitignore
-a----        29.07.2021     22:08            410 ansible.cfg
-a----        03.08.2021     15:49     8592031744 disk-0-1.vdi
-a----        03.08.2021     15:50     8592031744 disk-0-2.vdi
-a----        29.07.2021     22:08            462 inventory
-a----        29.07.2021     22:08           1085 LICENSE
-a----        29.07.2021     22:08          12391 README.md
-a----        24.10.2020      4:23         520187 rsync.exe
-a----        03.08.2021     14:08           1184 rsync.lnk
-a----        29.07.2021     22:08           4436 Vagrantfile

To Reproduce
Steps to reproduce the behavior:
firstly, had an error with rsync, some of command is an attempt to fix it (successfully)

vagrant plugin install vagrant-rsync-back
vagrant plugin install vagrant-vbguest
vagrant plugin install vagrant-guest_ansible

vagrant.exe up

Output

PS E:\Education\MinimumVagrant\RGEL8\rhcsa8env> vagrant.exe up
Bringing machine 'server2' up with 'virtualbox' provider...
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'server1' up with 'virtualbox' provider...
==> server2: Importing base box 'rdbreak/rhel8node'...
==> server2: Matching MAC address for NAT networking...
==> server2: Setting the name of the VM: rhcsa8env_server2_1627994853571_39655
==> server2: Clearing any previously set network interfaces...
==> server2: Preparing network interfaces based on configuration...
    server2: Adapter 1: nat
    server2: Adapter 2: hostonly
    server2: Adapter 3: hostonly
==> server2: Forwarding ports...
    server2: 22 (guest) => 2222 (host) (adapter 1)
==> server2: Running 'pre-boot' VM customizations...
==> server2: Booting VM...
==> server2: Waiting for machine to boot. This may take a few minutes...
    server2: SSH address: 127.0.0.1:2222
    server2: SSH username: vagrant
    server2: SSH auth method: private key
==> server2: Machine booted and ready!
[server2] GuestAdditions versions on your host (6.1.26) and guest (5.2.30) do not match.
Updating Subscription Management repositories.
Unable to read consumer identity
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Error: There are no enabled repos.
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: not mounted.
==> server2: Checking for guest additions in VM...
    server2: The guest additions on this VM do not match the installed version of
    server2: VirtualBox! In most cases this is fine, but in rare cases it can
    server2: prevent things such as shared folders from working properly. If you see
    server2: shared folder errors, please make sure the guest additions within the
    server2: virtual machine match the version of VirtualBox you have installed on
    server2: your host and reload your VM.
    server2:
    server2: Guest Additions Version: 5.2.30
    server2: VirtualBox Version: 6.1
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

umount /mnt

Stdout from the command:



Stderr from the command:

umount: /mnt: not mounted.

Expected behavior
Running structure

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: chrome
• Version: 91.0.4472.124

Additional context
Fixing problem with rsync

https://www.vagrantup.com/docs/synced-folders/rsync
http://repo.msys2.org/msys/x86_64/rsync-3.2.3-1-x86_64.pkg.tar.zst
https://www.reddit.com/r/unix/comments/kl15ow/im_trying_to_extract_a_zstd_file_but_i_cant_do_it/
https://github.com/facebook/zstd

PS C:\Program Files\zstd> dir "c:\Program Files\zstd\"
Directory: C:\Program Files\zstd
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        03.08.2021     13:29                dll
d-----        03.08.2021     13:29                example
d-----        03.08.2021     13:29                include
d-----        03.08.2021     13:29                static
-a----        19.12.2020      2:06           2953 README.md
-a----        03.08.2021     13:05         354320 rsync-3.2.3-1-x86_64.pkg.tar.zst
-a----        19.12.2020      2:06           2953 win rsync — todo steps.md
-a----        19.12.2020      2:11        1275277 zstd.exe

PS C:\Program Files\zstd> .\zstd.exe  --decompress rsync-3.2.3-1-x86_64.pkg.tar.zst
rsync-3.2.3-1-x86_64.pkg.tar.zst: 686080 bytes
8. tar was unpacked by TTCMD c:\Program Files\rsync\

getting below error while try to set environment

==> repo: Installing rsync to the VM...
==> repo: Rsyncing folder: /cygdrive/e/rhcsa8env-master/rhcsa8env-master/ => /vagrant
==> repo: - Exclude: [".vagrant/", ".git/"]
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /cygdrive/e/rhcsa8env-master/rhcsa8env-master/
Guest path: /vagrant
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--chmod=ugo=rwX" "--no-perms" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i 'C:/Users/Inaya/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8repo/1.1/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" ".git/" "/cygdrive/e/rhcsa8env-master/rhcsa8env-master/" "[email protected]:/vagrant"
Error: rsync: write failed on "/vagrant/disk-0-1.vdi": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]

Hello there,

First of all, thank you very much for taking the trouble for preparing the study materials. By the way, I am trying to install the rhcsa8env on my centos8. I am getting this error

*Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:

Unable to resolve dependency: user requested 'vagrant-guest-ansible (> 0)'
*

I have tried to figure it out by googling but was at my wits end.
Looking forward to hear from u.

Thanking you in advance.

The link provided to the slack channel is not working? I was wonder if that can be updated or if anyone can send me some practice questions for RHCSA8?

Thanks!

Hi,

It would be good to have the minimum system requirements (cpu, RAM and storage) in the README page, it helps to have proper setup before we start installation. As an optional info, typical amount of time required for installation may be helpful for few who might start thinking it finishes in 10mins :-)

Hi, @rdbreak
I tried to make the Lab Network Diagram for rhcsa8env. It helps understand the environment faster.
Would you like to place it into the current git repo?
RHCSA8-Net-Diagram.pdf

[Advit@fedora rhcsa8env-master]$ vagrant up
The provider 'virtualbox' that was requested to back the machine
'server2' is reporting that it isn't usable on this system. The
reason is shown below:

VirtualBox is complaining that the kernel module is not loaded. Please
run VBoxManage --version or open the VirtualBox GUI to see the error
message which should contain instructions on how to fix this error.
[Advit@fedora rhcsa8env-master]$ cat /etc/^C
[Advit@fedora rhcsa8env-master]$ uname -a
Linux fedora 5.14.10-300.fc35.x86_64 #1 SMP Thu Oct 7 20:48:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Describe the bug
The requested URL returned error: 416

To Reproduce
Steps to reproduce the behavior:
after running vagrant up

Expected behavior
1st VM was installed but this happened while 2nd VM installing

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser Chrome
• Version 98

Additional context
When 1st time I tried to install this suddenly had a power cut damn u Sri Lankan government 😒 then I tried to install this and got this error.

After installing/Download and unzip under /bin/rhcsa8env
I do vagrant up with root I get this:
_"No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
vagrant up --provider=PROVIDER, which should give you a more specific
error message for that particular provider."

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Fedora 34
• Browser firefox
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

on my Win-10 system the vagrant up fails with the error below. I also tries increasing disk size to 10G within the vagrant file. Any help would be appreciated. Thanks

There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /cygdrive/c/RHEL8Exam/rhcsa8env-master/
Guest path: /vagrant
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--chmod=ugo=rwX" "--no-perms" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i 'C:/Users/spari/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8repo/1.1/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" ".git/" "/cygdrive/c/RHEL8Exam/rhcsa8env-master/" "[email protected]:/vagrant"
Error: rsync: write failed on "/vagrant/disk-0-1.vdi": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]

Hi all,

I have installed all other softwares in my CentOS8. Then when I tried to use "vagrant up" to deploy the environment, i received the following errors. I have two hard drives and I am not sure if it's related.

Bringing machine 'server2' up with 'virtualbox' provider...
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'server1' up with 'virtualbox' provider...
==> server2: Clearing any previously set forwarded ports...
==> server2: Clearing any previously set network interfaces...
==> server2: Preparing network interfaces based on configuration...
server2: Adapter 1: nat
server2: Adapter 2: hostonly
server2: Adapter 3: hostonly
server2: Adapter 4: hostonly
==> server2: Forwarding ports...
server2: 22 (guest) => 2222 (host) (adapter 1)
==> server2: Running 'pre-boot' VM customizations...
A customization command failed:

["storagectl", :id, "--name", "SATA Controller", "--add", "sata", "--portcount", 2]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["storagectl", "d03f3308-2840-4b76-8dd6-0c7ecd164829", "--name", "SATA Controller", "--add", "sata", "--portcount", "2"]

Stderr: VBoxManage: error: Storage controller named 'SATA Controller' already exists
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "AddStorageController(Bstr(pszCtl).raw(), StorageBus_SATA, ctl.asOutParam())" at line 1080 of file VBoxManageStorageController.cpp

Please fix this customization and try again.

Hello,
I'm using Fedora 35 and I ran into this issue when I tried vagrant up

[dan@fedora rhcsa8env]$ sudo vagrant up
Bringing machine 'server2' up with 'virtualbox' provider...
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'server1' up with 'virtualbox' provider...
==> server2: Clearing any previously set network interfaces...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "ipconfig", "vboxnet1", "--ip", "192.168.55.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

Hello,
Is it possible to add 2 more drives to the server2 VM? It would be nice to be able to setup LVM in /dev/sdb and setup VDO and Stratis on /dev/sdc and /dev/sdd respectively. I attempted to alter the vagrant code that builds the VM's and sets up the hard drive on server2, but have not found success. If this is possible, it would make the environment more flexible for practicing partitioning and advanced storage as presented in the class.

Thanks for your consideration,
OpenCloudJedi

#!/usr/bin/ruby

STDERR.print <<EOS
Warning: The Ruby Homebrew installer is now deprecated and has been rewritten in
Bash. Please migrate to the following command:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

EOS

Kernel.exec "/bin/bash", "-c", '/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"'

I followed the procedure for CentOS 8. When I run # vagrant up I get

No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp

Hello,
Thank you for your contribute.
It seems that the invite link to Slack is no longer active and working.
This is the error message I get when following:
https://join.slack.com/t/redhat-certs/shared_invite/zt-7ju3rz7b-_G3Njp3PDwdBG_81SwPeLA

********* SNIP ***********
This link is no longer active

To join this workspace, you’ll need to ask the person who originally invited you for a new link.
********* SNIP ***********
thank you

Exactly what command is needed to access this link? dnf install nor yum install don't work.
"There is a Repo/AppStream available to use from http://repo.eight.example.com/BaseOS and http://repo.eight.example.com/AppStream"

Describe the bug
Slack link doesn't work.

To Reproduce
Steps to reproduce the behavior:

1. Click link to practice exams here:
   

Expected behavior
Practice exams open.

Screenshots
Here's what I see:

Desktop (please complete the following information):

• OS: RHEL 8.5
• Browser: Firefox
• Version 91.6

Additional context
I'm a Red Hatter. I'm logged into Slack.

Hi there!
I am using since 6/7 months this cool RHCSA environment on a win10 pc without any issue(also using the last virtual box and vagrant versions ; today I had to vagrant destroy everything and start the assessment exam from a new environment..so, after destroy -f, I have done a vagrant up...everything is going fine except for server2, that fails with this error:

INFO interface: detail: mke2fs 1.44.3 (10-July-2018)
The file /dev/sdb does not exist and no size was specified.
INFO interface: detail: server2: mke2fs 1.44.3 (10-July-2018)
server2: The file /dev/sdb does not exist and no size was specified.
server2: mke2fs 1.44.3 (10-July-2018)
server2: The file /dev/sdb does not exist and no size was specified.
DEBUG ssh: Exit status: 1
ERROR warden: Error occurred: The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

what is going wrong guys? after this error the VM server2 is deployed with minimal configuration (also no login banner is showed) I really need the environment in these days, my real exam is on 16th of decemberrr

PS: next time I will use the ansible-playbook playbooks/reset.yml command to reset the servers 1/2 for sure :))))

thanks!

The VirtualBox Guest Additions version on server2 does not match latest VirtualBox version.

Guest Additions Version: 5.2.30
VirtualBox Version: 6.0

This might cause issues for users in the future.

Steps to reproduce the behavior:

1. After running 'vagrant up' for the first time, the error occurs while it is checking for the guest additions in the VM.

INFO interface: detail: Requirement already up-to-date: pip in /usr/local/lib/python3.6/site-packages (20.2.3)
INFO interface: detail: repo: Requirement already up-to-date: pip in /usr/local/lib/python3.6/site-packages (20.2.3)
repo: Requirement already up-to-date: pip in /usr/local/lib/python3.6/site-packages (20.2.3)
INFO interface: detail: Collecting pexpect
INFO interface: detail: repo: Collecting pexpect
repo: Collecting pexpect
INFO interface: detail: Using cached pexpect-4.8.0-py2.py3-none-any.whl (59 kB)
INFO interface: detail: repo: Using cached pexpect-4.8.0-py2.py3-none-any.whl (59 kB)
repo: Using cached pexpect-4.8.0-py2.py3-none-any.whl (59 kB)
DEBUG ssh: stderr: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
pexpect from https://files.pythonhosted.org/packages/39/7b/88dbb785881c28a102619d46423cb853b46dbccc70d3ac362d99773a78ce/pexpect-4.8.0-py2.py3-none-any.whl#sha256=0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937:
Expected sha256 0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937
Got 6927f1fa55c7b4e96e42f119d28b6ef2497f04dca57af5d987bce7fac49e599d

INFO interface: detail: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
pexpect from https://files.pythonhosted.org/packages/39/7b/88dbb785881c28a102619d46423cb853b46dbccc70d3ac362d99773a78ce/pexpect-4.8.0-py2.py3-none-any.whl#sha256=0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937:
Expected sha256 0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937
Got 6927f1fa55c7b4e96e42f119d28b6ef2497f04dca57af5d987bce7fac49e599d
INFO interface: detail: repo: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
repo: pexpect from https://files.pythonhosted.org/packages/39/7b/88dbb785881c28a102619d46423cb853b46dbccc70d3ac362d99773a78ce/pexpect-4.8.0-py2.py3-none-any.whl#sha256=0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937:
repo: Expected sha256 0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937
repo: Got 6927f1fa55c7b4e96e42f119d28b6ef2497f04dca57af5d987bce7fac49e599d
repo: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
repo: pexpect from https://files.pythonhosted.org/packages/39/7b/88dbb785881c28a102619d46423cb853b46dbccc70d3ac362d99773a78ce/pexpect-4.8.0-py2.py3-none-any.whl#sha256=0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937:
repo: Expected sha256 0b48a55dcb3c05f3329815901ea4fc1537514d6ba867a152b581d69ae3710937
repo: Got 6927f1fa55c7b4e96e42f119d28b6ef2497f04dca57af5d987bce7fac49e599d
INFO interface: detail: Collecting ansible
INFO interface: detail: repo: Collecting ansible
repo: Collecting ansible
INFO interface: detail: Using cached ansible-2.9.13.tar.gz (14.3 MB)
INFO interface: detail: repo: Using cached ansible-2.9.13.tar.gz (14.3 MB)
repo: Using cached ansible-2.9.13.tar.gz (14.3 MB)
DEBUG ssh: stderr: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
ansible from https://files.pythonhosted.org/packages/32/62/eec759cd8ac89a866df1aba91abf785486fed7774188a41f42f5c7326dcb/ansible-2.9.13.tar.gz#sha256=3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644:
Expected sha256 3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644
Got 571e251c0c3cf58a38e8b0bc5e3f45b7fd346064eedab4e5c54ba221baae2438

INFO interface: detail: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
ansible from https://files.pythonhosted.org/packages/32/62/eec759cd8ac89a866df1aba91abf785486fed7774188a41f42f5c7326dcb/ansible-2.9.13.tar.gz#sha256=3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644:
Expected sha256 3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644
Got 571e251c0c3cf58a38e8b0bc5e3f45b7fd346064eedab4e5c54ba221baae2438
INFO interface: detail: repo: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
repo: ansible from https://files.pythonhosted.org/packages/32/62/eec759cd8ac89a866df1aba91abf785486fed7774188a41f42f5c7326dcb/ansible-2.9.13.tar.gz#sha256=3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644:
repo: Expected sha256 3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644
repo: Got 571e251c0c3cf58a38e8b0bc5e3f45b7fd346064eedab4e5c54ba221baae2438
repo: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
repo: ansible from https://files.pythonhosted.org/packages/32/62/eec759cd8ac89a866df1aba91abf785486fed7774188a41f42f5c7326dcb/ansible-2.9.13.tar.gz#sha256=3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644:
repo: Expected sha256 3ab21588992fbfe9de3173aefd63da1267dc12892a60f5cfdc055fe19c549644
repo: Got 571e251c0c3cf58a38e8b0bc5e3f45b7fd346064eedab4e5c54ba221baae2438
DEBUG ssh: Exit status: 1
ERROR warden: Error occurred: The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what

Running vagrant on Powershell in Windows as admin and I get the following error when installing the repo. It terminates after this. This is when I do 'vagrant up'.

==> repo: Running provisioner: shell... repo: Running: inline script repo: Updating Subscription Management repositories. repo: Unable to read consumer identity repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. repo: Last metadata expiration check: 0:02:02 ago on Thu 20 Aug 2020 07:39:37 AM PDT. repo: [MIRROR] epel-release-latest-7.noarch.rpm: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org] repo: [FAILED] epel-release-latest-7.noarch.rpm: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org] repo: Curl error (6): Couldn't resolve host name for https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm [Could not resolve host: dl.fedoraproject.org] repo: Updating Subscription Management repositories. repo: Unable to read consumer identity repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. repo: Last metadata expiration check: 0:02:04 ago on Thu 20 Aug 2020 07:39:37 AM PDT. repo: No match for argument: sshpass repo: Package httpd-2.4.37-10.module+el8+2764+7127e69e.x86_64 is already installed. repo: No match for argument: sshpass repo: Error: Unable to find a match The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

**repo: Failed to synchronize cache for repo 'epel', ignoring this repo.**
repo: epel-release-latest-7.noarch.rpm                 11 kB/s |  15 kB     00:01    
repo: Package epel-release-7-12.noarch is already installed.
repo: Dependencies resolved.
repo: Nothing to do.
repo: Complete!
repo: Updating Subscription Management repositories.
repo: Unable to read consumer identity
repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo: Extra Packages for Enterprise Linux 7 - x86_64  0.0  B/s |   0  B     00:01    
**repo: Failed to synchronize cache for repo 'epel', ignoring this repo.**
repo: Last metadata expiration check: 0:00:16 ago on Fri 27 Dec 2019 05:29:00 AM PST.
**repo: No match for argument: sshpass**
repo: Package httpd-2.4.37-10.module+el8+2764+7127e69e.x86_64 is already installed.
repo: No match for argument: sshpass
repo: Error: Unable to find a match

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
$ vagrant status
Current machine states:

system running (virtualbox)
repo running (virtualbox)
ipa not created (virtualbox)

**As of this issue submission repo is using image Oracle 8 **

as title says