VNC viewer should open on 10.20.20.1 and not on 127.0.0.1

Thank you for the bug report and precise root cause analysis. You may be able to work around this by dropping a file into the correct .d directory in /var/snap/common/microstack/etc, and restarting services (sudo snap restart microstack).

This bug can be closed when the correct defaults are set.

Hi,

thanks for the answer. Can you instruct me which file to fix to get the
correct behavior, please?

Thanks a lot,
/PA

On Thu, 23 Jan 2020 at 07:50, Pete Vander Giessen <
<email address hidden>> wrote:

> Thank you for the bug report and precise root cause analysis. You may be
> able to work around this by dropping a file into the correct .d
> directory in /var/snap/common/microstack/etc, and restarting services
> (sudo snap restart microstack).
>
> This bug can be closed when the correct defaults are set.
>
> ** Changed in: microstack
> Importance: Undecided => High
>
> ** Changed in: microstack
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860508
>
> Title:
> VNC viewer should open on 10.20.20.1 and not on 127.0.0.1
>
> Status in MicroStack:
> Confirmed
>
> Bug description:
> I have a microstack on a Ubuntu 18.04 (server) VM runnng directly over
> virsh. I'm able to access the dashboard with a route on the host. I'm
> using
>
> route add 10.20.20.0/24 via <guest_ip>
>
> to access the VMs created in the microstack. When I want to access an
> instance's console through the Network Topology in te Dashboard, the
> browser in the host gets finally redirected to 127.0.0.1 and thus can
> not access the instance's console.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/microstack/+bug/1860508/+subscriptions
>

--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellet zu werden
Georg Kreisler

Hi Pedro,

You probably want to make a file called something like "custom_console.conf" in /var/snap/microstack/common/etc/nova/nova.conf.d. The docs on what settings you might want to put in the file look like they live here:

https://docs.openstack.org/nova/stein/admin/remote-console-access.html#vnc-configuration-options

As a note to whomever makes a formal PR against MicroStack to fix the bug (probably me), you'll want to drop the settings into https://opendev.org/x/microstack/src/branch/master/snap-overlay/etc/nova/nova.conf.d/, probably as "console.conf" or "vnc.conf".

Quick follow up: we may need to add a console proxy service to the snap; this may not work until we add that component, along with default config for it.

Thx a ton!
/PA

Enviado desde mi iPhone

> El 23 ene 2020, a las 10:05, Pete Vander Giessen <email address hidden> escribió:
>
> Hi Pedro,
>
> You probably want to make a file called something like
> "custom_console.conf" in
> /var/snap/microstack/common/etc/nova/nova.conf.d. The docs on what
> settings you might want to put in the file look like they live here:
>
> https://docs.openstack.org/nova/stein/admin/remote-console-access.html
> #vnc-configuration-options
>
> As a note to whomever makes a formal PR against MicroStack to fix the
> bug (probably me), you'll want to drop the settings into
> https://opendev.org/x/microstack/src/branch/master/snap-
> overlay/etc/nova/nova.conf.d/, probably as "console.conf" or "vnc.conf".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860508
>
> Title:
> VNC viewer should open on 10.20.20.1 and not on 127.0.0.1
>
> Status in MicroStack:
> Confirmed
>
> Bug description:
> I have a microstack on a Ubuntu 18.04 (server) VM runnng directly over
> virsh. I'm able to access the dashboard with a route on the host. I'm
> using
>
> route add 10.20.20.0/24 via <guest_ip>
>
> to access the VMs created in the microstack. When I want to access an
> instance's console through the Network Topology in te Dashboard, the
> browser in the host gets finally redirected to 127.0.0.1 and thus can
> not access the instance's console.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/microstack/+bug/1860508/+subscriptions

This falls under the roadmap work to enable the console.

Moving to wishlist for now, to reflect that this is feature work. It is still important, and still is on the roadmap!

Surely without a console, this snap's not usable?
Is there a way of getting a console interface from the command line?

Also, this is a duplicate of https://bugs.launchpad.net/microstack/+bug/1812417 should anyone get here by Google.

Hi David,

you can access the VM when you assign a floating IP and ssh into the VM
with that IP address. ALthough that is convoluted, right?

/PA

On Sat, 18 Apr 2020 at 19:25, David Field <email address hidden>
wrote:

> Surely without a console, this snap's not usable?
> Is there a way of getting a console interface from the command line?
>
> Also, this is a duplicate of
> https://bugs.launchpad.net/microstack/+bug/1812417 should anyone get
> here by Google.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860508
>
> Title:
> VNC viewer should open on 10.20.20.1 and not on 127.0.0.1
>
> Status in MicroStack:
> Confirmed
>
> Bug description:
> I have a microstack on a Ubuntu 18.04 (server) VM runnng directly over
> virsh. I'm able to access the dashboard with a route on the host. I'm
> using
>
> route add 10.20.20.0/24 via <guest_ip>
>
> to access the VMs created in the microstack. When I want to access an
> instance's console through the Network Topology in te Dashboard, the
> browser in the host gets finally redirected to 127.0.0.1 and thus can
> not access the instance's console.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/microstack/+bug/1860508/+subscriptions
>

--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellet zu werden
Georg Kreisler