Osmos

[jreadey]

Re-raising Cancelled exceptions based on this guidance:
https://docs.python.org/3.8/library/asyncio-exceptions.html#asyncio.CancelledError

---

Important

Re-raise CancelledError exceptions and improve logging and node management in HSDS.

• Exception Handling:
  • Re-raise CancelledError instead of converting to HTTPInternalServerError in azureBlobClient.py and fileClient.py.
• Logging:
  • Change log level from warn to info for certain messages in azureBlobClient.py and fileClient.py.
  • Minor log message concatenation improvements in datanode_lib.py.
• Cluster Management:
  • Add active_sn_ids and active_dn_ids management in headnode.py for better node tracking.
  • Modify isClusterReady() and register() in headnode.py to use active node lists.
• Miscellaneous:
  • Fix typo in headnode.py.
  • Add getNodeUrls() function in headnode.py for URL management.

^{This description was created by for 5803e48. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Typo in the error message: "pending_s3_write timestamp for got updated unexpectedly for {obj_id}" seems to have an extra or misplaced 'for'. Consider revising it, e.g., "pending_s3_write timestamp got updated unexpectedly for {obj_id}".

Suggested change

	msg = f"pending_s3_write timestamp for got updated unexpectedly for {obj_id}"
	msg = f"pending_s3_write timestamp got updated unexpectedly for {obj_id}"