What this category's data looks like
Vocational school student internship management materials include three categories: internship agreements, internship plans, and internship logs. The sources are the school's internship management department, supervising teachers, and internship units, signed and receipted by all three parties. Agreements contain the unit name, position, start and end dates, and signatures and seals; plans contain the batch, number of people, supervising teacher, and dates; logs contain daily tasks, work hours, and signatures. The three categories of materials have different update rhythms: agreements are signed by batch, plans are adjusted by semester, and logs are filled in daily. When entering the deployment and upgrade function, agreements and plans serve as the version comparison baseline, and logs serve as the business-side mapping of the data row index status. The fields, dates, and signatures of the three must be consistent item by item; a missing signature or receipt is regarded as an incomplete record.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image versions, migration task records, and data row index status. The handover-ready deployment status and operation records are then completed by operations handover and business use. The migration script does 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 description | In the deployment environment, check the image version identifiers of fastgpt-app and fastgpt-pro, and record the filling status of the connection strings MONGODB_URI, PG_URL, REDIS_URL, and DB_MAX_LINK |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired; view the execution record of this task on the administrator version upgrade page | On the version upgrade page, view the execution record of this task, check the trigger time and status, and confirm that the old instance has been stopped |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete; compare the time and status of the two records | Compare the time and status of the two migration task records, and confirm that the latter was triggered after the former completed |
| Data row index status | After migration, it is the new index status system; sample one data row and check the status field | Sample one data row and check the status field to confirm that it has switched from the old marker to the new index status system |
Three common errors
- Symptom: the service can start, but the data row status is still the old marker. Cause: consistent image versions do not mean the business data migration is complete; the migration script was not executed or not completed.
- Symptom: the name, quantity, and date of the same record do not match between the internship agreement and the internship log. Cause: versions are not synchronized, the agreement and log were updated separately, and the handover form was not checked item by item.
- Symptom: the internship plan lacks a signature or receipt, and one record is missing during handover form verification. Cause: the signing status was not synchronized when the materials entered the upgrade function, and the deployment status and operation records are incomplete.
How to verify the setup
This function 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 to see which record is missing.
- On the version upgrade page, view the time and status of the two migration task records, and confirm that the latter was triggered after the former completed.
- Sample one data row to check the index status field, and check the connection filling records for
MONGODB_URI,PG_URL,REDIS_URL, andDB_MAX_LINK.