What this category's data looks like
In enterprise compliance and security training scenarios, materials usually fall into three categories: compliance training courseware, security operating procedures, and exam records. Courseware and procedures come from business and security departments and are updated according to the policy revision cycle; exam records are compiled by the training organizer after the assessment is completed, and the fields include name, department, course name, score, date, and signature. During deployment, operations, and application handover, the three categories of materials enter the version upgrade page, and their roles differ: courseware and procedures are checked as business content together with the image version, while exam records are archived as handover evidence together with the migration task records. In terms of field characteristics, the name, quantity, and date of the same material in different versions must remain consistent, and signatures or receipts must not be missing. The update cadence is driven by both policy revisions and deployment upgrades, and after an upgrade the material fields and migration records need to be re-checked.
Configuration and implementation checks
This step is performed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image version, migration task records, and data row index status. "Handover-ready deployment status and operation records" are then completed by operations handover and business use. The upgrade includes version updates for two images, the main service and the commercial edition, as well as two manually triggered migration scripts; the scripts do not block service startup, and the latter depends on the former completing.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images are the same target version; check the version identifiers of the two images against the version notes | View the image version identifiers on the administrator version upgrade page, confirm that the main service and commercial edition are consistent, and check the MONGODB_URI, PG_URL, and REDIS_URL connection configurations |
| Historical chunk training task migration | Trigger only after the old instances have been fully stopped and the old task lease has expired; view the execution record of this task on the administrator version upgrade page | Confirm that all old-version instances in the cluster have been stopped, then view the time and status of this migration task record, and check the connection parameters related to DB_MAX_LINK |
| Knowledge base rebuild status migration | Trigger only after the previous migration is completed; check the time and status of the two records | Check the two migration task records in order, confirm that the latter was executed after the former was completed, and sample one data row to check the index status field |
| Exam records and security operating procedures | The name, department, course name, score, date, and signature of the exam records must correspond to the courseware and procedure versions | Check the name, quantity, and date of the exam records against the courseware and procedures item by item, and check whether signatures or receipts are complete |
Three common errors
- Symptom: the service can start but the data row status still shows the old marker. Cause: consistent image versions do not mean the business data migration is complete; the migration script was not triggered or was not executed in order.
- Symptom: the name, quantity, and date of the same record do not match between the courseware and the exam records. Cause: the versions were not synchronized, and the materials were not checked together with the image update.
- Symptom: the exam records lack signatures or receipts, making them impossible to confirm during handover. Cause: when the materials entered the upgrade page, they were not checked item by item by field, and the handover form had missing items.
How to verify the setup
This feature's acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in order.
Business test: check once item by item according to the handover form, and see which record is missing.
- On the administrator version upgrade page, check the image version identifiers of the main service and commercial edition, and confirm that the two image versions are consistent
- View the execution records of the historical chunk training task migration and the knowledge base rebuild status migration in order, and sample one data row to check the index status field