I, unfortunately, happened to get the copr-fe-dev-db volume to a state when it shows as
copr-fe-dev-db
Attached to None on /dev/vdc
I was trying to upgrade copr-fe-dev instance from F28 to F30 and instead of terminating the instance I renamed it and shut it down. Then provisioned a new one and when the volume didn't mount into the new instance, I deleted the old one in order to fix the issue. Unfortunately, I made it much worse and now I really don't know how to fix it.
copr-fe-dev
ok,, I poked the database to get this back to available state.
Can you try and attach it now?
Metadata Update from @kevin: - Issue assigned to kevin - Issue priority set to: Waiting on Reporter (was: Needs Review)
Unfortunately, it still doesn't work. Well, it is not attached to None anymore, but I still get
None
TASK [copr/frontend-cloud : mount up disk of copr fe] **************************************************************************************************************************************************************************************** Monday 08 July 2019 19:06:39 +0000 (0:00:00.271) 0:37:13.372 *********** fatal: [copr-fe-dev.cloud.fedoraproject.org]: FAILED! => {"changed": false, "msg": "Error mounting /srv/copr-fe: mount: /srv/copr-fe: can't find LABEL=copr-fe.\n"}
from the playbook
Are you able to login to the system at all? It might need some work from the console and fdisk to see if the drive has partitions or labels still
Metadata Update from @smooge: - Issue priority set to: Needs Review (was: Waiting on Reporter)
@smooge, yep, I am able to log in via SSH. What should I do?
Metadata Update from @smooge: - Issue assigned to smooge (was: kevin)
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: cloud
I've done some magic based on suggestions from @msuchy and got it working by the following procedure. I have ...
copr-fe-dev-db-snapshot
copr-fe-dev-db-2
/dev/vdb
/dev/vdc
Now I have the volume available and mounted, the original data is there and the database is working.
Do I need to follow-up this with some other steps or I should just update the volume descriptions and leave it be?
Given how hopelessly fragile it is, I would say update the descriptions and call it a day. :)
I agree with kevin. Thanks to msuchy on that.
Drives are named by the order they are seen. For the old system to have a /dev/vdc there needed to be a /dev/vdb at one point so it probably had it for a similar mount/move in the past when it was rebuilt.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.