clear VMs for demo #273
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#226 OKR: demo}
fediversity/fediversity
#286 allow accessing test vms from fedi201}
fediversity/fediversity
Reference: fediversity/fediversity#273
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As Fediversity,
I want to be able to reset our VMs (test01~04) to a 'clean' state,
so that our demo may show what our application can do.
kiara referenced this issue2025-04-01 14:00:36 +02:00
notably test03's ssh access seems botched
One rather brutal way of achieving this is:
I suppose it wouldn't be so hard to have a script simply re-install over an existing VM, without having to create it.
@Niols weird, regardless of vm picked, the remove script gives me this error.
to be fair, even in the web interface i don't see options to ditch a vm - is that normal @kevin or might my proxmox user lack certain permissions?
I get:
Do you get the same when creating VMs?
@Niols nope 😶 (expand my
<summary>above for log).thanks tho!
trying provisioning for that one now, which also seems to fail for me:
with the demo having passed i'll close in favor of #116