Bug #4322

If the GLOBAL_PREFIX has been defined and then undefined fsck fails

Added by OpenNebula Systems Support Team over 5 years ago. Updated about 5 years ago.

Status:ClosedStart date:02/10/2016
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:Release 5.0
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14

Description

If the GLOBAL_PREFIX has been defined and then removed, the XML generated by the core is the following:

<AR_POOL>
   <AR>
     <ALLOCATED>...</ALLOCATED>
     <AR_ID>...</AR_ID>
     <GLOBAL_PREFIX/>
     <IP>...</IP>
     <MAC>...</MAC>
     <SIZE>...</SIZE>
     <TYPE>...</TYPE>
  </AR>
</AR_POOL>

In the fsck.rb in the line:
https://github.com/OpenNebula/one/blob/release-4.14.2/src/onedb/fsck.rb#L1355

global_prefix would become the empty string, but it's later matched against nil, which leads to failures.

History

#1 Updated by Ruben S. Montero about 5 years ago

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

This issue has been fixed in commit f518b526

Also available in: Atom PDF