#12663 netapp storage for Forgejo stg/prod
Closed: Fixed by dkirwan. Opened by dkirwan.

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Please check https://www.fedorastatus.org for known outages
before filing a ticket about an outage.

Describe what you would like us to do:


Hi, I need access to about 30gb netapp backed storage for Forgejo staging on the staging openshift and about 100gb for prod forgejo on the prod openshift clusters.

Can you create the PV? Otherwise I can do it once I have the paths etc.

When do you need this to be done by? (YYYY/MM/DD)


When ever possible


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

Metadata Update from @kevin:
- Issue assigned to kevin

I've created:

fedora_forgejo_prod_backups

and

fedora_forgejo_stage_backups

They should be mountable by the proc/stg openshift workers.
I have a ticket in to get them snapmirrored.

The pv still needs to be created, but then they should be good to go.

Let me know if you want me to make the pv...

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Hey Kevin, darknao was troubleshooting this earlier and it looks like once we got past the original error related to not putting the fully qualified domain name, we now get the following error.

Looks like the NFS export is not accessible:

Output: mount.nfs: mounting ntap-rdu3-c02-fedora01-nfs01a.rdu3.fedoraproject.org:/fedora_forgejo_prod_backups failed, reason given by server: No such file or directory
showmount -e ntap-rdu3-c02-fedora01-nfs01a.rdu3.fedoraproject.org
Export list for ntap-rdu3-c02-fedora01-nfs01a.rdu3.fedoraproject.org:

Metadata Update from @dkirwan:
- Issue status updated to: Open (was: Closed)

darknao checked the staging export that too seems not to be working on ntap-rdu3-c02-fedora01-nfs01a.

Please try again now...

Resolved again thanks @kevin @darknao !

Metadata Update from @dkirwan:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata