rdbreak / rhcsa7env Goto Github PK

Having issues installing environment on CentOS

ASK [Setting Hostname] ********************************************************
fatal: [repo.example.com]: UNREACHABLE! => changed=false
msg: |-
Data could not be sent to remote host "192.168.55.4". Make sure this host can be reached over ssh: ssh: connect to host 192.168.55.4 port 22: No route to host
unreachable: true

As shown in https://app.slack.com/docs/TGTE0EB5Z/FLTSDD9HB?origin_team=TGTE0EB5Z&origin_channel=CHDDTG4V6 there is an objective to have dave and lisa automatically mount home directories from ipa server ( and also be authenticated with it ).
I managed to get partially done, by creating the shares on ipa server and use them ( also in nfs3 at the moment ) but being that in RHCSA7 there is an objective on this it would be better to have them already prepared on the server so it' s possible to accomplish point 7 of the indicated doc.

system: Running ansible-playbook...

ERROR! 'reboot' is not a valid attribute for a Play

The error appears to have been in '/Users/stuartmcmullen/bin/rhcsaenv/playbooks/system.yml': line 74, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

service: name=firewalld state=started

• name: Rebooting machine
  ^ here

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

System1.example.com fails on reboot after expanding the / LVM and filesystem.

After adding partition 2 of type LVM to /dev/sdb (partition 1 previously added as type swap), and extending volume group 'centos' by adding /dev/sdb2 to the volume group, expand the root filesystem with 'xfs_growfs -d /'. Upon rebooting, system fails to boot with error:

"Starting File System Check on /dev/disk/by-uuid/db65...6226f63e1fcd...
systemd-fsck[257]: fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/disk/by-uuid/db651e5f-a2c2-4236-9570-6226f63e1fcd
[ OK ] Started File System Check on /dev/disk/by-uuid/db651...0-6226f63e1fcd.
[ 125.496511] Buffer I/O error on device dm-2, logical block 4971504
[ 125.497958] Buffer I/O error on device dm-2, logical block 4971504"

The logical block changes with several iterations of the Buffer I/O error message before dracut-initqueue throws a warning about not being able to boot and the disk device not existing and dropping into emergency mode.

Steps to reproduce:
vagrant destroy -f
vagrant up --provider virtualbox
Reset root password
add partition /dev/sdb1 1107MB type swap
add partition /dev/sdb2 1G type LVM
pvcreate /dev/sdb2
vgextend centos /dev/sdb2
lvextend -L +500M /dev/centos/root
xfs_growfs -d /
reboot

Gave up on running in RHEL8 (no epel), reverted to CentOS7.
Downloaded vagrant & VirtualBox.

yum localinstall -y vagrant_2.2.5_x86_64.rpm # works fine

vagrant plugin install vagrant-guest-ansible
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)'

sudo yum localinstall -y VirtualBox-6.0-6.0.10_132072_el7-1.x86_64.rpm
((It complained that my system was not set up to build kernel modules, and I should install kernel-devel kerneld-devel-3.10.0.957.12.2.el7.x86_64. I installed kernel-devel and it actually installed 27.2 instead of 12.2. 12.2 does not seem to be available. But it still said I needed 12.2. Finally I rebooted and tried running /bin/vboxconfig again, and that worked. Guess it had to do some cleanup / config after I installed kernel-devel?))

vagrant up --provider virtualbox
Many happy green messages, until:
==> ipa: Running provisioner: shell...
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of vagrant status to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.

vagrant status
_Current machine states:

ipa aborted (virtualbox)
repo not created (virtualbox)
system1 not created (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run vagrant status NAME._

More or less by accident, I did a "vagrant up" and it took off again. It's been running for over an hour now, slowly printing green "Package xxx will be installed" messages...

The Linux VM (in VMware Player) is churning like mad, but I think it may be hung now. I tried to pause the VM to see if restarting it would dislodge the stuck process, but I can't pause it. It just keeps running.

EDIT: No, it kept running for at least 3 hours. Then I checked it about 4 hours after doing the second "vagrant up," and the VM is no longer sluggish/unresponsive. The vagrant command is no longer consuming CPU -- but it never returned to a shell prompt either.

So it churned for about 3 hours, then just... stopped churning. But it didn't exit the command.

EDIT 2: The next morning, 14 hours later, it's still just sitting there. ps -ef says vagrant is still running, but it hasn't done anything for the last 12-14 hours.

Need this additional package bash-completion

rsync failing on CentOS 7