View M3 Service Status
Lifecycle of an M3 Service Request
Each M3 service request moves through several stages. These describe where the request is in the approval and provisioning process and what you can do at each stage.
The typical lifecycle is:
Pending approval
After you submit an M3 service request it will appear as Pending approval.
At this stage:
- The request has been successfully submitted.
- eResearch staff are reviewing the information you provided (use case, allocation scheme, members, end date, etc.).
- You cannot yet log in to M3 under this project allocation.
You can:
- Review the request details in the application.
- Cancel the request (if the UI allows).
- Contact eResearch support if you realise important information is missing.
Approved
Once the request has been reviewed and accepted it changes to Approved.
At this stage:
- The request has been approved by the allocation administrators.
- Provisioning of the HPC resources (project group, storage, accounts) is queued or in progress.
- You still might not be able to log in to M3 immediately.
You can:
- Confirm that the request details (end date, members, etc.) are still correct.
- Monitor the application for the final Provisioned status.
- Notify your project members that access will be available soon.
Provisioned
After the technical provisioning completes the status changes to Provisioned.
At this stage:
- The M3 project group and associated resources have been created.
- Members listed in the request should now have access to M3 under this project.
- The End Date is now in effect for the allocation.
You can:
- Manage membership of the service, if you are a project leader or the applicant of the project.
- Update the end date (subject to allocation rules) by submitting an update or extension request, if supported by the application.
Troubleshooting Status Issues
-
If a request is Pending approval for longer than expected, open a support ticket or contact the eResearch.
-
If the status is Provisioned but a member cannot log in to M3, check:
- The user is listed as a member for the service.
- The user is authenticating with the same institution/AAF identity used in the application.
If problems persist, capture screenshots of the service status and any error messages and include them in your support request.