As this is happening relatively often lately it would be good to add guide.
Signed-off-by: Michal Konecny mkonecny@redhat.com
@kevin I'm not sure how one becomes the koji admin. Which would be nice to document as well.
For disabling, we could just stop kojid on the builder. That would prevent it from taking new jobs. That could be done by anyone who can login to the builder, no auth needed.
koji admin is added for people who do releng stuff and are acked/+1ed by existing koji admins. ;)
Let me update the guide then
1 new commit added
Add another option of disabling builder
I added a note with the second option to disable it.
The only think I'm not sure about is if running the playbook will also destroy the existing machine or if you need to destroy it first by running destroy_virt_inst.yml playbook.
destroy_virt_inst.yml
yeah, you will need to run destroy_virt to destroy it first. (Or manually destroy it and undefine it).
rebased onto 88dee1f3ea8b5ba14c2f28bea14772349a7a188f
Add guide for destroying the virt instance
I hope it should be OK now.
I was able to go through the whole procedure today and can confirm that the guide works.
rebased onto b19a40cbf16d1fad4004d023fa237965d8852512
Pull-Request has been merged by zlopez
As this is happening relatively often lately it would be good to add guide.
Signed-off-by: Michal Konecny mkonecny@redhat.com