Closed berndtfromat closed 1 year ago
So, this is a bug with Set-OVNetworkSet
inadvertently changing the Network Set type when it should not. I have been finalizing the 8.30 library release, and will get this fixed in both 8.00 and 8.30.
if this is possible pls also for the last valid 6.60 version or are newer cmdlets compatible with older Oneviews? I guess there is no distinct positive answer for this question, the other way around is more likely to work.
Yes, I will backport the fix to the 6.60 library for LTS customers.
Providing an update: I have finally resolved a number of lab issues that have caused me serious delays in getting updates published. I'm testing an 8.00 release now, then a 6.60 release. Should have them published over the US holiday weekend.
I have just published an updated 8.00 library, and am in the process of publishing a 6.60 library update.
This is fixed in the following releases:
Please verify before this issue is closed.
thx a lot! creation of network did work this time without changing the networksettype and still having more entries than 333:
me@server> New-OVNetwork -Name 1234_mynetwork -Type Ethernet -VlanId 1234 -NetworkSet (Get-OVNetworkSet -Name mynetworkset)
Name Status Details
---- ------ -------
1234_mynetwork Completed @{associatedResource=; associatedTaskUri=; completedSteps=0; computedPercentComplete=100; created=2023-06-06T15:12:44.850Z; data=; eTag="1"; expectedDuration=240; hidden=False; modif...
me@server> Get-OVNetworkSet -Name mynetworkset | ft networkSetType
networkSetType
--------------
Large
me@server> (Get-OVNetworkSet -Name mynetworkset | select -ExpandProperty networkUris | measure).count
335
me@server>
fixed, verified with 6.60.3530.1622
Expected Behavior
create network and add it to an existing networkset of type large in the same step
Actual Behavior
ignores existing networkset type and therefore fails in rare cases. Seems like the cmdlet actively tries to change a networkset to type regular which will/would create issues in environments where (maybe 40GBit interconnects/3820C nics and) vlan# >333 are used.
Steps to reproduce
I can't easily reproduce this since it would have effect on our production, but you can see the anonymized history in part 1 (production) and the relevant passage in the second part (test system-> not anonymized). There is also a HPE Support Case 5372126802 with support dump and L2 comment, etc.
part 1 - history
relevant part of supportdump in which we see the wrong networksettype: putResource():327,Putting NetworkSet- id:00000000-0000-0000-0000-000000000001, complexObject:com.hp.ci.mgmt.crm.model.NetworkSetV5@00000002 [ nativeNetworkUri=, networkUris= [ /rest/ethernet-networks/00000000-0000-0000-0000-000000000003, /rest/ethernet-networks/00000000-0000-0000-0000-000000000004, /rest/ethernet-networks/00000000-0000-0000-0000-000000000005, /rest/ethernet-networks/00000000-0000-0000-0000-000000000006, /rest/ethernet-networks/00000000-0000-0000-0000-000000000007, /rest/ethernet-networks/00000000-0000-0000-0000-000000000008, /rest/ethernet-networks/00000000-0000-0000-0000-000000000009, /rest/ethernet-networks/00000000-0000-0000-0000-000000000010, /rest/ethernet-networks/00000000-0000-0000-0000-000000000011, /rest/ethernet-networks/00000000-0000-0000-0000-000000000012, /rest/ethernet-networks/00000000-0000-0000-0000-000000000013, /rest/ethernet-networks/00000000-0000-0000-0000-000000000014, /rest/ethernet-networks/00000000-0000-0000-0000-000000000015, /rest/ethernet-networks/00000000-0000-0000-0000-000000000016, /rest/ethernet-networks/00000000-0000-0000-0000-000000000017, /rest/ethernet-networks/00000000-0000-0000-0000-000000000018, /rest/ethernet-networks/00000000-0000-0000-0000-000000000019, /rest/ethernet-networks/00000000-0000-0000-0000-000000000020, /rest/ethernet-networks/00000000-0000-0000-0000-000000000021, /rest/ethernet-networks/00000000-0000-0000-0000-000000000022, /rest/ethernet-networks/00000000-0000-0000-0000-000000000023, /rest/ethernet-networks/00000000-0000-0000-0000-000000000024, /rest/ethernet-networks/00000000-0000-0000-0000-000000000025, /rest/ethernet-networks/00000000-0000-0000-0000-000000000026, /rest/ethernet-networks/00000000-0000-0000-0000-000000000027, /rest/ethernet-networks/00000000-0000-0000-0000-000000000028, /rest/ethernet-networks/00000000-0000-0000-0000-000000000029, /rest/ethernet-networks/00000000-0000-0000-0000-000000000030, /rest/ethernet-networks/00000000-0000-0000-0000-000000000031, /rest/ethernet-networks/00000000-0000-0000-0000-000000000032, /rest/ethernet-networks/00000000-0000-0000-0000-000000000033, /rest/ethernet-networks/00000000-0000-0000-0000-000000000034, /rest/ethernet-networks/00000000-0000-0000-0000-000000000035, /rest/ethernet-networks/00000000-0000-0000-0000-000000000036, /rest/ethernet-networks/00000000-0000-0000-0000-000000000037, /rest/ethernet-networks/00000000-0000-0000-0000-000000000038, /rest/ethernet-networks/00000000-0000-0000-0000-000000000039, /rest/ethernet-networks/00000000-0000-0000-0000-000000000040 ], connectionTemplateUri=/rest/connection-templates/00000000-0000-0000-0000-000000000041, networkSetType=Regular, scopesUri=/rest/scopes/resources/rest/network-sets/00000000-0000-0000-0000-000000000001, initialScopeUris=, delegate=com.hp.ci.mgmt.model.ManagedResourceDelegate@00000042[name=mynetworkset,description=,status=,state=]uri=/rest/network-sets/00000000-0000-0000-0000-000000000001, category=network-sets, type=network-setV5, eTag=00000000-0000-0000-0000-000000000043, created=, modified=, requestId=ZBNLhJWmbgkhwfh3xax8ewAAAKc ], parentTask:null, force:false, eTag:00000000-0000-0000-0000-000000000043, locale:en_US
BUT the used networkset is already existent and is of type large
part 2 - theory - see line 520 (why is the networkset changed to regular???)(end is shortened due to max comment size)
Version Information
HPE OneView PowerShell Library Version (
Get-HPOVVersion
or$PSLibraryVersion
): 6.30.2928.3678/6.60.3332.3428 HPE OneView Appliance Version (Get-HPOVVersion -ApplianceVer
): 6.60.02.467825.00 Output from$PSVersionTable
on your Windows Host: