Bug #3978

Upgrading gems should be mentionned in documentation

Added by Edouard Bourguignon almost 6 years ago. Updated almost 6 years ago.

Status:ClosedStart date:09/10/2015
Priority:LowDue date:
Assignee:Carlos Martín% Done:

0%

Category:Documentation
Target version:Release 4.14
Resolution:fixed Pull request:
Affected Versions:Development

Description

Hi,

We are upgrading from 4.12 to 4.14 devel following this documentation http://docs.opennebula.org/4.14/release_notes/release_notes/upgrade_412.html
Everything seems ok when we first upgraded to opennebula-4.13.80-1.x86_64. Then we upgraded to opennebula-4.13.85-1.x86_64 just via yum update. Some services/daemon were broken:

/usr/lib/one/oneflow/lib/models/role.rb:22:in `<top (required)>': treetop gem version must be >= 1.6.3 (RuntimeError)

We had to rerun /usr/share/one/install_gems which is not specified in the documentation.


Related issues

Related to Feature #3979: Notify users they must run install_gems in debian and ubu... Closed 09/11/2015

History

#1 Updated by Carlos Martín almost 6 years ago

  • Status changed from Pending to New
  • Target version set to Release 4.14

It is not mentioned directly in the upgrade guide because it's step 2 of the installation guide1. But I agree that adding a reminder in the upgrade guide will not hurt.

http://docs.opennebula.org/4.14/design_and_installation/building_your_cloud/ignc.html#step-2-ruby-runtime-installation

#2 Updated by Carlos Martín almost 6 years ago

  • Related to Feature #3979: Notify users they must run install_gems in debian and ubuntu packages added

#3 Updated by Ruben S. Montero almost 6 years ago

  • Assignee set to Carlos Martín

#4 Updated by Carlos Martín almost 6 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF