Bug 1438963

Summary: [RFE] Smartstate on Datastore Failures
Product: Red Hat CloudForms Management Engine Reporter: Saif Ali <saali>
Component: SmartState AnalysisAssignee: James Wong <jwong>
Status: CLOSED DUPLICATE QA Contact: Satyajit Bulage <sbulage>
Severity: medium Docs Contact:
Priority: high    
Version: 5.7.0CC: agrare, gblomqui, gscott, jhardy, jocarter, jwong, mfeifer, myoder, obarenbo, roliveri, saali
Target Milestone: GAKeywords: FutureFeature, Reopened
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: datastore:smartstate
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-07 13:27:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: VMware Target Upstream Version:
Embargoed:

Description Saif Ali 2017-04-04 21:59:00 UTC
Description of problem:
After reconfiguring smartstate to no longer execute from the host but instead execute from vcenter if a datastore is select for smartstate the following error occurs:
error during 'scan': Check that a Host is running and has valid credentials for Datastore 

[1]
[----] E, [2017-03-31T16:19:29.157470 #40378:f9d378] ERROR -- : MIQ(storage_controller-x_button): Datastore "dnvrco03-vmax3-1889-00dd-fbf": Error during 'scan': Check that a Host is running and has valid credentials for Datastores [dnvrco03-vmax3-1889-00dd-fbf] with id: [10000000000002]
[----] E, [2017-03-31T16:19:29.163563 #40378:f9d378] ERROR -- : MIQ(storage_controller-x_button): Datastore "dnvrco03-vmax3-1889-00de-fbf": Error during 'scan': Check that a Host is running and has valid credentials for Datastores [dnvrco03-vmax3-1889-00de-fbf] with id: [10000000000001]
[----] E, [2017-03-31T16:19:29.169492 #40378:f9d378] ERROR -- : MIQ(storage_controller-x_button): Datastore "ncw-stg-template-ds": Error during 'scan': Check that a Host is running and has valid credentials for Datastores [ncw-stg-template-ds] with id: [10000000000003]




Version-Release number of selected component (if applicable):
4.2
VC version  5.5.
fiber channel on a EMC VMAX

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Adam Grare 2017-05-25 17:12:57 UTC
Hey James can you take a look at this?

Comment 5 James Wong 2017-05-30 19:48:33 UTC
Ali,

Can you check with customer if they have entered the credential of the host?
When they go to the summary page of the host to which the datastore is attached, use the pull-down menu 'configure -> Edit this item' to do that.

In my test, no matter which way (using host or using vCenter) user chooses, host credential has to be entered.


regards,
James

Comment 8 James Wong 2017-06-06 14:16:12 UTC
Maybe this is never a feature for Storage SSA.  It doesn't seems to check on the flag scan_via_host. It always tries to authenticate the host(s)

https://github.com/jameswnl/manageiq/blob/c559da011484fc1019bbe400135219b2bdc45439/app/models/storage.rb#L535-L535

Comment 11 Rich Oliveri 2017-06-08 17:56:30 UTC
As far as I know, scan_via_host only applies to VM SSA. Storage SSA for VMware should use the VIM datastore browser, so I can't see why it would have to authenticate to the host.

Comment 17 Adam Grare 2018-01-22 19:10:22 UTC
This was completed by https://bugzilla.redhat.com/show_bug.cgi?id=1529725

*** This bug has been marked as a duplicate of bug 1529725 ***

Comment 18 Greg Scott 2018-02-06 21:32:39 UTC
I'm putting this BZ back into ASSIGNED state again.  I don't think it's a duplicate at all of 1529725. This bug documents an authentication error. The other bug documents a "not found" error.  The other bug only shows up with the host name for the datastore is different than the vCenter name for the datastore.  But in this case, both the host and vCenter have the same name.

If I messed up and they're different sides of the same problem, apologies in advance.  I'll put a needsinfo to make sure I'm not in left field.

thanks

- Greg Scott

Comment 19 Adam Grare 2018-02-06 21:38:44 UTC
Hey Greg, I'll give you the reasons why I closed this and hopefully you agree.

The bug was opened because you didn't add credentials to your hosts because you wanted to scan the storage via the EMS.  Scanning storage via EMS never was possible before so per Comment https://bugzilla.redhat.com/show_bug.cgi?id=1438963#c14 this was essentially an RFE.

Part of the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1529725 was _always_ scanning storage via the EMS so no host credentials are ever required which should cover the use-case you opened the BZ for.

Hopefully that makes sense, let me know if you have any questions.

Comment 20 Greg Scott 2018-02-06 22:35:23 UTC
Thanks Adam. I'll run that past the customer and see what they say.  If the end result is they can Smart State via the vCenter instead of hosts, they will be very happy.

Comment 21 Adam Grare 2018-02-07 13:27:32 UTC

*** This bug has been marked as a duplicate of bug 1529725 ***