Giter VIP home page Giter VIP logo

rhce8env's People

Contributors

dellipse avatar midu16 avatar nabbott2008 avatar oddly avatar quangln94 avatar rdbreak avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

rhce8env's Issues

Repo vm disk size issue

Hi,
after adding epel repo and try the download rpms, the issue occur about disk freespace,

Could you modify disk size in vagrantfile and vdi file for repo vm

Thanks in advance

Error: Connection to 127.0.0.1 closed by remote host.

Need support as I tried to install the environment by vagrant up but got the below error at stage server1
Note : I am using centos 7 and vmware hypervisor

==> server1: Importing base box 'rdbreak/rhel8node'...
==> server1: Matching MAC address for NAT networking...
==> server1: Setting the name of the VM: rhcsa8env_server1_1618497400946_46292
==> server1: Fixed port collision for 22 => 2222. Now on port 2201.
==> server1: Clearing any previously set network interfaces...
==> server1: Preparing network interfaces based on configuration...
server1: Adapter 1: nat
server1: Adapter 2: hostonly
==> server1: Forwarding ports...
server1: 22 (guest) => 2201 (host) (adapter 1)
==> server1: Running 'pre-boot' VM customizations...
==> server1: Booting VM...
==> server1: Waiting for machine to boot. This may take a few minutes...
server1: SSH address: 127.0.0.1:2201
server1: SSH username: vagrant
server1: SSH auth method: private key
==> server1: Machine booted and ready!
==> server1: Checking for guest additions in VM...
server1: The guest additions on this VM do not match the installed version of
server1: VirtualBox! In most cases this is fine, but in rare cases it can
server1: prevent things such as shared folders from working properly. If you see
server1: shared folder errors, please make sure the guest additions within the
server1: virtual machine match the version of VirtualBox you have installed on
server1: your host and reload your VM.
server1:
server1: Guest Additions Version: 5.2.30 r130521
server1: VirtualBox Version: 6.0
==> server1: Configuring and enabling network interfaces...
==> server1: Rsyncing folder: /root/rhcsa8env/ => /vagrant
==> server1: - 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: /root/rhcsa8env/
Guest path: /vagrant
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2201 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/tmp/vagrant-rsync-20210415-17981-y72n7j -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/root/.vagrant.d/boxes/rdbreak-VAGRANTSLASH-rhel8node/1.0/virtualbox/vagrant_private_key'" "--exclude" ".vagrant/" "--exclude" ".git/" "/root/rhcsa8env/" "[email protected]:/vagrant"
Error: Connection to 127.0.0.1 closed by remote host.
rsync: [sender] write error: Broken pipe (32)
rsync error: unexplained error (code 255) at io.c(820) [sender=3.1.2]

Vagrant doesn't support Virtualbox 6.1 yet. (Mac)

Installing with the command
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" && xcode-select --install &&brew install ansible ; brew install python ; brew cask install vagrant ; brew cask install VirtualBox ; brew cask install virtualbox-extension-pack ; vagrant plugin install vagrant-guest_ansible
works, it installs Virtualbox 6.1, but this is not yet supported by the version provided by Brew.
A solution is to pach Vagrant with these commands, or use the official Vagrant packages instead of the Brew cask ones.

VirtualBox can be blocked by HyperV

Running the 'vagrant up' environment build will fail If HyperV is installed on the Windows VirtualBox host.
Error is usually "VT-x is not available. (VERR_VMX_NO_VMX)" or similar, when the script attempts to boot the first VM.

Resolution seems to be either remove HyperV, or preventing its hypervisor from starting with the command:
bcdedit /set hypervisorlaunchtype off

followed by a reboot.

Suggest a documentation update to mention this for the practice environments.

error while rebuilding env

Hi,
All work the first time with root or sudo user. After deleting every thing ( box and vm), i got the error:
repo: Error: Unable to find a match: sshpass
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.

Can u please help me

Regards

Repo vm will not provision with an error about not enough space for pip to install ansible.

Environments: RHEL 8.4 and Fedora 33.
F33 running the following pkgs:

vagrant-libvirt-0.1.2-1.fc33.noarch
vagrant-2.2.9-3.fc33.noarch
virtualbox-guest-additions-6.1.18-1.fc33.x86_64
VirtualBox-kmodsrc-6.1.18-1.fc33.noarch
akmod-VirtualBox-6.1.18-1.fc33.x86_64
VirtualBox-server-6.1.18-1.fc33.x86_64
VirtualBox-6.1.18-1.fc33.x86_64
kmod-VirtualBox-5.11.8-200.fc33.x86_64-6.1.18-1.fc33.x86_64

Running 'vagrant up' results in:

==> repo: Running provisioner: shell...
    repo: Running: inline script
    repo: Updating Subscription Management repositories.
    repo: Unable to read consumer identity
    repo: 
    repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
    repo: Last metadata expiration check: 0:47:29 ago on Wed 24 Mar 2021 09:43:18 PM PDT.
    repo: epel-release-latest-7.noarch.rpm                 64 kB/s |  15 kB     00:00    
    repo: Package epel-release-7-13.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: 
    repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
    repo: Last metadata expiration check: 0:47:30 ago on Wed 24 Mar 2021 09:43:18 PM PDT.
    repo: Package sshpass-1.06-1.el7.x86_64 is already installed.
    repo: Package python3-pip-9.0.3-13.el8.noarch is already installed.
    repo: Package python36-devel-3.6.8-1.module+el8+2710+846623d6.x86_64 is already installed.
    repo: Package httpd-2.4.37-30.module+el8.3.0+7001+0766b9e7.x86_64 is already installed.
    repo: Package vsftpd-3.0.3-28.el8.x86_64 is already installed.
    repo: Package createrepo_c-0.11.0-1.el8.x86_64 is already installed.
    repo: Dependencies resolved.
    repo: Nothing to do.
    repo: Complete!
==> repo: Running provisioner: shell...
    repo: Running: inline script
    repo: Requirement already satisfied: pip in /usr/local/lib/python3.6/site-packages (21.0.1)
    repo: Requirement already satisfied: pexpect in /usr/local/lib/python3.6/site-packages (4.8.0)
    repo: Requirement already satisfied: ptyprocess>=0.5 in /usr/local/lib/python3.6/site-packages (from pexpect) (0.7.0)
    repo: Collecting ansible
    repo:   Downloading ansible-3.1.0.tar.gz (31.1 MB)
    repo: ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device: '/tmp/pip-install-y4vxk1eb/ansible_ac2c1320a7644857a445e84eeefeb766/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospfv3.py'
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.

I have plenty of disk space available and have set my TMPDIR variable to /home:

[root@localhost rhce8env]# df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs         16G     0   16G   0% /dev
tmpfs            16G     0   16G   0% /dev/shm
tmpfs           6.3G  2.1M  6.3G   1% /run
/dev/nvme0n1p3  465G  168G  297G  37% /
/dev/nvme0n1p3  465G  168G  297G  37% /home
/dev/nvme0n1p2  976M  245M  665M  27% /boot
/dev/nvme0n1p1  599M   21M  579M   4% /boot/efi
tmpfs            16G   64K   16G   1% /tmp
tmpfs           3.2G  200K  3.2G   1% /run/user/1000

Please let me know if there's any other info I can provide. Thanks!

vagrant up issue

arshad@DESKTOP-C7451KF MINGW64 /d/github/ansible/rhce8env (master)
$ vagrant up
Bringing machine 'repo' up with 'virtualbox' provider...
Bringing machine 'node1' up with 'virtualbox' provider...
Bringing machine 'node2' up with 'virtualbox' provider...
Bringing machine 'node3' up with 'virtualbox' provider...
Bringing machine 'node4' up with 'virtualbox' provider...
Bringing machine 'control' up with 'virtualbox' provider...
==> repo: Importing base box 'rdbreak/rhel8repo'...
==> repo: Matching MAC address for NAT networking...
==> repo: Setting the name of the VM: rhce8env_repo_1711273380728_18854
==> 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] GuestAdditions versions on your host (7.0.12) and guest (6.1.18) 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.

Base 193 MB/s | 2.2 MB 00:00
AppStream 235 MB/s | 5.3 MB 00:00
Package kernel-devel-4.18.0-80.el8.x86_64 is already installed.
Package kernel-devel-4.18.0-240.15.1.el8_3.x86_64 is already installed.
Package kernel-devel-4.18.0-240.15.1.el8_3.x86_64 is already installed.
Package gcc-8.3.1-5.1.el8.x86_64 is already installed.
Package binutils-2.30-79.el8.x86_64 is already installed.
Package make-1:4.2.1-10.el8.x86_64 is already installed.
Package perl-interpreter-4:5.26.3-417.el8_3.x86_64 is already installed.
Package bzip2-1.0.6-26.el8.x86_64 is already installed.
Package elfutils-libelf-devel-0.180-1.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Copy iso file C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /mnt: WARNING: device write-protected, mounted read-only.
Installing Virtualbox Guest Additions 7.0.12 - guest version is 6.1.18
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing VirtualBox 7.0.12 Guest Additions for Linux 100%
VirtualBox Guest Additions installer
Removing installed version 6.1.18 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
4.18.0-240.15.1.el8_3.x86_64.
strip:/var/tmp/dracut.fBm55M/initramfs/usr/lib/modules/4.18.0-240.15.1.el8_3.x86_64/misc/vboxvideo.ko: could not create temporary file to hold stripped copy: No error
strip:/var/tmp/dracut.fBm55M/initramfs/usr/lib/modules/4.18.0-240.15.1.el8_3.x86_64/misc/vboxsf.ko: could not create temporary file to hold stripped copy: No error
strip:/var/tmp/dracut.fBm55M/initramfs/usr/lib/modules/4.18.0-240.15.1.el8_3.x86_64/misc/vboxguest.ko: could not create temporary file to hold stripped copy: No error
/bin/dracut: line 1927: /var/tmp/dracut.fBm55M/initramfs.img: No space left on device
dracut: dracut: creation of /boot/initramfs-4.18.0-240.15.1.el8_3.x86_64.img failed
dracut failed with exit status 1.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted or 'rcvboxadd reload' triggered
VirtualBox Guest Additions: reloading kernel modules and services
VirtualBox Guest Additions: kernel modules and services 7.0.12 r159484 reloaded
VirtualBox Guest Additions: NOTE: you may still consider to re-login if some
user session specific services (Shared Clipboard, Drag and Drop, Seamless or
Guest Screen Resize) were not restarted automatically
An error occurred during installation of VirtualBox Guest Additions 7.0.12. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> repo: Checking for guest additions in VM...
==> repo: Configuring and enabling network interfaces...
==> repo: Installing rsync to the VM...
==> repo: Rsyncing folder: /cygdrive/d/github/ansible/rhce8env/ => /vagrant
==> repo: - Exclude: [".vagrant/", ".git/"]
==> repo: Running provisioner: shell...
repo: Running: inline script
repo: Physical volume "/dev/sdb" successfully created.
repo: Volume group "rhel_rhel8" successfully extended
repo: Size of logical volume rhel_rhel8/root changed from <28.93 GiB (7405 extents) to 30.92 GiB (7916 extents).
repo: Logical volume rhel_rhel8/root successfully resized.
repo: meta-data=/dev/mapper/rhel_rhel8-root isize=512 agcount=4, agsize=1895680 blks
repo: = sectsz=512 attr=2, projid32bit=1
repo: = crc=1 finobt=1, sparse=1, rmapbt=0
repo: = reflink=1
repo: data = bsize=4096 blocks=7582720, imaxpct=25
repo: = sunit=0 swidth=0 blks
repo: naming =version 2 bsize=4096 ascii-ci=0, ftype=1
repo: log =internal log bsize=4096 blocks=3702, version=2
repo: = sectsz=512 sunit=0 blks, lazy-count=1
repo: realtime =none extsz=4096 blocks=0, rtextents=0
repo: data blocks changed from 7582720 to 8105984
==> repo: Running provisioner: shell...
repo: Running: inline script
==> repo: Running provisioner: shell...
repo: Running: inline script
repo: Updating Subscription Management repositories.
repo: Unable to read consumer identity
repo:
repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo:
repo: Last metadata expiration check: 0:01:17 ago on Sun 24 Mar 2024 02:43:38 AM PDT.
repo: epel-release-latest-7.noarch.rpm 9.5 kB/s | 15 kB 00:01
repo: Dependencies resolved.
repo: ================================================================================
repo: Package Architecture Version Repository Size
repo: ================================================================================
repo: Installing:
repo: epel-release noarch 7-14 @commandline 15 k
repo:
repo: Transaction Summary
repo: ================================================================================
repo: Install 1 Package
repo:
repo: Total size: 15 k
repo: Installed size: 25 k
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: Installing : epel-release-7-14.noarch 1/1
repo: Running scriptlet: epel-release-7-14.noarch 1/1
repo: Verifying : epel-release-7-14.noarch 1/1
repo: Installed products updated.
repo:
repo: Installed:
repo: epel-release-7-14.noarch
repo:
repo: Complete!
repo: Updating Subscription Management repositories.
repo: Unable to read consumer identity
repo:
repo: This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
repo:
repo: Extra Packages for Enterprise Linux 7 - x86_64 80 kB/s | 17 MB 03:34
repo: Last metadata expiration check: 0:01:21 ago on Sun 24 Mar 2024 02:47:15 AM PDT.
repo: Package httpd-2.4.37-30.module+el8.3.0+7001+0766b9e7.x86_64 is already installed.
repo: Dependencies resolved.
repo: =======================================================================================
repo: Package Arch Version Repo Size
repo: =======================================================================================
repo: Installing:
repo: createrepo_c x86_64 0.11.0-1.el8 AppStream 76 k
repo: python3-pip noarch 9.0.3-13.el8 AppStream 18 k
repo: python36-devel x86_64 3.6.8-1.module+el8+2710+846623d6 AppStream 16 k
repo: sshpass x86_64 1.06-1.el7 epel 21 k
repo: vsftpd x86_64 3.0.3-28.el8 AppStream 180 k
repo: Installing dependencies:
repo: annobin x86_64 8.64-1.el8 AppStream 187 k
repo: createrepo_c-libs x86_64 0.11.0-1.el8 AppStream 101 k
repo: drpm x86_64 0.3.0-14.el8 AppStream 71 k
repo: dwz x86_64 0.12-9.el8 AppStream 109 k
repo: efi-srpm-macros noarch 3-2.el8 AppStream 22 k
repo: ghc-srpm-macros noarch 1.4.2-7.el8 AppStream 9.4 k
repo: go-srpm-macros noarch 2-16.el8 AppStream 14 k
repo: ocaml-srpm-macros noarch 5-4.el8 AppStream 9.5 k
repo: openblas-srpm-macros noarch 2-2.el8 AppStream 8.0 k
repo: perl-srpm-macros noarch 1-25.el8 AppStream 11 k
repo: platform-python-devel x86_64 3.6.8-1.el8 AppStream 242 k
repo: python-rpm-macros noarch 3-37.el8 AppStream 14 k
repo: python-srpm-macros noarch 3-37.el8 AppStream 14 k
repo: python3-rpm-generators noarch 5-4.el8 AppStream 24 k
repo: python3-rpm-macros noarch 3-37.el8 AppStream 13 k
repo: python3-setuptools noarch 39.2.0-4.el8 Base 162 k
repo: python36 x86_64 3.6.8-1.module+el8+2710+846623d6 AppStream 19 k
repo: qt5-srpm-macros noarch 5.11.1-2.el8 AppStream 11 k
repo: redhat-rpm-config noarch 116-1.el8 AppStream 82 k
repo: rust-srpm-macros noarch 5-2.el8 AppStream 9.3 k
repo: unzip x86_64 6.0-41.el8 Base 193 k
repo: zip x86_64 3.0-23.el8 Base 270 k
repo: Downgrading:
repo: platform-python x86_64 3.6.8-1.el8 Base 78 k
repo: platform-python-pip noarch 9.0.3-13.el8 Base 1.8 M
repo: platform-python-setuptools noarch 39.2.0-4.el8 Base 632 k
repo: python3-libs x86_64 3.6.8-1.el8 Base 7.9 M
repo: Enabling module streams:
repo: python36 3.6
repo:
repo: Transaction Summary
repo: =======================================================================================
repo: Install 27 Packages
repo: Downgrade 4 Packages
repo:
repo: Total size: 12 M
repo: Total download size: 21 k
repo: Downloading Packages:
repo: sshpass-1.06-1.el7.x86_64.rpm 29 kB/s | 21 kB 00:00
repo: --------------------------------------------------------------------------------
repo: Total 10 kB/s | 21 kB 00:02
repo: warning: /var/cache/dnf/epel-a56bdfa2f5efdfb9/packages/sshpass-1.06-1.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
repo: Extra Packages for Enterprise Linux 7 - x86_64 1.6 MB/s | 1.6 kB 00:00
repo: Importing GPG key 0x352C64E5:
repo: Userid : "Fedora EPEL (7) [email protected]"
repo: Fingerprint: 91E9 7D7C 4A5E 96F1 7F3E 888F 6A2F AEA2 352C 64E5
repo: From : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
repo: Key imported successfully
repo: Running transaction check
repo: Transaction check succeeded.
repo: Running transaction test
repo: Transaction test succeeded.
repo: Running transaction
repo: Preparing : 1/1
repo: Downgrading : platform-python-pip-9.0.3-13.el8.noarch 1/35
repo: Downgrading : platform-python-setuptools-39.2.0-4.el8.noarch 2/35
repo: Downgrading : python3-libs-3.6.8-1.el8.x86_64 3/35
repo: Downgrading : platform-python-3.6.8-1.el8.x86_64 4/35
repo: Running scriptlet: platform-python-3.6.8-1.el8.x86_64 4/35
repo: Installing : python3-rpm-macros-3-37.el8.noarch 5/35
repo: Installing : python-srpm-macros-3-37.el8.noarch 6/35
repo: Installing : drpm-0.3.0-14.el8.x86_64 7/35
repo: Installing : createrepo_c-libs-0.11.0-1.el8.x86_64 8/35
repo: Installing : python-rpm-macros-3-37.el8.noarch 9/35
repo: Installing : python3-setuptools-39.2.0-4.el8.noarch 10/35
repo: Installing : python3-pip-9.0.3-13.el8.noarch 11/35
repo: Installing : python36-3.6.8-1.module+el8+2710+846623d6.x86_64 12/35
repo: Running scriptlet: python36-3.6.8-1.module+el8+2710+846623d6.x86_64 12/35
repo: Installing : python3-rpm-generators-5-4.el8.noarch 13/35
repo: Installing : rust-srpm-macros-5-2.el8.noarch 14/35
repo: Installing : qt5-srpm-macros-5.11.1-2.el8.noarch 15/35
repo: Installing : perl-srpm-macros-1-25.el8.noarch 16/35
repo: Installing : openblas-srpm-macros-2-2.el8.noarch 17/35
repo: Installing : ocaml-srpm-macros-5-4.el8.noarch 18/35
repo: Installing : go-srpm-macros-2-16.el8.noarch 19/35
repo: Installing : ghc-srpm-macros-1.4.2-7.el8.noarch 20/35
repo: Installing : efi-srpm-macros-3-2.el8.noarch 21/35
repo: Installing : dwz-0.12-9.el8.x86_64 22/35
repo: Installing : annobin-8.64-1.el8.x86_64 23/35
repo: Installing : unzip-6.0-41.el8.x86_64 24/35
repo: Installing : zip-3.0-23.el8.x86_64 25/35
repo: Installing : redhat-rpm-config-116-1.el8.noarch 26/35
repo: Installing : platform-python-devel-3.6.8-1.el8.x86_64 27/35
repo: Installing : python36-devel-3.6.8-1.module+el8+2710+846623d6.x8 28/35
repo: Running scriptlet: python36-devel-3.6.8-1.module+el8+2710+846623d6.x8 28/35
repo: Installing : createrepo_c-0.11.0-1.el8.x86_64 29/35
repo: Installing : vsftpd-3.0.3-28.el8.x86_64 30/35
repo: Running scriptlet: vsftpd-3.0.3-28.el8.x86_64 30/35
repo: Installing : sshpass-1.06-1.el7.x86_64 31/35
repo: Cleanup : platform-python-setuptools-39.2.0-6.el8.noarch 32/35
repo: Cleanup : platform-python-3.6.8-31.el8.x86_64 33/35
repo: Running scriptlet: platform-python-3.6.8-31.el8.x86_64 33/35
repo: Cleanup : platform-python-pip-9.0.3-18.el8.noarch 34/35
repo: Cleanup : python3-libs-3.6.8-31.el8.x86_64 35/35
repo: Running scriptlet: python3-libs-3.6.8-31.el8.x86_64 35/35
repo: Verifying : platform-python-3.6.8-1.el8.x86_64 1/35
repo: Verifying : platform-python-3.6.8-31.el8.x86_64 2/35
repo: Verifying : platform-python-pip-9.0.3-13.el8.noarch 3/35
repo: Verifying : platform-python-pip-9.0.3-18.el8.noarch 4/35
repo: Verifying : platform-python-setuptools-39.2.0-4.el8.noarch 5/35
repo: Verifying : platform-python-setuptools-39.2.0-6.el8.noarch 6/35
repo: Verifying : python3-libs-3.6.8-1.el8.x86_64 7/35
repo: Verifying : python3-libs-3.6.8-31.el8.x86_64 8/35
repo: Verifying : sshpass-1.06-1.el7.x86_64 9/35
repo: Verifying : python3-setuptools-39.2.0-4.el8.noarch 10/35
repo: Verifying : unzip-6.0-41.el8.x86_64 11/35
repo: Verifying : zip-3.0-23.el8.x86_64 12/35
repo: Verifying : annobin-8.64-1.el8.x86_64 13/35
repo: Verifying : createrepo_c-0.11.0-1.el8.x86_64 14/35
repo: Verifying : createrepo_c-libs-0.11.0-1.el8.x86_64 15/35
repo: Verifying : drpm-0.3.0-14.el8.x86_64 16/35
repo: Verifying : dwz-0.12-9.el8.x86_64 17/35
repo: Verifying : efi-srpm-macros-3-2.el8.noarch 18/35
repo: Verifying : ghc-srpm-macros-1.4.2-7.el8.noarch 19/35
repo: Verifying : go-srpm-macros-2-16.el8.noarch 20/35
repo: Verifying : ocaml-srpm-macros-5-4.el8.noarch 21/35
repo: Verifying : openblas-srpm-macros-2-2.el8.noarch 22/35
repo: Verifying : perl-srpm-macros-1-25.el8.noarch 23/35
repo: Verifying : platform-python-devel-3.6.8-1.el8.x86_64 24/35
repo: Verifying : python-rpm-macros-3-37.el8.noarch 25/35
repo: Verifying : python-srpm-macros-3-37.el8.noarch 26/35
repo: Verifying : python3-pip-9.0.3-13.el8.noarch 27/35
repo: Verifying : python3-rpm-generators-5-4.el8.noarch 28/35
repo: Verifying : python3-rpm-macros-3-37.el8.noarch 29/35
repo: Verifying : python36-3.6.8-1.module+el8+2710+846623d6.x86_64 30/35
repo: Verifying : python36-devel-3.6.8-1.module+el8+2710+846623d6.x8 31/35
repo: Verifying : qt5-srpm-macros-5.11.1-2.el8.noarch 32/35
repo: Verifying : redhat-rpm-config-116-1.el8.noarch 33/35
repo: Verifying : rust-srpm-macros-5-2.el8.noarch 34/35
repo: Verifying : vsftpd-3.0.3-28.el8.x86_64 35/35
repo: Installed products updated.
repo:
repo: Downgraded:
repo: platform-python-3.6.8-1.el8.x86_64
repo: platform-python-pip-9.0.3-13.el8.noarch
repo: platform-python-setuptools-39.2.0-4.el8.noarch
repo: python3-libs-3.6.8-1.el8.x86_64
repo:
repo: Installed:
repo: annobin-8.64-1.el8.x86_64
repo: createrepo_c-0.11.0-1.el8.x86_64
repo: createrepo_c-libs-0.11.0-1.el8.x86_64
repo: drpm-0.3.0-14.el8.x86_64
repo: dwz-0.12-9.el8.x86_64
repo: efi-srpm-macros-3-2.el8.noarch
repo: ghc-srpm-macros-1.4.2-7.el8.noarch
repo: go-srpm-macros-2-16.el8.noarch
repo: ocaml-srpm-macros-5-4.el8.noarch
repo: openblas-srpm-macros-2-2.el8.noarch
repo: perl-srpm-macros-1-25.el8.noarch
repo: platform-python-devel-3.6.8-1.el8.x86_64
repo: python-rpm-macros-3-37.el8.noarch
repo: python-srpm-macros-3-37.el8.noarch
repo: python3-pip-9.0.3-13.el8.noarch
repo: python3-rpm-generators-5-4.el8.noarch
repo: python3-rpm-macros-3-37.el8.noarch
repo: python3-setuptools-39.2.0-4.el8.noarch
repo: python36-3.6.8-1.module+el8+2710+846623d6.x86_64
repo: python36-devel-3.6.8-1.module+el8+2710+846623d6.x86_64
repo: qt5-srpm-macros-5.11.1-2.el8.noarch
repo: redhat-rpm-config-116-1.el8.noarch
repo: rust-srpm-macros-5-2.el8.noarch
repo: sshpass-1.06-1.el7.x86_64
repo: unzip-6.0-41.el8.x86_64
repo: vsftpd-3.0.3-28.el8.x86_64
repo: zip-3.0-23.el8.x86_64
repo:
repo: Complete!
==> repo: Running provisioner: shell...
repo: Running: inline script
repo: WARNING: Running pip install with root privileges is generally not a good idea. Try __main__.py install --user instead.
repo: Collecting pip
repo: Downloading https://files.pythonhosted.org/packages/a4/6d/6463d49a933f547439d6b5b98b46af8742cc03ae83543e4d7688c2420f8b/pip-21.3.1-py3-none-any.whl (1.7MB)
repo: Installing collected packages: pip
repo: Successfully installed pip-21.3.1
repo: Collecting pexpect
repo: Downloading pexpect-4.9.0-py2.py3-none-any.whl (63 kB)
repo: Collecting ptyprocess>=0.5
repo: Downloading ptyprocess-0.7.0-py2.py3-none-any.whl (13 kB)
repo: Installing collected packages: ptyprocess, pexpect
repo: Successfully installed pexpect-4.9.0 ptyprocess-0.7.0
repo: WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
repo: Collecting ansible
repo: Downloading ansible-4.10.0.tar.gz (36.8 MB)
repo: Preparing metadata (setup.py): started
repo: Preparing metadata (setup.py): finished with status 'done'
repo: Collecting ansible-core~=2.11.7
repo: Downloading ansible-core-2.11.12.tar.gz (7.1 MB)
repo: Preparing metadata (setup.py): started
repo: Preparing metadata (setup.py): finished with status 'done'
repo: Collecting jinja2
repo: Downloading Jinja2-3.0.3-py3-none-any.whl (133 kB)
repo: Collecting PyYAML
repo: Downloading PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (677 kB)
repo: Requirement already satisfied: cryptography in /usr/lib64/python3.6/site-packages (from ansible-core~=2.11.7->ansible) (2.3)
repo: Collecting packaging
repo: Downloading packaging-21.3-py3-none-any.whl (40 kB)
repo: Collecting resolvelib<0.6.0,>=0.5.3
repo: Downloading resolvelib-0.5.4-py2.py3-none-any.whl (12 kB)
repo: Requirement already satisfied: idna>=2.1 in /usr/lib/python3.6/site-packages (from cryptography->ansible-core~=2.11.7->ansible) (2.5)
repo: Requirement already satisfied: asn1crypto>=0.21.0 in /usr/lib/python3.6/site-packages (from cryptography->ansible-core~=2.11.7->ansible) (0.24.0)
repo: Requirement already satisfied: six>=1.4.1 in /usr/lib/python3.6/site-packages (from cryptography->ansible-core~=2.11.7->ansible) (1.11.0)
repo: Requirement already satisfied: cffi!=1.11.3,>=1.7 in /usr/lib64/python3.6/site-packages (from cryptography->ansible-core~=2.11.7->ansible) (1.11.5)
repo: Collecting MarkupSafe>=2.0
repo: Downloading MarkupSafe-2.0.1-cp36-cp36m-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (30 kB)
repo: Collecting pyparsing!=3.0.5,>=2.0.2
repo: Downloading pyparsing-3.1.2-py3-none-any.whl (103 kB)
repo: Requirement already satisfied: pycparser in /usr/lib/python3.6/site-packages (from cffi!=1.11.3,>=1.7->cryptography->ansible-core~=2.11.7->ansible) (2.14)
repo: Using legacy 'setup.py install' for ansible, since package 'wheel' is not installed.
repo: Using legacy 'setup.py install' for ansible-core, since package 'wheel' is not installed.
repo: Installing collected packages: pyparsing, MarkupSafe, resolvelib, PyYAML, packaging, jinja2, ansible-core, ansible
repo: Running setup.py install for ansible-core: started
repo: Running setup.py install for ansible-core: finished with status 'done'
repo: Running setup.py install for ansible: started

repo:     Running setup.py install for ansible: still running...
repo:     Running setup.py install for ansible: finished with status 'done'
repo: Successfully installed MarkupSafe-2.0.1 PyYAML-6.0.1 ansible-4.10.0 ansible-core-2.11.12 jinja2-3.0.3 packaging-21.3 pyparsing-3.1.2 resolvelib-0.5.4
repo: WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

==> node1: Importing base box 'rdbreak/rhel8node'...
==> node1: Matching MAC address for NAT networking...
==> node1: Setting the name of the VM: rhce8env_node1_1711273855603_50252
==> node1: Clearing any previously set network interfaces...
==> node1: Preparing network interfaces based on configuration...
node1: Adapter 1: nat
node1: Adapter 2: hostonly
==> node1: Forwarding ports...
node1: 22 (guest) => 2222 (host) (adapter 1)
==> node1: Running 'pre-boot' VM customizations...
==> node1: Booting VM...
==> node1: Waiting for machine to boot. This may take a few minutes...
node1: SSH address: 127.0.0.1:2222
node1: SSH username: vagrant
node1: SSH auth method: private key
==> node1: Machine booted and ready!
[node1] GuestAdditions versions on your host (7.0.12) 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.
Skipping unmount of Virtualbox Guest Additions ISO, because it was not mounted.
==> node1: Checking for guest additions in VM...
node1: The guest additions on this VM do not match the installed version of
node1: VirtualBox! In most cases this is fine, but in rare cases it can
node1: prevent things such as shared folders from working properly. If you see
node1: shared folder errors, please make sure the guest additions within the
node1: virtual machine match the version of VirtualBox you have installed on
node1: your host and reload your VM.
node1:
node1: Guest Additions Version: 5.2.30
node1: VirtualBox Version: 7.0
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

bash -c 'type -p dnf || type -p yum' install -y kernel-devel kernel-devel-uname -r gcc binutils make perl-interpreter bzip2 elfutils-libelf-devel

Stdout from the command:

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.

Stderr from the command:

Error: There are no enabled repos.

arshad@DESKTOP-C7451KF MINGW64 /d/github/ansible/rhce8env (master)
$

Error 28: no space left on device

RHEL8.4
VirtualBox-6.1-6.1.26_145957_el8-1.x86_64.rpm
vagrant version Installed Version: 2.2.18

repo: Downloading ansible-4.4.0.tar.gz (35.4 MB)
repo: ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device

Couldn't open file

This is my first time working with vagrant. I am trying to install on CentOS 8. I downloaded and installed all of the packages. I ran vagrant init to initialize. When I try to start vagrant up, I get

An error occurred downloading the remote file.

Couldn't open /home/david/base

I can't figure out what is going on. Can anyone point me in the right direction? This is all new to me.

vmware Fusion

Hi There,

Is there a easyway to use the vagrant file with VMware Fusion?

ssh issue: Warning: Remote connection disconnect. Retrying...

HI,

I'm using host with centos8 and virtualbox. I upgarde versions in install command.

When doing Vagrant up, I'm getting connection error to the first vm ( repo):

repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

I tried also with user/password and get the same error.

However, repo vm is stared and can be reached from virtualbox directory but it's configuration is not complete ( network pour adapter 2)

Regards

Access to slack link expired

Hi,

I would like to access to the sample exam for ex294 but it seems that the link is expired, could you please send another one?

Best Regards,

Rémi

Rpm repositories issues

Hi,

yesterday I've set up this environment with vagrant to do the practice exam.

First of all, many thanks for preparing and maintaining this. It is very valuable to be able to train with a practice exam.

But I had several issues related to the yum repositories :

  • The repo VM is working fine and exposes the BaseOS and AppStream repositories through HTTP. But they does not seem to contain some necessary packages for the practice exam : at least mod_ssl and php (for task 10), haproxy (for task 11), and PyMySQL (for the mysql_user ansible module for task 9). Or maybe I missed something?
  • The repo VM does not expose the MySQL repo that we have to configure on task 8. http://repo.example.com/rpms gives a 404 error response
  • Maybe it's on purpose but I was surprised that no repo was configured at all. That gives no template to create .repo files in /etc/yum.repos.d
  • I tried to install ansible through the repo VM but it was not available in it. I finally discovered that it was already installed, which is confusing because the first task is to install it. Maybe it would be worth mentioning that more clearly in the practice exam?
  • The man pages of ansible command-lines are missing. These command-lines can be called with --help, which gives the main information, but the man pages give much more detail

vagrant reload repo or sudo reboot on repo vm crashes the repo vm

$ vagrant ssh repo
sudo rebootLast login: Sun Mar 24 03:05:57 2024 from 10.0.2.2
sudo reboot[vagrant@rhel8 ~]$ sudo reboot
Connection to 127.0.0.1 closed by remote host.

I hit journalctl command in crashed machine dracut:/ # terminal and showing below logs for your reference.
image

[SOLVED] repo: xfs_growfs: /dev/rhel_rhel8/root is not a mounted XFS filesystem

Hi there!
I have noticed an issue while doing my first vagrant up with this environment; the deployment of the repo VM fails with the following error.

repo: Running: inline script
repo: Physical volume "/dev/sdb" successfully created.
repo: Volume group "rhel_rhel8" successfully extended
repo: Size of logical volume rhel_rhel8/root changed from <28.93 GiB (7405 extents) to 30.92 GiB (7916 extents).
repo: Logical volume rhel_rhel8/root successfully resized.
repo: xfs_growfs: /dev/rhel_rhel8/root is not a mounted XFS filesystem

UPDATE: to fix this I have modified the xfs_growfs command in the vagrantfile as follows:

repo.vm.provision :shell, :inline => "pvs | grep '/dev/sdb' && echo 'The disk was already expanded!' || (pvcreate /dev/sdb; vgextend rhel_rhel8 /dev/sdb; lvextend -l +100%FREE /dev/rhel_rhel8/root; xfs_growfs /)"

Hope that can be useful for someone :)

Wrong clone information for rhce8

Install the Virtual Box Extension Pack

Once the above software is installed. Do the following if you're running the environment on Mac:

Create a separate ~/bin directory and cd to it. (The directory doesn't have to be ~/bin, it can be anything you want.)
Clone the environment repo to it with git clone https://github.com/rdbreak/rhcsa8env.git
Change to the rhcsa8env directory that is now in your ~/bin directory.
Run vagrant up to deploy the environment (If the environment has a designated repo VM it will take the longest to deploy the first time only, this is because the repo system has all the packages available to the base release but will be quicker on subsequent deployments.)

Need to update the rhcsa8env with rhce8env ****

Issue in environment setup

I am running a windows environment with Virtual box and I have followed all the steps for setting up the environment. I am getting the following error message when I am running the command "vagrant up"

PS D:\HashiCorp\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: Box 'rdbreak/rhel8node' could not be found. Attempting to find and install...
server2: Box Provider: virtualbox
server2: Box Version: >= 0
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.

how to solve this error pls

README rework suggestion

Hello,

I added an index and reorganized the readme to be more streamlined. Im not sure how to contribute via a pull request so heres the markdown, hope this helps (Keep up the great work here):



RHCE 8 Automated Practice Deployment

Powered by Ansible and Vagrant

Getting Started

Setting up the Environment

(Recommended) Install Github Desktop to make pulling down changes easier

NOTE this requires a free Github account

  1. Navigate to https://desktop.github.com/ and download Github Desktop.
  2. Create or sign in to your account.
  3. Click "Clone a repository from the Internet" and enter "rdbreak/rhce8env" and choose a location then "Clone".
  4. You are also able to easily pull changes when they're made available.

Downloading the Environment Prep

git clone https://github.com/rdbreak/rhce8env.git && cd rhcsa8env

CentOS/RHEL7/Manjaro/Arch (Continue below for RHEL 8 specific script and Virtualbox Extension Pack)

systemctl stop packagekit; yum install -y epel-release && yum install -y git binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms libvirt libvirt-devel ruby-devel libxslt-devel libxml2-devel libguestfs-tools-c ; mkdir ~/Vagrant ; cd ~/Vagrant ; curl -o  vagrant_2.2.6_x86_64.rpm https://releases.hashicorp.com/vagrant/2.2.6/vagrant_2.2.6_x86_64.rpm && yum install -y vagrant_2.2.6_x86_64.rpm && vagrant plugin install vagrant-guest_ansible ; vagrant plugin install vagrant-guest-ansible ; wget -O /etc/yum.repos.d/virtualbox.repo wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo ; yum install -y VirtualBox-6.0 && systemctl start packagekit

*_NOTE* - If it's been awhile since you've run yum update, do that first. Reboot if the kernel was updated. There may be some dependencies errors but don't be alarmed as this won't stop the environment from working._

*_NOTE2* - If you receive an error for an ansible guest vagrant plugin, DO NOT worry, as there are two different plugins related to Ansible and only one needs to be installed._

If you're using RHEL 8, use the script below:
systemctl stop packagekit; dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ; dnf install -y git binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms libvirt libvirt-devel ruby-devel libxslt-devel libxml2-devel libguestfs-tools-c ; mkdir ~/Vagrant ; cd ~/Vagrant ; curl -o  vagrant_2.2.19_x86_64.rpm https://releases.hashicorp.com/vagrant/2.2.19/vagrant_2.2.19_x86_64.rpm && dnf install -y vagrant_2.2.19_x86_64.rpm && vagrant plugin install vagrant-guest_ansible ; wget -O /etc/yum.repos.d/virtualbox.repo wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo ; dnf install -y VirtualBox-6.1 && /usr/lib/virtualbox/vboxdrv.sh setup ; usermod -a -G vboxusers root ; systemctl start packagekit

Fedora

  • If using Fedora, run dnf update -y to update your system, then run the script below as root to install everything at once:
dnf -y install wget git binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms libvirt libvirt-devel ruby-devel libxslt-devel libxml2-devel ; wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo ; mv virtualbox.repo /etc/yum.repos.d/virtualbox.repo ; dnf install -y VirtualBox-6.0 ; usermod -a -G vboxusers ${USER} ; /usr/lib/virtualbox/vboxdrv.sh setup ; dnf -y install vagrant ; dnf remove -y rubygem-fog-core ; vagrant plugin install vagrant-guest_ansible

Windows

macOS

Gatekeeper will block virtualbox from installing. All you have to do is go into Security & Privacy of System Preferences and click Allow under the General tab and rerun installation.

Install all at once with the command below:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" && xcode-select --install &&brew install ansible ; brew install python ; brew cask install vagrant ; brew cask install VirtualBox ; brew cask install virtualbox-extension-pack ; vagrant plugin install vagrant-guest_ansible
Alternatively, you can install everything individually below.

Debian

sudo snap install ruby ; sudo apt install ruby-bundler git -y; wget -c https://releases.hashicorp.com/vagrant/2.2.6/vagrant_2.2.6_x86_64.deb ; sudo dpkg -i vagrant_2.2.6_x86_64.deb ; wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add - ; wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add - ; sudo add-apt-repository "deb http://download.virtualbox.org/virtualbox/debian bionic contrib"; sudo apt update; sudo apt install -y virtualbox-6.0 ; vagrant plugin install vagrant-guest_ansible
Also, install the Virtualbox extension pack below
  • Virtual Box Extension Pack
    Also, don't be spooked by any scary red font during the setup process. There are known issues that won't have a negative affect on the environment.

Now the deployment should be up and running!

Starting-Accessing the Environment

Access example (Needs sudo) - vagrant ssh control or ssh [email protected]

Notable Vagrant Commands to control the environment:

  • ansible-playbook playbooks/reset.yml - Used for resetting the environment after attempting the practice exam in the Red Hat Certs Slack workspace practice exam channel.
  • vagrant up - Boots and provisions the environment
  • vagrant destroy -f - Shuts down and destroys the environment
  • vagrant halt - Only shuts down the environment VMs (can be booted up with vagrant up)
  • vagrant suspend - Puts the VMs in a suspended state
  • vagrant resume - Takes VMs out of a suspended state

Included systems hosts:

  • repo.ansi.example.com
  • control.ansi.example.com
  • node1.ansi.example.com
  • node2.ansi.example.com
  • node3.ansi.example.com
  • node4.ansi.example.com

System Details:

control

  • 192.168.55.200
  • Gateway - 192.168.55.1
  • DNS - 8.8.8.8

node1

  • 192.168.55.201
  • Gateway - 192.168.55.1
  • DNS - 8.8.8.8

node2

  • 192.168.55.202
  • Gateway - 192.168.55.1
  • DNS - 8.8.8.8

node3

  • 192.168.55.203
  • Gateway - 192.168.55.1
  • DNS - 8.8.8.8

node4

  • 192.168.55.204
  • Gateway - 192.168.55.1
  • DNS - 8.8.8.8

There is a Repo/AppStream available to use from http://repo.ansi.example.com/BaseOS and http://repo.ansi.example.com/AppStream

Remember to add the IP addresses to your local host file if you want to connect to the guest systems with the hostname.
Username - user or root
Password - password

Other Useful Information

You can also use the VirtualBox console to interact with the VMs or through a terminal. If you need to reset the root password, you would need to use the console. I'm constantly making upgrades to the environments, so every once and awhile run git pull in the repo directory to pull down changes. If you're using Windows, it's recommended to use Github Desktop so you can easily pull changes that are made to the environment. The first time you run the vagrant up command, it will download the OS images for later use. In other words, it will take longest the first time around but will be faster when it is deployed again. You can run vagrant destroy -f to destroy your environment at anytime. This will erase everything. This environment is meant to be reuseable, If you run the vagrant up command after destroying the environment, the OS image will already be downloaded and environment will deploy faster. Deployment should take around 15 minutes depending on your computer. You shouldn't need to access the IPA server during your practice exams. Everything should be provided that you would normally need during an actual exam. Hope this helps in your studies!

Known Issues

Running the 'vagrant up' environment build will fail If HyperV is installed on the Windows VirtualBox host.
Error is usually "VT-x is not available. (VERR_VMX_NO_VMX)" or similar, when the script attempts to boot the first VM.

Resolution seems to be either remove HyperV, or preventing its hypervisor from starting with the command:
bcdedit /set hypervisorlaunchtype off, followed by a reboot.


Submitting a Bug Report

If you're having problems with the environment, please submit an issue by going to the ISSUES tab at the top. If you have more questions, looking for practice exams to use against this environment, or just looking for a fantastic Red Hat community to join to get your questions answered, check out the Red Hat Certs Slack Workspace. You can find the invite link at the top of this page next to the description.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.