6.3 Known Issues

This page documents current known issues, limitations, and workarounds for the Australian Dataspace Testbed Platform.

Bootstrap & Installation Issues

Bootstrap Script Timeout

  • Issue: On smaller instance sizes, bootstrap may exceed 60 minutes
  • Impact: Some services may not fully initialise
  • Workaround: Use recommended instance sizes (m3.medium or larger for Nectar, m7i.xlarge or larger for AWS, Standard_D4s_v3 or larger for Azure)
  • Status: Working as designed; larger instances recommended

Docker Compose Parallel Limit

  • Issue: On Nectar and Azure, Docker containers may fail to start if launched in parallel
  • Impact: Some dataspace components may not initialise correctly
  • Workaround: Bootstrap script includes COMPOSE_PARALLEL_LIMIT=1 for Nectar/Azure deployments
  • Status: Resolved in current bootstrap scripts

Package Repository Timeouts

  • Issue: Occasionally, package repositories (dnf/yum) may timeout during installation
  • Impact: Bootstrap script fails partway through installation
  • Workaround: Terminate and recreate the instance; repository mirrors are usually restored quickly
  • Status: Intermittent; dependent on upstream repository availability

Dataspace Component Issues

Self-Signed Certificate Warnings

  • Issue: Browsers display security warnings for self-signed certificates
  • Impact: Users must manually accept certificate warnings
  • Workaround: Click “Advanced” and proceed to site; this is expected for development environments
  • Status: By design; production deployments will use proper certificates

RDA API Rate Limiting

  • Issue: Research Data Australia API has rate limits
  • Impact: Excessive queries may be temporarily blocked
  • Workaround: Implement reasonable delays between queries; cache results where possible
  • Status: Dashboard already has pagination support to reduce risk

Performance Issues

Large Dataset Transfers

  • Issue: Transferring datasets larger than 1GB may make the dashboard appear to be unresponsive
  • Impact: Data transfer operations fail
  • Workaround: Split large datasets into smaller chunks; increase instance size for better network performance
  • Status: Working as designed. Break up datasets, or simply wait for the completion message

Cloud-specific Issues

Azure Storage Space Full

  • Issue: Azure storage volumes may reach 100% capacity even with less data then the total volume size
  • Impact: Dataspace services may fail due to lack of disk space
  • Workaround: Azure does not allocate the entire volume by default. Expand the required volumes into unallocated space
  • Status: Workaround not documented. Check Azure documentation or raise a support case for assistance

Reporting Issues

If you encounter an issue not listed here, please report it through the Getting Support channels. Include:

  • Detailed description of the issue
  • Steps to reproduce
  • Cloud provider and instance details
  • Error messages or logs
  • Screenshots if applicable