Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ResourceName: iscsiinitiator #42

Open
ewhitesides opened this issue Nov 27, 2018 · 2 comments
Open

ResourceName: iscsiinitiator #42

ewhitesides opened this issue Nov 27, 2018 · 2 comments
Labels
bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community.

Comments

@ewhitesides
Copy link

ewhitesides commented Nov 27, 2018

applied configuration extremely similar to the example given for the iSCSIInitiator resource. however, tests show the following even though it is connected and working fine:

Service iSCSIService {
Name = 'MSiSCSI'
StartupType = 'Automatic'
State = 'Running'
}

iSCSIInitiator iSCSIInitiator {
Ensure = 'Present'
NodeAddress = 'iqn.2000-01.com.longiscsiname'
TargetPortalAddress = 'x.x.x.x'
InitiatorPortalAddress = 'x.x.x.x'
IsPersistent = $true
DependsOn = "[Service]iSCSIService"
}

VERBOSE: [mycomputer]: LCM: [ Start Resource ] [[iSCSIInitiator]iSCSIInitiator]
VERBOSE: [mycomputer]: LCM: [ Start Test ] [[iSCSIInitiator]iSCSIInitiator]
VERBOSE: [mycomputer]: [[iSCSIInitiator]iSCSIInitiator] Test-TargetResource: Testing iSCSI Initiator 'iqn.2000-01.com.longiscsiname', 'x.x.x.x' from ''.
VERBOSE: [mycomputer]: [[iSCSIInitiator]iSCSIInitiator] Test-TargetResource: iSCSI Connection 'iqn.2000-01.com.longiscsiname' does not exist but should. Change required.
VERBOSE: [mycomputer]: LCM: [ End Test ] [[iSCSIInitiator]iSCSIInitiator] False in 0.2500 seconds.
VERBOSE: [mycomputer]: LCM: [ End Resource ] [[iSCSIInitiator]iSCSIInitiator]

because it works correctly in applying, my temporary solution is to apply it, then comment it out, and apply my configuration again, so the testing doesn't keep alerting me on a false configuration.

@PlagueHO PlagueHO added bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community. labels Nov 28, 2018
@PlagueHO
Copy link
Member

PlagueHO commented Nov 28, 2018

Hi @ewhitesides - thanks for raising this. It does look like a bit of a bug here. If you run the following commands on the machine with the initiator what do you see:

Get-iSCSIConnection -IscsiTarget (Get-iSCSITarget -NodeAddress 'iqn.2000-01.com.longiscsiname')

Also, what do you see if you just run:

Get-iSCSIConnection

What appears to be happening is that all the target is all set up the connection record isn't appearing.

@ewhitesides
Copy link
Author

get-iscsiconnection returns an object with info on the connection
get-iscsiconnection | get-iscsitarget also returns the correct node address.

however, get-isciconnection -iscsitarget (get-iscsitarget -nodeaddress ) returns 'no matching MSFT_iSCSIConnection objects found'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community.
Projects
None yet
Development

No branches or pull requests

2 participants