Cannot create guest after certificate relation is added

Bug #1862974 reported by Liam Young
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Keystone Charm
Fix Released
High
Unassigned
OpenStack Neutron API Charm
Fix Released
High
Liam Young
OpenStack Nova Cloud Controller Charm
Fix Released
High
Liam Young
OpenStack Nova Compute Charm
Invalid
High
Liam Young
OpenStack Placement Charm
Invalid
High
Liam Young

Bug Description

When the certificate relation is added to the api services in the cloud it sometimes causes services to be unable to talk to one another. This seems to be due to them attempting to talk http to https services.

This is related to Bug #1826382

Liam Young (gnuoy)
Changed in charm-nova-compute:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Liam Young (gnuoy)
Changed in charm-nova-cloud-controller:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Liam Young (gnuoy)
Changed in charm-neutron-api:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Liam Young (gnuoy)
Changed in charm-placement:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Liam Young (gnuoy)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-nova-cloud-controller (master)

Fix proposed to branch: master
Review: https://review.opendev.org/708094

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

Reviewed: https://review.opendev.org/708094
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=335b67c66a835e983349ecd4579619c333a77b48
Submitter: Zuul
Branch: master

commit 335b67c66a835e983349ecd4579619c333a77b48
Author: Liam Young <email address hidden>
Date: Mon Feb 17 11:03:49 2020 +0000

    Watch & react to placement and neutron ep changes.

    Request to be informed of changes to placement and neutron changes.
    If a placement change occurs restart nova-scheduler as it will
    cache the old endpoint url and tell nova-compute to restart its
    services as they will have done the same.

    Change-Id: I7537723e40a5a25672fbbdc2d5c3144724f6240a
    Closes-Bug: #1862974

Changed in charm-nova-cloud-controller:
status: In Progress → Fix Committed
Revision history for this message
Yoshi Kadokawa (yoshikadokawa) wrote :

I confirmed the same symptom in OpenStack Train environment using Placement charm.
After upgrading the nova-cloud-controller to cs:~openstack-charmers-next/nova-cloud-controller-475, the issue was mitigated.
Since this is affecting customer's deployment, I have subscribed this to field-high.
Can this fix be backported to stable charm as well?
Thank you

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-nova-cloud-controller (stable/20.02)

Fix proposed to branch: stable/20.02
Review: https://review.opendev.org/713356

Revision history for this message
Nobuto Murata (nobuto) wrote :
Changed in charm-keystone:
status: New → Fix Committed
Revision history for this message
Nobuto Murata (nobuto) wrote :
Changed in charm-neutron-api:
status: Confirmed → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-nova-cloud-controller (stable/20.02)

Change abandoned by Nobuto Murata (<email address hidden>) on branch: stable/20.02
Review: https://review.opendev.org/713356
Reason: Dropping this review for the time being. The bug is related to 3 charms at least and charm-helpers so I will leave it to OpenStack Charmers for proper backports altogether.

Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

Removing placement and nova-compute as this bug is resolved via changes already landed into other projects.

Changed in charm-placement:
status: Confirmed → Invalid
Changed in charm-nova-compute:
status: Confirmed → Invalid
James Page (james-page)
Changed in charm-nova-cloud-controller:
milestone: none → 20.05
Changed in charm-neutron-api:
milestone: none → 20.05
Changed in charm-keystone:
milestone: none → 20.05
importance: Undecided → High
David Ames (thedac)
Changed in charm-nova-cloud-controller:
status: Fix Committed → Fix Released
Changed in charm-neutron-api:
status: Fix Committed → Fix Released
Changed in charm-keystone:
status: Fix Committed → Fix Released
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.