Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RHEL 8.7 Install via RPMs not Working #354

Closed
JPGlaser opened this issue Dec 30, 2022 · 8 comments
Closed

RHEL 8.7 Install via RPMs not Working #354

JPGlaser opened this issue Dec 30, 2022 · 8 comments

Comments

@JPGlaser
Copy link

Hey All,

I am working on getting a new GPU cluster up and running on our HPC. One of the last pieces of work I need to do is get TurboVNC installed for our OpenOnDemand instance. While the following normally works (my Warewulf cluster uses this in a Singularity container), it seems to be hitting a brick wall with RHEL 8.7. Any ideas?

Just an FYI: This happens for all versions of turbovnc RPMs.

cd /etc/yum.repos.d/ && wget https://turbovnc.org/pmwiki/uploads/Downloads/TurboVNC.repo && cd ~/
[root@titan ~]# dnf install turbovnc-3.0-20220503.x86_64
Updating Subscription Management repositories.
Last metadata expiration check: 0:08:12 ago on Fri 30 Dec 2022 02:21:58 PM EST.
Dependencies resolved.
=======================================================================================================================================================================================
 Package                                    Architecture                             Version                                          Repository                                  Size
=======================================================================================================================================================================================
Installing:
 turbovnc                                   x86_64                                   3.0-20220503                                     TurboVNC                                    39 M

Transaction Summary
=======================================================================================================================================================================================
Install  1 Package

Total download size: 39 M
Installed size: 66 M
Is this ok [y/N]: y
Downloading Packages:
turbovnc-3.0.x86_64.rpm                                                                                                                                 18 MB/s |  39 MB     00:02    
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                   18 MB/s |  39 MB     00:02     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                               1/1 
  Installing       : turbovnc-3.0-20220503.x86_64                                                                                                                                  1/1 
warning: /etc/turbovncserver.conf created as /etc/turbovncserver.conf.rpmnew

Error unpacking rpm package turbovnc-3.0-20220503.x86_64
  Verifying        : turbovnc-3.0-20220503.x86_64                                                                                                                                  1/1 
Installed products updated.

Failed:
  turbovnc-3.0-20220503.x86_64                                                                                                                                                         

Error: Transaction failed
[root@titan ~]# hostnamectl 
   Static hostname: titan.deku
         Icon name: computer-server
           Chassis: server
        Machine ID: 2a63000c23ee41618736ebf8cbaa8b95
           Boot ID: bd294af0186547a18a061b1268a8347c
  Operating System: Red Hat Enterprise Linux 8.7 (Ootpa)
       CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
            Kernel: Linux 4.18.0-425.3.1.el8.x86_64
      Architecture: x86-64
@dcommander
Copy link
Member

This may be related to what I am experiencing in #354

Is your system configured for FIPS? Otherwise, I don't know if this is related to #353. I have a non-FIPS Rocky Linux 8.7 system and am able to install TurboVNC RPMs just fine. Anyhow, I will spin new RPMs with updated digests next week and let you know when those are ready to test. If the new RPMs don't fix this issue, then we can continue trying to diagnose what's different about your system.

@JPGlaser
Copy link
Author

JPGlaser commented Jan 9, 2023

@dcommander It is not! I had missed that clarifying bit in the registered issue.

I am running stock RHEL with the latest kernel. The system has AMD processors and 2 NVIDIA RTX Titans, though those are just compute and the graphics driver comes from the motherboard.

~ Joe G.

@dcommander
Copy link
Member

It may simply be a security policy in RHEL.

@JPGlaser
Copy link
Author

While I have SELinux installed, I don't have much of the booleans active. Any ideas on what might be the issue here besides a generic security policy? There was no such issue on the head node which is running an earlier subversion of RHEL 8.

~ Joe G.

@dcommander
Copy link
Member

I wish I knew. I will dig into it hopefully later this week and try to find out. I'm hip-deep in a libjpeg-turbo project at the moment.

@dcommander
Copy link
Member

New TurboVNC 3.0.2 RPM packages with FIPS-compliant SHA-256 payload digests have been deployed to SourceForge (and, by extension, the YUM repository.) Try the new packages and see if that fixes this issue. If not, then I have no other ideas.

@dcommander
Copy link
Member

@JPGlaser Please test the new RPM packages and let me know if this issue is still observed. If I don't hear from you soon, the issue will be closed due to lack of response.

@dcommander
Copy link
Member

Closed due to lack of response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants