rhel-labs / instruqt Goto Github PK

This may not be a problem of the lab, but a problem of Edge Management.

While I try the edge-management lab. Rebooting a edge system didn't happen.
I found following log in /var/log/rhc-worker-playbook/ansible/*/stdout. 

TASK [schedule reboot when rpmostree upgraded] *********************************
fatal: [localhost]: FAILED! => {"msg": "The conditional check '"Staging deployment...done" in rpmostree_upgrade_out.stdout' failed.
The error was: error while evaluating conditional ("Staging deployment...done" in rpmostree_upgrade_out.stdout): 'dict object' has no attribute 'stdout'"}

Thanks,

Seems that the insights-vulnerability lab is now no longer registering to insights at start-up. I suspect the changes to the registration process broke it? I will investigate

The existing labs cover building a container image with buildah and running it with podman. As a system administrator or developer, graphically managing containers with Cockpit might be easier. As a solutions architect, showing the integration increases the value of the Red Hat stack.

Maybe just add a short Cockpit-based section to the existing Podman lab, rather than creating a whole new lab.

convert2rhel lab doesn't work.

Add system-roles lab to this repo.

Please set the time limit to 3420. See #51 for more info.

John Spinks has pointed out a few typos/corrections. Hist comments follow:

Main page as the lab was setting up. Bottom of the page.
Asminidtrators > Administrators

Gathering System information
rhc = Remote Host Configuration
As written it sounds like rhc = cloud connector.
I'm not opposed to it as written as I don't know that people will really know or care about cloud connector or RHC

Accessing the Hybrid Cloud Console

Wondering if you want to add a note in this section that the user may want to make sure they are logged out of Red Hat websites before beginning.
Otherwise the lab opening a window may take them to an environment where they are already logged in as themselves.
(I opened it in an incognito window since that would prevent the issue for me.
Not sure if Instruct is smart enough to open a new incognito window)

NOTE: I do expect the main page navigation will change before Summit. There is a group working on this now, so in the future you might not be navigating to RHEL > Insights.

Vulnerability Reporting

(This section may also be affected by the above referenced navigation changes later this year)

Finading and remediating a CVE

Typo in title - should be finding.

first sentence.... After proving
Should that be After providing?

Verifying CVE Remediation

1st paragraph:
Change: Insights will do this periodically,
to something like: Insights will do this automatically once every 24 hours.

2nd paragraph:
change: Cloud Console
to: Hybrid Cloud Console

Lab

• #112
• #113
• #111
• #109
• #89
• #114
• #97
• #96
• #115
• #116
• #117
• #102
• #91
• #104
• #90
• #118
• #119
• #120
• #121
• #93

RHEL 9.1 Lab image: image: projects/tmm-instruqt-11-26-2021/global/images/rhel-9-1-11-18-2022-4

1. RHEL1 is booting into an older kernel 3.10.0-1160.76.1 instead of the latest installed kernel 3.10.0-1160.83.1 which is causing an error when the pre-upgrade runs "Inhibitor: Newest installed kernel not in use". Rebooting the instance addresses the issue and allows the lab to progress but it should boot the latest to prevent the extra step / time

2. When leapp --version is run, the documentation should reflect the current version which is 0.15.0 instead of 0.14.0 as documented

3. This wording should be updated to reflect what is actually happening, which is not running the upgrade in the background, it is pre-upgraded for the use of the lab:

"Disclaimer: The Leapp process can take upwards of 15 minutes to run. Instead of waiting for that process to complete, a second server has been running the upgrade in the background. Switch to the tab labeled RHEL2 to continue:"

4. The documentation which has you cat /etc/redhat-release on the RHEL2 instance should be updated to say RHEL 8.7 instead of 8.6 since that is the running version

• add centos image
• use static ip
• for virt labs, disable VM autostart
• start VMs in the config script

I think we should make the step name and title (line 5) more meaningful such as "01-gather-system-information".
slug: gather-system-information

So line 5:
title: Gather system information

Couple of findings during the LAB execution

• Screenshot will have to be updated in certain places

Page 1 - where the login screen is, the top bar of console.dot has changed and the favorites is not there anymore
Page 1 - Beta is not beta anymore, it says Preview
Page 2 - With the expected update in couple of days from now, the Repositories configuration is going to be moved out from the settings menu. It should be found in the left hand side bar.
Page 2 - we need to advise participants to think of a random repository, or if they decide to just use what is available. the reason being the validation is based on repository URL, so even if they put the different names they might still get an error that the repo sexists
Page 3 - for some reason, today, if you type Image in the search bar, it will show you something else, you need to type in Builder
Page 3 - I will try to change the screenshot where we see names of customers such as ASML and REWE
Page 3 - The source is labeled RHTE1
Page 3 - The IB Wizard has changed, so update of the screenshot is needed
Page 3 - We shall advise participants to use for example their names, or pet names, or whatsoever to avoid duplication of names. IB does not do such validation, thus they might lose their own image!
Page 4 - The Launch wizard changed too, now it supports AWS Launch templates
Page 5 - You don't need to run the rhc connect anymore. It is enabled by default.
Page 6 - The Pre Upgrade check analysis is executable only in case you install OS from a RHEL 8 Images. So I guess it would be good to suggest to work with RHEL 8 Images rather than RHEL 9.

This lab will need an example application to run within a pod, this application should require two containers which need to communicate with each other. Such as a web site with a back-end database, message queue, something. These should be based on our UBI

Resolving issues with Red Hat Insights Advisor lab

• First challenge. The RHEL Web Console tab not working. Screenshot attached.
  

We've edited the titles and descriptions of all of the labs in Instruqt dashboard so they're grammatically correct and match Red Hat brand/voice. We've noticed a number of them have recently reverted back to the original headers and descriptions.

Since this repo is the source-of-truth for the RHEL labs, please make the the following lab:

https://github.com/rhel-labs/instruqt/blob/master/selinux-containers
Title: Secure containers with SELinux (Udica)
Description: Use Red Hat Enterprise Linux container tools to generate custom SELinux security profiles for a containerized application.

@myee111 if this format works, i can add the 35 others into the next issue. or i'll be happy to try another way if it's easier, like making the changes as a suggestion to the actual file. as a designer i don't know my way around github too well yet.

thanks!

This lab should:

• Describe a podman pod
• Allow the user to create a pod with an application running within it, where the application has a dependency on a second container. Such as a web site with a database back-end.
• Demonstrate how the pod limits public access to services, unless explicitly forwarded, while granting access to in-pod services

Please set the timelimit in challenge 1 to 3420 (57 minutes). Please set the timelimit in subsequent challenges to 1 second. This is something Scott and I agreed to just yesterday to control instruqt costs.

The "Add repositories" button is greyed out and I get this message when I mouse over it.
"You do not have the required permissions to perform this action."

suggestion: tell student to hit "y" explicitly to install the update.

In the future, please make the step name meaningful. This way the summary presented to the student is more meaningful and easier for us to read.

So line 2: slug: install-pcp-tools

line 5: title: Install PCP tools

The ebpf-tracing lab requires a cpu/io/networking intensive workload to run in order to show performance anomalies. On new version of RHEL, the dnf update process doesn't run very long, rendering the lab ineffective.

test

cockpit-composer-41-1.el9.noarch is broken.
bugzilla

As we keep our labs up to date, vulnerabilities in a system cannot be guaranteed to be present. So I'd like to add in a package that we know is vulnerable in rhel 9, that is easily fixed with an RHSA. I'd like to keep the install size as small as possible so it doesn't slow down lab provisioning.

something is broken in dns/hosts file

Feed is related to idm-workshop-1

• IdM leverages sssd within these distributions -->  IdM leverages System Security Services Daemon (SSSD) within these distributions 
• Identity Management is fully supported for servers and clients at no additional cost, as it is included within your Red Hat Enterprise Linux subscription
• Labsetup.sh - There is no output, could an output print the 'Static hostname' from 'hostnamectl'? Which would then be aligned w/ instructions of pinging the hostname
• 'Enrolling Systems' - In this section, you will install the IdM client on a Red Hat Enterprise Linxu 
• Install packages on system - Small and likely irrelevant detail, YUM is used over DNF
•  'Sudo Rule Management' - When changes are required they happen near instantaniously throughout the environment - adding access or revoking access is immediate.

Introduction to Extended Update Support lab is ready to be published on Lab Dot. Please do the needful.

This might just be me but for some reason I can't see stress-ng show up in the performance section of the web console as causing a CPU spike.

Hello! We need to make updates to the titles and descriptions of thirty Red Hat Enterprise Linux labs in Instruqt. The issue is that we've adjusted these on the /interactive-labs page and we want them to align with what someone sees after clicking into one; we want no room for a hiccup in the flow.

See the "RHEL" tab of this spreadsheet for the original titles/descriptions as well as the updates we want to make, along with the lab URLs: (https://docs.google.com/spreadsheets/d/1sRQb5Q-6QF_-S9TEr0s-eq3wlMRmSYQGkigh5GjnWIY/edit#gid=0)

Scott, I'm replacing my last issue with this one. This method worked for updating them on the Ansibile side, so we can see if it works for you all too.