<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"DejaVu Sans";
panose-1:2 11 6 3 3 8 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.StylE-mailovZprvy17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=CS link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Hi!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>If this was OpenStack Kilo and HPE 3PAR over Fibre Channel, I would tell you that the volume extend operation is designed to work with detached volumes only. Hence you need cinder </span>reset-state. At least in our case, it does not update the SCSI devices and multipath setup. The volume continues to work with the old size. We do a live migrate operation afterwards to disconnect the storage from one node and connect to another. Even resize to the same node works. However, os-brick was introduced in Liberty, so the case may be different.<o:p></o:p></p><p class=MsoNormal>Tomas<span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Adam Dibiase [mailto:adibiase@digiumcloud.com] <br><b>Sent:</b> Wednesday, August 23, 2017 9:06 PM<br><b>To:</b> Sean McGinnis<br><b>Cc:</b> openstack-operators@lists.openstack.org<br><b>Subject:</b> Re: [Openstack-operators] cinder/nova issues<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='color:black'>Thanks Sean. I filed a bug report to track this. </span><span style='font-family:"DejaVu Sans","sans-serif";color:black'>Bug #1712651. I would agree with you on connectivity issues with the Netapp if it happened on all volume extensions, but this only happens in one scenario only.</span><o:p></o:p></p><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><div><p class=MsoNormal><span style='background:white'>Thanks, </span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='background:white'>Adam</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Aug 23, 2017 at 2:04 PM, Sean McGinnis <<a href="mailto:sean.mcginnis@gmx.com" target="_blank">sean.mcginnis@gmx.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hey Adam,<br><br>There have been some updates since Liberty to improve handling in the os-brick<br>library that handles the local device management. But with this showing the<br>paths down, I wonder if there's something else going on there between the<br>NetApp box and the Nova compute host.<br><br>Could you file a bug to track this? I think you could just copy and paste the<br>content of your original email since it captures a lot of great info.<br><br><a href="https://bugs.launchpad.net/cinder/+filebug" target="_blank">https://bugs.launchpad.net/cinder/+filebug</a><br><br>We can tag it with netapp so maybe it will get some attention there.<br><br>Thanks,<br>Sean<br><br>On Wed, Aug 23, 2017 at 01:01:24PM -0400, Adam Dibiase wrote:<br>> Greetings,<br>><br>> I am having an issue with nova starting an instance that is using a root<br>> volume that cinder has extended. More specifically, a volume that has been<br>> extended past the max resize limit of our Netapp filer. I am running<br>> Liberty and upgraded cinder packages to 7.0.3 from 7.0.0 to take advantage<br>> of this functionality. >From what I can gather, it uses sub-lun cloning to<br>> get past the hard limit set by Netapp when cloning past 64G (starting from<br>> a 4G volume).<br>><br>> *Environment*:<br>><br>> - Release: Liberty<br>> - Filer: Netapp<br>> - Protocol: Fiberchannel<br>> - Multipath: yes<br>><br>><br>><br>> *Steps to reproduce: *<br>><br>> - Create new instance<br>> - stop instance<br>> - extend the volume by running the following commands:<br>> - cinder reset-state --state available (volume-ID or name)<br>> - cinder extend (volume-ID or name) 100<br>> - cinder reset-state --state in-use (volume-ID or name)<br>> - start instance with either nova start or nova reboot --hard --same<br>> result<br>><br>><br>> I can see that the instance's multipath status is good before the resize...<br>><br>> *360a98000417643556a2b496d58665473 dm-17 NETAPP ,LUN *<br>><br>> size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw<br>><br>> |-+- policy='round-robin 0' prio=-1 status=active<br>><br>> | |- 6:0:1:5 sdy 65:128 active undef running<br>><br>> | `- 7:0:0:5 sdz 65:144 active undef running<br>><br>> `-+- policy='round-robin 0' prio=-1 status=enabled<br>><br>> |- 6:0:0:5 sdx 65:112 active undef running<br>><br>> `- 7:0:1:5 sdaa 65:160 active undef running<br>><br>><br>> Once the volume is resized, the lun goes to a failed state and it does not<br>> show the new size:<br>><br>><br>> *360a98000417643556a2b496d58665473 dm-17 NETAPP ,LUN *<br>><br>> size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw<br>><br>> |-+- policy='round-robin 0' prio=-1 status=enabled<br>><br>> | |- 6:0:1:5 sdy 65:128 failed undef running<br>><br>> | `- 7:0:0:5 sdz 65:144 failed undef running<br>><br>> `-+- policy='round-robin 0' prio=-1 status=enabled<br>><br>> |- 6:0:0:5 sdx 65:112 failed undef running<br>><br>> `- 7:0:1:5 sdaa 65:160 failed undef running<br>><br>><br>> Like I said, this only happens on volumes that have been extended past 64G.<br>> Smaller sizes to not have this issue. I can only assume that the original<br>> lun is getting destroyed after the clone process and that is cause of the<br>> failed state. Why is it not picking up the new one and attaching it to the<br>> compute node? Is there something I am missing?<br>><br>> Thanks in advance,<br>><br>> Adam<br><br>> _______________________________________________<br>> OpenStack-operators mailing list<br>> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>