fix: improve CloudSigma error messages and update RamNode README (#947)

CloudSigma UX fixes:
- Use log_error consistently for remediation hints (was log_warn)
- Add "Common issues" block to create_server failure
- Add actionable hints to server timeout error
- Extract API error message instead of dumping raw response
- Fix README: VNC password is random, not hardcoded

RamNode README:
- Update implemented agents list from 9 to all 15

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
A 2026-02-13 07:54:31 -08:00 committed by GitHub
parent 8dbe5d0710
commit 793dee20ae
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 29 additions and 14 deletions

View file

@ -117,7 +117,7 @@ CloudSigma servers typically start in 30-60 seconds. If timeout occurs:
- **Auth**: HTTP Basic Auth (Base64-encoded `email:password`)
- **Drive cloning**: Each server gets a fresh Ubuntu 24.04 clone (not shared)
- **Networking**: DHCP-based IPv4 with virtio NIC model
- **VNC**: Available via CloudSigma portal (password: `spawn123`)
- **VNC**: Available via CloudSigma portal (random password generated per server)
## Resources