#7044 Fix NFS mount for odcs backend in staging
Closed: Fixed 5 years ago Opened 5 years ago by ralph.

Triggered by #7042.

odcs-backend-stg needs to mount /fedora_koji read only, but the nfs server is denying it access.

It seems like it may have something to do with an eth1_ip. I tried deleting that when I rebuilt the node on F28, but it didn't seem to work. Can someone more familiar with our network and nfs setup take a look?

Note - I think this is blocking @cverna from experimenting with some new OSBS features in staging.


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

5 years ago

The eth1 interface is the one with NFS access, so that is critical for the functioning of NFS.

So, the issue is:

odcs-backend01 (prod) had a eth1 ip, but the virthost it was on didn't have a bridge to the storage network. So, we disabled that as a quick fix and let it mount over the normal eth0 network.

The staging one never had a storage mount, but it might have mounted prod nfs over the eth0 network before we moved it to the new staging subnet (10.5.128.x).

I have fixed the virthost for the prod one and now it can reach the storage network.
I added eth1 interfaces to both and set them to be used.

Fixed.

:spaghetti:

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

5 years ago

Login to comment on this ticket.

Metadata