benblasco

Results 46 comments of benblasco

RHEL version in use: ``` [ec2-user@ip-10-0-2-119 ~]$ more /etc/*release :::::::::::::: /etc/os-release :::::::::::::: NAME="Red Hat Enterprise Linux" VERSION="8.5 (Ootpa)" ID="rhel" ID_LIKE="fedora" VERSION_ID="8.5" PLATFORM_ID="platform:el8" PRETTY_NAME="Red Hat Enterprise Linux 8.5 (Ootpa)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"...

It appears though the directory needs to be created by the playbook and have the correct permissions set. ``` [root@bblasco-rhel82 ws-certs.d]# ls -ld /etc/cockpit/ws-certs.d/ drwxr-xr-x. 2 root root 6 Mar...

Looks like the above fix takes us to a problem in the next task: ``` TASK [install real certificate to web console] ***************************************************************************************************************************************************************************************************** fatal: [node-1.rhel.sandbox506.opentlc.com]: FAILED! => {"changed": false, "checksum":...

Root cause found: 2_load.yml hjas checks for rhel_ver to determine whether it's RHEL 7 or RHEL 8, and therefore determine how to install cockpit. e.g. ``` - name: Configure web...

Potential work around/fix in 2_load.yml ``` %s/when: rhel_ver == 'rhel8'/when: rhel_ver is search('RHEL-8') ``` However the above is a somewhat hacky fix that again is a byproduct of the breaking...

Added printout of stdout_lines so you can follow what's going on.

This will also require the installation of the correct version of scap-security-guide on the host as per: [Insights Compliance - Supported Configurations](https://access.redhat.com/articles/6644131) Here's an example of how I have dealt...

I have revisited this particular demo and realise that it is not connected to Insights in any way. We are just running one of the compliance demos available from here:...

I believe I have addressed this issue via PR #51 Do you think we can close this issue as a consequence?

Insights will only pick up changes when you run the insights-client, so we either want the results immediately (as per this issue) or we just wait until the next job...