whitetiger264 commented on issue #7244:
URL: https://github.com/apache/cloudstack/issues/7244#issuecomment-1438580735
@whitetiger264 & @DaanHoogland
So here's an update. I do not know what **magic** is happening. So I have
done the following:
1. Update the DB table and set the Template status from `Migrating` to
`Ready`.
2. Done a "Complete" migration from "broken" NFS to Working NFS.
3. Removed "broken" NFS secondary storage via UI.
4. Destroy SSVM, however, the new SSVM did not boot back up. Got an error
about missing a template.
5. So I added a "broken" secondary NFS back via UI.
6. Destroy SSVM again and now new SSVM deployed.
Now, the IP route in SSVM updates accordingly for **BOTH** NFS storages:
```
root@s-149-VM:~# ip route
default via 197.189.XXX.YYY dev eth2
1.1.1.1 via 192.168.50.1 dev eth1
8.8.8.8 via 192.168.50.1 dev eth1
10.0.0.0/8 via 192.168.50.1 dev eth1
102.165.XXX.XXX via 192.168.50.1 dev eth1
102.165.XXX.YYYY via 192.168.50.1 dev eth1
156.38.XXX.XXX/XX via 192.168.50.1 dev eth1
156.38.XXX.XXX via 192.168.50.1 dev eth1
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.235.208
172.16.0.0/12 via 192.168.50.1 dev eth1
192.168.0.0/16 via 192.168.50.1 dev eth1
192.168.50.0/24 dev eth1 proto kernel scope link src 192.168.50.78
192.168.50.0/24 dev eth3 proto kernel scope link src 192.168.50.91
197.189.XXX.XXX/XX dev eth2 proto kernel scope link src 197.189.XXX.XXX
```
And now, I can successfully reach **BOTH** NFS storages via `192.168.50.1`
gateway:
```
root@s-149-VM:~# traceroute 102.165.XXX.YYY
traceroute to 102.165.XXX.YYY (102.165.XXX.YYY), 30 hops max, 60 byte packets
1 192.168.50.1 (192.168.50.1) 0.340 ms 0.281 ms 0.219 ms
2 * * *
3 * * *
4 HOSTNAME (197.189.XXX.XXX) 0.786 ms 0.769 ms 0.790 ms
5 HOSTNAME (196.60.XXX.XXX) 1.454 ms 1.371 ms 1.352 ms
6 HOSTNAME (102.165.XXX.YYY) 1.395 ms 1.342 ms 1.287 ms
```
```
root@s-149-VM:~# fping -S 192.168.50.78 102.165.XXX.YYY
102.165.XXX.YYY is alive
```
However, the NFS mount is still failing, for **BOTH** secondary NFS now but
this time with a new error:
```
2023-02-21 14:21:37,321 ERROR [storage.resource.NfsSecondaryStorageResource]
(agentRequest-Handler-1:null) GetRootDir for
nfs://102.165.XXX.YYY/data/secondary failed due to
com.cloud.utils.exception.CloudRuntimeException: Unable to mount
102.165.XXX.YYY:/data/secondary at
/mnt/SecStorage/91de6d1c-4c04-359c-82b5-fdcfe4a83da7 due to mount.nfs: access
denied by server while mounting 102.165.XXX.YYY:/data/secondary
```
And here's the exports file for `102.165.XXX.YYY`:
```
[root@nfshost ~]# cat /etc/exports
/data/secondary *(rw,async,no_root_squash,no_subtree_check)
```
I can mount from my personal client machine so I now no idea why I am
getting an `access denied` error now. So if I can solve this, I believe my
secondary NFS storages will be working 100% as expected...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
