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

Update Ruby 3.1 to 3.1.4 #1850

Merged
merged 1 commit into from
Jun 21, 2023
Merged

Update Ruby 3.1 to 3.1.4 #1850

merged 1 commit into from
Jun 21, 2023

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Jun 21, 2023

No description provided.

@ehelms ehelms merged commit e98bb94 into theforeman:master Jun 21, 2023
2 checks passed
@ekohl
Copy link
Member

ekohl commented Jul 20, 2023

While checking #1856 I see things appear to be failing on some nodes:

change from 'absent' to 'present' failed: Execution of '/usr/local/rvm/bin/rvm install ruby-3.1.4 ' returned 2: ruby-3.1.4 - #removing src/ruby-3.1.4..
Searching for binary rubies, this might take some time.
No binary rubies available for: centos/7/x86_64/ruby-3.1.4.
Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.
Checking requirements for centos.
Requirements installation successful.
Installing Ruby from source to: /usr/local/rvm/rubies/ruby-3.1.4, this may take a while depending on your cpu(s)...
ruby-3.1.4 - #downloading ruby-3.1.4, this may take a while depending on your connection...
ruby-3.1.4 - #extracting ruby-3.1.4 to /usr/local/rvm/src/ruby-3.1.4.....
ruby-3.1.4 - #configuring..............................................................
ruby-3.1.4 - #post-configuration..
ruby-3.1.4 - #compiling.......
Error running '__rvm_make -j4',
please read /usr/local/rvm/log/1689863511_ruby-3.1.4/make.log

There has been an error while running make. Halting the installation.

This is https://blog.cloud-mes.com/2022/11/25/fix-vm-core-dot-h-error-ruby-current-ec-undeclared-when-install-ruby-3-dot-1-3-or-3-dot-0-5/

So we'll need to update to a newer GCC. I'd vote for updating our nodes to EL8, but in the short term change it back to 3.0.4 and 3.1.3.

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

Successfully merging this pull request may close these issues.

2 participants