Bug 1834157 - Reporting failure "NFS access cannot be validated on the destination cluste"r while controller deployed on source cluster
Summary: Reporting failure "NFS access cannot be validated on the destination cluste"r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Scott Seago
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-11 08:29 UTC by Xin jiang
Modified: 2020-05-28 11:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 11:10:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2326 0 None None None 2020-05-28 11:11:15 UTC

Description Xin jiang 2020-05-11 08:29:25 UTC
Description of problem:
The clusters is  4.2->4.4 on AWS, the controller is deployed on source cluster. While creating migplan, the UI always report error "NFS access cannot be validated on the destination cluster". If controller deployed on the target cluster(4.2->4.4), there is not this failure.

Version-Release number of selected component (if applicable):
CAM 1.2

How reproducible:
always

Steps to Reproduce:
1. Create a project on source cluster
$ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/projects/node-selector.json 
2. Create a migplan on CAM console on CAM console


Actual results:
 it reports failure "NFS access cannot be validated on the destination cluster." at step "Persistent volumes"

Expected results:
it shouldn't report any failures

Additional info:
4.2 Source cluster:
$ oc get pods
NAME                                                           READY   STATUS      RESTARTS   AGE
migration-controller-5875775b49-ct9c5                          2/2     Running     0          4h20m
migration-operator-cdf59f769-fv55q                             2/2     Running     0          4h21m
migration-ui-5f957f775d-fllb4                                  1/1     Running     0          4h20m
registry-99713ee5-934d-11ea-8fea-02bf582a1110-mqfql-1-deploy   0/1     Completed   0          5m57s
registry-99713ee5-934d-11ea-8fea-02bf582a1110-mqfql-1-wdl7c    1/1     Running     0          5m49s
restic-d4kzw                                                   1/1     Running     0          4h20m
restic-ltcsx                                                   1/1     Running     0          4h20m
restic-nd9c6                                                   1/1     Running     0          4h20m
velero-74db9b99cb-jrnrt                                        1/1     Running     0          4h20m


$ oc rsh velero-74db9b99cb-jrnrt
sh-4.4$
$ ls
bin  boot  credentials	credentials-azure  credentials-gcp  dev  etc  home  lib  lib64	lost+found  media  mnt	opt  plugins  proc  root  run  sbin  scratch  srv  sys	tmp  usr  var  velero


$ oc get migplan test -o yaml
apiVersion: migration.openshift.io/v1alpha1
kind: MigPlan
metadata:
  annotations:
    openshift.io/touch: 95d160d5-934e-11ea-a827-0a580a810209
  creationTimestamp: "2020-05-11T06:06:48Z"
  generation: 2
  name: test
  namespace: openshift-migration
  resourceVersion: "114471"
  selfLink: /apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/test
  uid: 99713ee5-934d-11ea-8fea-02bf582a1110
spec:
  destMigClusterRef:
    name: target-cluster
    namespace: openshift-migration
  migStorageRef:
    name: cambucketxj
    namespace: openshift-migration
  namespaces:
  - jhou
  srcMigClusterRef:
    name: host
    namespace: openshift-migration
status:
  conditions:
  - category: Required
    lastTransitionTime: "2020-05-11T06:06:53Z"
    message: The `persistentVolumes` list has been updated with discovered PVs.
    reason: Done
    status: "True"
    type: PvsDiscovered
  - category: Error
    lastTransitionTime: "2020-05-11T06:06:54Z"
    message: NFS access cannot be validated on the destination cluster.
    reason: NotFound
    status: "True"
    type: NfsAccessCannotBeValidated
  - category: Required
    lastTransitionTime: "2020-05-11T06:06:55Z"
    message: The storage resources have been created.
    status: "True"
    type: StorageEnsured
  - category: Required
    lastTransitionTime: "2020-05-11T06:06:56Z"
    message: The migration registry resources have been created.
    status: "True"
    type: RegistriesEnsured
  observedDigest: 6473ada65b2d484fe2a56b46ff8b2452d6140339eba014172c11009242f44946

Comment 5 Xin jiang 2020-05-22 10:02:58 UTC
Verified

Comment 7 errata-xmlrpc 2020-05-28 11:10:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:2326


Note You need to log in before you can comment on or make changes to this bug.