Bug 1437558 - containers: volumes menu Unexpected error after several add/remove of provider
Summary: containers: volumes menu Unexpected error after several add/remove of provider
Keywords:
Status: CLOSED DUPLICATE of bug 1437549
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: GA
: 5.9.0
Assignee: Federico Simoncelli
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-30 14:13 UTC by Dafna Ron
Modified: 2017-12-05 15:36 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-22 09:11:36 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs and screenshot (4.37 MB, application/x-gzip)
2017-03-30 14:13 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2017-03-30 14:13:58 UTC
Created attachment 1267578 [details]
logs and screenshot

Description of problem:

I added and removed the same provider and at some point the volumes menu gives an Unexpected error 


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

cfme-5.8.0.8-alpha1.1.el7cf.x86_64

How reproducible:

unknown 

1. deploy cfme
2. Add the provider to cfme -> refresh to make sure the objects in the cluster are added
3. remove the provider 
4. repeat step 2 and 3 several times
5. navigate to compute -> containers -> volumes

Actual results:

we get an unexpected error

Expected results:

we should not get an error. 

Additional info:

Unexpected error encountered

Errors in Management Engine can be caused by:

① Accessing Management Engine from multiple tabs or windows of the same browser on a single machine. Close any duplicate browser sessions, then select an option from the menu.
② Pressing the back button during a session. 
      Close any duplicate browser sessions, then select an option from the menu.
③ An internal system error. 
      Please contact your administrator for assistance.


Error text:

PersistentVolume#parent_name delegated to parent.name, but parent is nil: #<PersistentVolume id: 477, parent_id: 5, type: "PersistentVolume", name: "cfme-pv01", empty_dir_medium_type: nil, gce_pd_name: nil, git_repository: nil, git_revision: nil, nfs_server: "10.35.69.178", iscsi_target_portal: nil, iscsi_iqn: nil, iscsi_lun: nil, glusterfs_endpoint_name: nil, claim_name: nil, rbd_ceph_monitors: "", rbd_image: nil, rbd_pool: nil, rbd_rados_user: nil, rbd_keyring: nil, common_path: "/exports/v10", common_fs_type: nil, common_read_only: nil, common_volume_id: nil, common_partition: nil, common_secret: nil, ems_ref: "cc575af3-1539-11e7-b323-001a4a1697aa", ems_created_on: "2017-03-30 11:12:44", resource_version: "5263", capacity: {:storage=>16106127360}, access_modes: "ReadWriteOnce", reclaim_policy: "Retain", status_phase: "Bound", status_message: nil, status_reason: nil, parent_type: "ExtManagementSystem", persistent_volume_claim_id: 30, created_on: "2017-03-30 13:32:26"> [persistent_volume/show_list]

Comment 1 Barak 2017-04-03 09:37:18 UTC
How much time did you wait before re adding the same provider,
It might be that there is information that is pending deletion but was not deleted yet ... and this may create such a phenomena.

Please try to reproduce again this wait several minutes before adding the same provider again (clean env)

Comment 2 Dafna Ron 2017-04-03 09:49:10 UTC
I waited until the provider icon was removed from the provider's menu. 
Before that happens you are unable to add the same provider. 

I agree that there is race condition here which is why I wrote that perhaps you should not remove the provider's from the provider's tab until all other items linked to it are cleaned as well. 

However, please also note that I am still re-directed to the an exception page after a few days so we are not cleaning stale connections for some reason.

Comment 3 Dave Johnson 2017-07-14 03:47:38 UTC
Please assess the importance of this issue and update the priority accordingly.  Somewhere it was missed in the bug triage process.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.


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