vnc console doesnt work in openstack yoga

Bug #1974082 reported by Maxim Monin
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Invalid
Undecided
Unassigned
OpenStack Nova Compute Charm
Fix Committed
High
Unassigned

Bug Description

nova config generation for vnc options uses [Default] section. But this section is depricated in openstack yoga. Valid config requires generation:
[vnc]
server_proxyclient_address = $my_ip

Revision history for this message
Maxim Monin (maximmonin) wrote :

issue was fixed, moved from "stable" version to "yoga/stable" version of charm

Revision history for this message
Siarhei Matashuk (m1588) wrote :

I have the same issue also, it seems that with yoga/stable channel of nova-compute charm the nova.conf is rendered using /var/lib/juju/agents/unit-nova-compute-6/charm/templates/train/nova.conf template which is old and has no [vnc] section.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

> I have the same issue also, it seems that with yoga/stable channel of nova-compute charm the nova.conf is rendered using /var/lib/juju/agents/unit-nova-compute-6/charm/templates/train/nova.conf template which is old and has no [vnc] section.

Yes, this is an issue. More interestingly, it's due to the (deprecated) vncserver_proxy_address being removed at yoga and only using the server_proxy_address: https://docs.openstack.org/releasenotes/nova/yoga.html#upgrade-notes

For future travellers: move the vnc options into a [vnc] section in a newly created ./templates/yoga/nova.conf.

Fix on master, then backport to stable/yoga branch.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

This bug only affects the nova-compute charm; the console isn't provided from the nova-cloud-controller for this particularly setting.

Changed in charm-nova-compute:
importance: Undecided → High
status: New → Triaged
Changed in charm-nova-cloud-controller:
status: New → Invalid
tags: added: backport-required good-first-bug
Revision history for this message
Jason C. Nucciarone (nuccitheboss) wrote :

Currently working on this bug. However, a new bug has been presented by the zaza openstack tests. For some reason, the tests are failing to retrieve the name of the nova-compute/0 unit.

New bug has been raised against the zaza openstack tests, so once this issue is resolved I should be able to propose my fix for nova-compute. Here is the link to the bug report on the zaza openstack repository: https://github.com/openstack-charmers/zaza-openstack-tests/issues/824.

Changed in charm-nova-compute:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-nova-compute (master)

Reviewed: https://review.opendev.org/c/openstack/charm-nova-compute/+/850247
Committed: https://opendev.org/openstack/charm-nova-compute/commit/73edc4f817d0a8c281284a0df850d93ea5427014
Submitter: "Zuul (22348)"
Branch: master

commit 73edc4f817d0a8c281284a0df850d93ea5427014
Author: NucciTheBoss <email address hidden>
Date: Mon Jul 18 13:37:42 2022 -0400

    Update nova.conf for OpenStack Yoga

    This merge request focuses on fixing the VNC config for OpenStack Yoga
    on the Focal and Jammy series. Originally, the Yoga version of this
    charm was using a template nova.conf file from Train which did not use
    the new [vnc] required for Yoga. Train had the VNC config in the
    [DEFAULT] section, which is depreciated in Yoga.

    Itemized changes to charm below:

     * Create templates/yoga
     * Move VNC config to [vnc] section in nova.conf
     * Rename VNC config keys to follow the Yoga specification.

    Closes-Bug: #1974082
    Closes-Bug: #1734683

    Change-Id: Ic100528f9f38bbc0c83e4f563166113024e3db59

Changed in charm-nova-compute:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-nova-compute (stable/yoga)

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/charm-nova-compute/+/864697

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-nova-compute (stable/yoga)

Reviewed: https://review.opendev.org/c/openstack/charm-nova-compute/+/864697
Committed: https://opendev.org/openstack/charm-nova-compute/commit/9092d68ae66335c0bf2db75dffdb2731d9165fcd
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit 9092d68ae66335c0bf2db75dffdb2731d9165fcd
Author: NucciTheBoss <email address hidden>
Date: Mon Jul 18 13:37:42 2022 -0400

    Update nova.conf for OpenStack Yoga

    This merge request focuses on fixing the VNC config for OpenStack Yoga
    on the Focal and Jammy series. Originally, the Yoga version of this
    charm was using a template nova.conf file from Train which did not use
    the new [vnc] required for Yoga. Train had the VNC config in the
    [DEFAULT] section, which is depreciated in Yoga.

    Itemized changes to charm below:

     * Create templates/yoga
     * Move VNC config to [vnc] section in nova.conf
     * Rename VNC config keys to follow the Yoga specification.

    Closes-Bug: #1974082
    Closes-Bug: #1734683

    Change-Id: Ic100528f9f38bbc0c83e4f563166113024e3db59
    (cherry picked from commit 73edc4f817d0a8c281284a0df850d93ea5427014)

tags: added: in-stable-yoga
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.