-
Notifications
You must be signed in to change notification settings - Fork 0
Demo #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Demo #6
Conversation
|
/info |
|
📋 Deploy Replay - Default Parameters Current Default Values:
Allowed Servers: Usage Examples: Basic deployment (all defaults): Custom deployment: Available Parameters:
|
|
/deploy-replay |
|
🚀 Deployment Started The deployment is in progress. You should receive a response within 5–10 minutes. ⏳ |
|
❌ Deployment Failed Failed Step: Reason: Tier0Feeder failed Details: Either traceback errors were found in Tier0Feeder logs or verification process encountered an error Configuration Used:
Troubleshooting Steps: Quick Actions:
|
|
/deploy-replay |
|
🚀 Deployment Started The deployment is in progress. You should receive a response within 5–10 minutes. ⏳ |
|
✅ Deployment Successful Configuration:
📊 Monitoring: 📊 Output Data (DAS): Note: Output data will be available in DAS when all jobs are completed Deployment completed successfully! 🎉 |
|
/check-servers |
|
📋 Server Status Report 📊 Summary: 3 empty, 1 busy, 0 errors (of 4 total) Detailed Status: |
|
/check-servers |
|
📋 Server Status Report 📊 Summary: 3 empty, 1 busy, 0 errors (of 4 total) Detailed Status: |
Replay Request
Requestor
Team or person that requests this replay
Describe the configuration
Purpose of the test
A replay test is costly, both in computational and human resources. Please describe the reason why this test is needed.
T0 Operations cmsTalk thread
If necessary, provide a link to the cmsTalk thread announcing the test to the relevant groups.
Tier0 Operations cmsTalk Forum