xtophd / rhel8-workshop Goto Github PK

cannot attach kprobe, probe entry may not exist
Traceback (most recent call last):
File "/usr/share/bcc/tools/xfsslower", line 283, in
b.attach_kprobe(event="xfs_file_read_iter", fn_name="trace_rw_entry")
File "/usr/lib/python3.6/site-packages/bcc/init.py", line 596, in attach_kprobe
raise Exception("Failed to attach BPF to kprobe")
Exception: Failed to attach BPF to kprobe

The ansible playbook (appstream-pgsql.yml) for the appstream exercise should get deployed as a template into roots home directory, and NOT as a playbook in the workshop project itself. Workshop exercise components should not nested in the project directory.

Fix documentation accordingly.

Probably affects other units, but Webconsole->Firewall and Webconsole->Services need to be refreshed with shots of RHEL 8.1

create an XML (workshop.xml)

<?xml version="1.0" encoding="utf-8"?>
<service>
 <short>workshop</short>
 <description>Workshop Test Service</description>
 <port protocol="tcp" port="7890" />
 <port protocol="udp" port="7890" />
</service>

import
firewall-cmd --permanent --new-service-from-file=workshop.xml

activate
firewall-cmd --enable=workshop

Hi I am having trouble getting the Ravello console to show in full screen, this is probably a huge oversight in my part - but I can't find the full screen option :/

Documentation needs to be a bit more flexible to unknown environments. The callout of libvirt interfaces confused a few folks and lead them to believe the firewall-cmd exercises needed to be run on workstation.

Do you have Terraform or CloudFormation or other automation you could share if we wanted to setup the RHEL 8 Workshop lab in our own public cloud provider for further testing? I understand the various RHEL images and containers would not be included, but I'm wondering if there are pieces of the lab setup you would be able to share. Thank you.

node 2 reporting an rpm error (or message)

believe error was generated during this command:

ansible rhel8 -o -a "rpm -q postgresql-server"

make mention of the python update from rhel7 to rhel8

It's documented and the cheat scripts work around it, but in the default RHOSP environment we were given for Summit the root disk is UUID based and boom cannot correctly identify the device paths (bug?). Revisit this and the docs once we get a sanely deployed environment (normal block devices and paths, or preferred LVM based filesystems).

I tried running the script but received this error :

xtoph-deploy.yml
[efe@rhel1 RHEL8-Workshop]$ ./rhel8-workshop.sh
ERROR: Are you in the right directory? Can not find ./config/master-config.yml
[efe@rhel1 RHEL8-Workshop]$ sudo ./rhel8-workshop.sh
ERROR: Are you in the right directory? Can not find ./config/master-config.yml
[efd@rhel1 RHEL8-Workshop]$

https://www.redhat.com/sysadmin/tips-using-tmux

since we started leveraging the web-console dashboard on workstation to manage node2, user priviledges are not sufficient to change firewall setting. Either update documents or resolve priviledges.

workshop-cockpit-checkhost.sh is located in
/usr/local/bin

[root@bastion ~]# find / -name checkhost
/root/RHEL8-Workshop/playbooks/templates/workshop-checkhost.j2
/usr/local/bin/workshop-podman-checkhost.sh
/usr/local/bin/workshop-cockpit-checkhost.sh
[root@bastion ~]#

[root@bastion ~]# echo $PATH
/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin

Add /usr/local/bin to the path
[root@bastion ~]# PATH=$PATH:/usr/local/bin;export PATH
[root@bastion ~]# echo $PATH
/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/bin

[root@bastion ~]# workshop-cockpit-checkhost.sh
YES : this is the correct host

https://github.com/xtophd/RHEL8-Workshop/blob/master/playbooks/rhel8-unit-webconsole.yml
Should update the path via handler or set the path in
https://github.com/xtophd/RHEL8-Workshop/blob/master/playbooks/rhel8-prep.yml

target node is not identified and unit does not follow convention

In running through the exercise, at least on Fedora 33, I also needed to install pcp-system-tools in order to use the pmrep command.

here is the RHEL documentation on using Application Streams: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/installing_managing_and_removing_user-space_components/using-appstream_using-appstream

How to maintaining a latest and greatest version of podman on RHEL 8. Point out the appstream for podman in the yum unit and in the podman unit.

Hey guys, could we jettison the Wayland lab and shove one in about managing your population with Ansible System Roles?

Also, when doing buildah, could you start with a UBI image, that's already pretty much done except for app-stuff?