[VCL-573] Reservations which alter default imagemeta values may affect other reservations

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 2.3
• Component/s: vcld (backend)
• Assignee: Andrew Kurth
• Reporter: Andrew Kurth
• Created: 04/Apr/12 14:26
• Updated: 09/May/12 16:12
• Resolved: 09/May/12 16:12

Description

There is a bug involving the hash reference containing the default imagemeta values. utils.pm::get_default_imagemeta_info will retrieve the default values from the database and then save a cached copy in $ENV

{imagemeta_info} {default}

. This cached hash reference is returned for subsequent calls to get_default_imagemeta_info. This data is retrieved before vcld forks a process for each reservation. As a result, multiple reservation processes share the same hash reference. If one process changes anything in this hash, it affects other processes.

This is occurring with the checkuser value. This value is being changed to 0 for server requests. Once changed by one reservation, all subsequent reservations which use the default imagemeta data have the value set to 0.

The code must be updated so that reservations can't affect each other.