I can’t run yum update. When I try, I get this:
--> Processing Dependency: python3-libs(x86-64) = 3.6.8-18.el7 for package: python3-3.6.8-18.el7.x86_64 -
--> Package python3-pycparser.noarch 0:2.14-14.el8 will be installed -
--> Package readline.x86_64 0:6.2-11.el7 will be updated
--> Processing Dependency: libreadline.so.6()(64bit) for package: alt-sqlite-3.26.0-1.1.el7.x86_64
--> Processing Dependency: libreadline.so.6()(64bit) for package: cpanel-sqlite-3.32.3-1.cp1198.x86_64
--> Processing Dependency: libreadline.so.6()(64bit) for package: python-libs-2.7.5-91.el7.cloudlinux.x86_64
--> Processing Dependency: libreadline.so.6()(64bit) for package: alt-php-internal-cli-7.4.22-2.el7.x86_64
--> Processing Dependency: libreadline.so.6()(64bit) for package: jetlftp-4.9.1.1-1.x86_64 -
--> Package redhat-rpm-config.noarch 0:129-1.el8.alma will be installed Error: Invalid version flag: if
CloudLinux release: 8.6
AdminBee
20.7k17 gold badges46 silver badges68 bronze badges
asked Aug 28, 2022 at 18:21
9
I’m trying to install Apache Cassandra on Red Hat 7 via yum as described here https://cassandra.apache.org/_/download.html. The installation process was successful with version 4.0.3.
However, with the latest version 4.0.5 the following error message is returned during the installation process Error: Invalid version flag: or.
The or operator was added to the Apache Cassandra configuration with https://github.com/apache/cassandra/tree/cd0a40d09e5c029e3cac260ecf4cb3dc02deabc7.
From my understanding the or operator was introduced with the RPM version 4.13 but Red Hat 7 ships with 4.11.3.
Is there any other solution than upgrading to a new Red Hat version?
asked Aug 8, 2022 at 12:17
This is still happening on Cassandra 4.1.0. I successfully installed it on Centos 7 after I changed the repo baseUrl to noboolean path (basically, you just need to append /noboolean string to the path and that’s it). Steps to fix the issue:
- Run the
vi /etc/yum.repos.d/cassandra.repocommand - Set
baseurl=https://redhat.cassandra.apache.org/41x/nobooleanand save the file - Run the
sudo yum install cassandra(as stated in the official docs)
Works fine. Cassandra 4.1 is up and running in the cluster. Centos 8+ doesn’t need this change and official instructions work well as they are.
answered Dec 29, 2022 at 17:23
Ivan SivakIvan Sivak
6,9583 gold badges35 silver badges42 bronze badges
Skip to navigation
Skip to main content
Infrastructure and Management
-
Red Hat Enterprise Linux
- Red Hat Virtualization
- Red Hat Identity Management
- Red Hat Directory Server
- Red Hat Certificate System
- Red Hat Satellite
- Red Hat Subscription Management
- Red Hat Update Infrastructure
- Red Hat Insights
- Red Hat Ansible Automation Platform
Cloud Computing
- Red Hat OpenShift
-
Red Hat CloudForms
- Red Hat OpenStack Platform
- Red Hat OpenShift Container Platform
- Red Hat OpenShift Data Science
- Red Hat OpenShift Online
- Red Hat OpenShift Dedicated
- Red Hat Advanced Cluster Security for Kubernetes
- Red Hat Advanced Cluster Management for Kubernetes
- Red Hat Quay
- OpenShift Dev Spaces
-
Red Hat OpenShift Service on AWS
Storage
- Red Hat Gluster Storage
- Red Hat Hyperconverged Infrastructure
- Red Hat Ceph Storage
- Red Hat OpenShift Data Foundation
Runtimes
- Red Hat Runtimes
- Red Hat JBoss Enterprise Application Platform
- Red Hat Data Grid
- Red Hat JBoss Web Server
- Red Hat Single Sign On
-
Red Hat support for Spring Boot
- Red Hat build of Node.js
- Red Hat build of Thorntail
- Red Hat build of Eclipse Vert.x
- Red Hat build of OpenJDK
- Red Hat build of Quarkus
Integration and Automation
- Red Hat Process Automation
- Red Hat Process Automation Manager
- Red Hat Decision Manager
All Products
Issue
# yum update
ID-CD_epel_redhat-7 | 2.6 kB 00:00:00
ID-CD_epel_redhat-8 | 2.4 kB 00:00:00
rhel-7-server-rpms | 2.0 kB 00:00:00
(1/9): ID-CD_epel_redhat-7/group | 392 kB 00:00:00
(2/9): ID-CD_epel_redhat-7/updateinfo | 892 kB 00:00:00
(3/9): ID-CD_epel_redhat-7/primary | 4.9 MB 00:00:00
(4/9): ID-CD_epel_redhat-8/group | 121 kB 00:00:00
(5/9): ID-CD_epel_redhat-8/updateinfo | 455 kB 00:00:00
(6/9): ID-CD_epel_redhat-8/primary | 2.6 MB 00:00:00
(7/9): rhel-7-server-rpms/7Server/x86_64/group | 637 kB 00:00:00
(8/9): rhel-7-server-rpms/7Server/x86_64/updateinfo | 4.1 MB 00:00:00
(9/9): rhel-7-server-rpms/7Server/x86_64/primary | 51 MB 00:00:00
ID-CD_epel_redhat-7 13592/13592
ID-CD_epel_redhat-8 7349/7349
rhel-7-server-rpms 31780/31780
.
Error: Invalid version flag: if
Environment
- Red Hat Enterprise Linux 7.x.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
Current Customers and Partners
Log in for full access
Log In
As Michael mentioned in early comment, your are trying to perform an upgrade with the wrong process.
Firstly we have to be clear about update and upgrade.
Update
Sometimes called a software patch, an update is an addition to the current version of the application, operating system, or software that you are running. A software update addresses any issues or bugs to provide a better experience of working with the technology. In RHEL, an update relates to a minor release, for example, updating from RHEL 8.1 to 8.2.
Upgrade
An upgrade is when you replace the application, operating system, or software that you are currently running with a newer version. Typically, you first back up your data according to instructions from Red Hat. When you upgrade RHEL, you have two options:
In-place upgrade: During an in-place upgrade, you replace the earlier version with the new version without removing the earlier version first. The installed applications and utilities, along with the configurations and preferences, are incorporated into the new version.
Clean install: A clean install removes all traces of the previously installed operating system, system data, configurations, and applications and installs the latest version of the operating system. A clean install is ideal if you do not need any of the previous data or applications on your systems or if you are developing a new project that does not rely on prior builds.
As you are trying to move from version 7 to version 8 you need an upgrade.
In this point I would like to share with you the next video from Red Hat channel in youtube, this video shows you the In-Place Upgrade using Leapp.
Let me know if this resolve your concerns,