# The form data below was edited by tom_tyler
# Perforce Workshop Jobs
#
# Job: The job name. 'new' generates a sequenced job number.
#
# Status: Job status; required field. There is no enforced or
# promoted workflow for transition of jobs from one
# status to another, just a set of job status values
# for users to apply as they see fit. Possible values:
#
# open - Issue is available to be worked on.
#
# inprogress - Active development is in progress.
#
# blocked - Issue cannot be implemented for some reason.
#
# fixed - Fixed, optional status to use before closed.
#
# closed - Issue has been dealt with definitively.
#
# punted - Decision made not to address the issue,
# possibly not ever.
#
# suspended - Decision made not to address the issue
# in the immediate future, but noting that it may
# have some merit and may be revisited later.
#
# duplicate - Duplicate of another issue that.
#
# obsolete - The need behind the request has become
# overcome by events.
#
# Project: The project this job is for. Required.
#
# Severity: [A/B/C] (A is highest) Required.
#
# ReportedBy The user who created the job. Can be changed.
#
# ReportedDate: The date the job was created. Automatic.
#
# ModifiedBy: The user who last modified this job. Automatic.
#
# ModifiedDate: The date this job was last modified. Automatic.
#
# OwnedBy: The owner, responsible for doing the job. Optional.
#
# Description: Description of the job. Required.
#
# DevNotes: Developer's comments. Optional. Can be used to
# explain a status, e.g. for blocked, punted,
# obsolete or duplicate jobs.
#
# Component: Projects may use this optional field to indicate
# which component of the project a givenjob is associated
# with.
#
# For the SDP, the list of components is defined in:
# //guest/perforce_software/sdp/tools/components.txt
#
# Type: Type of job [Bug/Feature]. Required.
Job: SDP-293
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: adam_morriss
ReportedDate: 2018/01/26 05:12:38
ModifiedBy: tom_tyler
ModifiedDate: 2018/01/26 05:12:38
OwnedBy: tom_tyler
Description:
recover_edge.sh fails due to missing EdgeCheckpointsDir.
The "recover-edge" script doesn't create the EdgeCheckpointsDir; this causes the command checkpoint-dump
command to fail. A workaround is to create this directory.
Per Adam: I don't think that the recover-edge script should be creating the directory, instead having this
part of the standard mkdirs setup script and created at the very beginning. If the directory doesn't exist
when it's needed, then there's a different problem to be verified - have the symlinks been moved, mount
points failed, permissions changed, and so on. Attempting to create it may also fail or, potentially worse,
somehow overwrite or partially create what's required.
Whatever the correct situation, this directory should be created by the SDP ahead of the point when it's used.
Component: core-unix
Type: Bug