<div dir="ltr">Nova-novncproxy.log:<div><br></div><div>2023-06-25 10:55:32.487 515433 INFO nova.console.websocketproxy [-] 172.25.201.205 - - [25/Jun/2023 10:55:32] <a href="http://172.25.201.205">172.25.201.205</a>: Plain non-SSL (ws://) WebSocket connection<br>2023-06-25 10:55:32.489 515433 INFO nova.console.websocketproxy [-] 172.25.201.205 - - [25/Jun/2023 10:55:32] <a href="http://172.25.201.205">172.25.201.205</a>: Path: '/?token=f985582a-47ae-48f6-bfb3-477dae02c369'<br>2023-06-25 10:55:33.131 515433 INFO nova.console.websocketproxy [req-ee483ce0-1d1a-446e-8e03-da371daa977d - - - - -] 34368: connect info: ConsoleAuthToken(access_url_base='<a href="https://bolt.bdxworld.com:13080/vnc_auto.html">https://bolt.bdxworld.com:13080/vnc_auto.html</a>',console_type='novnc',created_at=2023-06-25T10:55:31Z,host='172.25.221.228',id=3579,instance_uuid=cdcfe890-4f15-4091-abc1-9fe0cf7eff85,internal_access_path=None,port=5900,token='***',updated_at=None)<br>2023-06-25 10:55:33.135 515433 INFO nova.console.websocketproxy [req-ee483ce0-1d1a-446e-8e03-da371daa977d - - - - -] 34368: connecting to: <a href="http://172.25.221.228:5900">172.25.221.228:5900</a><br>2023-06-25 10:55:33.419 515433 INFO nova.console.securityproxy.rfb [req-ee483ce0-1d1a-446e-8e03-da371daa977d - - - - -] Finished security handshake, resuming normal proxy mode using secured socket<br>2023-06-25 10:55:33.456 515433 INFO nova.console.websocketproxy [req-ee483ce0-1d1a-446e-8e03-da371daa977d - - - - -] handler exception: [Errno 107] Transport endpoint is not connected<br>2023-06-25 10:55:34.830 515436 INFO nova.console.websocketproxy [-] 172.25.201.205 - - [25/Jun/2023 10:55:34] <a href="http://172.25.201.205">172.25.201.205</a>: Plain non-SSL (ws://) WebSocket connection<br>2023-06-25 10:55:34.832 515436 INFO nova.console.websocketproxy [-] 172.25.201.205 - - [25/Jun/2023 10:55:34] <a href="http://172.25.201.205">172.25.201.205</a>: Path: '/?token=f985582a-47ae-48f6-bfb3-477dae02c369'<br>2023-06-25 10:55:35.458 515436 INFO nova.console.websocketproxy [req-c9f5d4de-a4e3-4040-9fcf-dc42d5f0b0d3 - - - - -] 34369: connect info: ConsoleAuthToken(access_url_base='<a href="https://bolt.bdxworld.com:13080/vnc_auto.html">https://bolt.bdxworld.com:13080/vnc_auto.html</a>',console_type='novnc',created_at=2023-06-25T10:55:31Z,host='172.25.221.228',id=3579,instance_uuid=cdcfe890-4f15-4091-abc1-9fe0cf7eff85,internal_access_path=None,port=5900,token='***',updated_at=None)<br>2023-06-25 10:55:35.461 515436 INFO nova.console.websocketproxy [req-c9f5d4de-a4e3-4040-9fcf-dc42d5f0b0d3 - - - - -] 34369: connecting to: <a href="http://172.25.221.228:5900">172.25.221.228:5900</a><br>2023-06-25 10:55:35.753 515436 INFO nova.console.securityproxy.rfb [req-c9f5d4de-a4e3-4040-9fcf-dc42d5f0b0d3 - - - - -] Finished security handshake, resuming normal proxy mode using secured socket<br>2023-06-25 10:55:35.790 515436 INFO nova.console.websocketproxy [req-c9f5d4de-a4e3-4040-9fcf-dc42d5f0b0d3 - - - - -] handler exception: [Errno 107] Transport endpoint is not connected<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jun 25, 2023 at 4:20 PM Swogat Pradhan <<a href="mailto:swogatpradhan22@gmail.com">swogatpradhan22@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div>After doing a console url show after migration, I am still unable to access the console.</div><div><br></div><div> My site consists of 1 central site and 2 DCN sites. Consoles for central and DCN02 are working fine without any issues.</div><div>But when i am creating an instance for DCN01 the console for the instance is not coming up (attached image for reference).</div><div><br></div><div>Today I created 3 different VM's using the same flavor, image, security group, the instances were created in the same compute host. Console was not accessible, so I shelved and unshelved all 3 instances, after which I was able to access the console for 2 of those VM's and am still unable to access the console of the 3rd VM no matter what I do.</div><div><br></div><div>With regards,</div><div>Swogat Pradhan</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 24, 2023 at 2:00 AM melanie witt <<a href="mailto:melwittt@gmail.com" target="_blank">melwittt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 06/22/23 20:07, Swogat Pradhan wrote:<br>
> Hi Mel,<br>
> Thank you for your response.<br>
> I am facing issues with the instance console (vnc) in the openstack <br>
> dashboard, Most of the time I shelve the instance and unshelve the <br>
> instance to get the console.<br>
> But there are some VM's I created which are not working even after <br>
> shelve/unshelve.<br>
> <br>
> I have used the same director to deploy a total of a central and 2 edge <br>
> sites.<br>
> This issue is happening on a single edge site.<br>
> Cold Migration also helps in some situations.<br>
<br>
OK, you didn't mention whether requesting a new console 'openstack <br>
console url show --vnc <server>' gets you a working console after a <br>
migration (or other event where you see the console stop working). I'm <br>
trying to determine whether the behavior you're seeing is expected or a <br>
bug. After an instance is moved to a different compute node than the one <br>
it was on when the console was started, that console is not expected to <br>
work anymore. And a new console needs to be started.<br>
<br>
Can you give steps for reproducing the issue? Maybe that will provide <br>
more clarity.<br>
<br>
-melwitt<br>
<br>
> On Fri, Jun 23, 2023 at 12:42 AM melanie witt <<a href="mailto:melwittt@gmail.com" target="_blank">melwittt@gmail.com</a> <br>
> <mailto:<a href="mailto:melwittt@gmail.com" target="_blank">melwittt@gmail.com</a>>> wrote:<br>
> <br>
> On 06/22/23 01:08, Swogat Pradhan wrote:<br>
> > Hi,<br>
> > Please find the below log:<br>
> > [root@dcn01-hci-1 libvirt]# cat virtqemud.log<br>
> > 2023-06-22 07:40:01.575+0000: 350319: error :<br>
> virNetSocketReadWire:1804<br>
> > : End of file while reading data: Input/output error<br>
> > 2023-06-22 07:40:01.575+0000: 350319: error :<br>
> virNetSocketWriteWire:1844<br>
> > : Cannot write data: Broken pipe<br>
> ><br>
> > I think this is causing the problem of not getting the instance<br>
> console.<br>
> <br>
> When you say "instance console" are you referring to an interactive<br>
> console like VNC or are you talking about the console log for the<br>
> instance?<br>
> <br>
> If it's the interactive console, if you have a console open and then<br>
> migrate the instance, that console will not be moved along with the<br>
> instance. When a user requests a console, the console proxy service<br>
> establishes a connection to the compute host where the instance is<br>
> located. The proxy doesn't know when an instance has been moved though,<br>
> so if the instance is moved, the user will need to request a new<br>
> console<br>
> (which will establish a new connection to the new compute host).<br>
> <br>
> Is that the behavior you are seeing?<br>
> <br>
> -melwitt<br>
> <br>
> > On Fri, Jun 2, 2023 at 11:27 AM Swogat Pradhan<br>
> > <<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a> <mailto:<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a>><br>
> <mailto:<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a><br>
> <mailto:<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a>>>> wrote:<br>
> ><br>
> > Update:<br>
> > If the i am performing any activity like migration or resize<br>
> of an<br>
> > instance whose console is accessible, the console becomes<br>
> > inaccessible giving out the following error : something went<br>
> wrong,<br>
> > connection is closed<br>
> ><br>
> > The was 1 other instance whose console was not accessible and<br>
> i did<br>
> > a shelve and unshelve and suddenly the instance console became<br>
> > accessible.<br>
> ><br>
> > This is a peculiar behavior and i don't understand where is<br>
> the issue .<br>
> ><br>
> > With regards,<br>
> > Swogat Pradhan<br>
> ><br>
> > On Fri, Jun 2, 2023 at 11:19 AM Swogat Pradhan<br>
> > <<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a> <mailto:<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a>><br>
> <mailto:<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a><br>
> <mailto:<a href="mailto:swogatpradhan22@gmail.com" target="_blank">swogatpradhan22@gmail.com</a>>>> wrote:<br>
> ><br>
> > Hi,<br>
> > I am creating instances in my DCN site and i am unable to get<br>
> > the console sometimes, error: something went wrong,<br>
> connection<br>
> > is closed<br>
> ><br>
> > I have 3 instances now running on my hci02 node and there is<br>
> > console access on 1 of the vm's and the rest two i am not<br>
> > getting the console, i have used the same flavor, same image<br>
> > same security group for the VM's.<br>
> ><br>
> > Please suggest what can be done.<br>
> ><br>
> > With regards,<br>
> > Swogat Pradhan<br>
> ><br>
> <br>
<br>
</blockquote></div>
</blockquote></div>