[SRU] magnum deb v6.1.0 not containing queens/stable data

Bug #1789425 reported by Radu Popescu
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
magnum (Ubuntu)
Confirmed
Undecided
Unassigned
Bionic
Incomplete
Undecided
Unassigned

Bug Description

[Impact]
It's about this file:

https://github.com/openstack/magnum/blob/stable/queens/magnum/drivers/common/templates/kubernetes/fragments/configure-kubernetes-master.sh

The version installed has this condition:
if [ -n "$CERT_MANAGER_API" ]; then
    KUBE_CONTROLLER_MANAGER_ARGS="$KUBE_CONTROLLER_MANAGER_ARGS --cluster-signing-cert-file=$CERT_DIR/ca.crt --cluster-signing-key-file=$CERT_DIR/ca.key"
fi

The version that should be installed, has this condition:
if [ "$(echo $CERT_MANAGER_API | tr '[:upper:]
' '[:lower:]')" = "true" ]; then
    KUBE_CONTROLLER_MANAGER_ARGS="$KUBE_CONTROLLER_MANAGER_ARGS --cluster-signing-cert-file=$CERT_DIR/ca.crt --cluster-signing-key-file=$CERT_DIR/ca.key"
fi

CERT_MANAGER_API is either true or false, never empty.

Thanks

[Test Case]

This deb will be deployed by our magnum juju charm and configured as part of an Ubuntu OpenStack deployment. Any relevant test results will be posted back in this bug report.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned tests are attached to this bug.

[Discussion]
Updating to stable point release 6.1.1 fixes the aforementioned issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in magnum (Ubuntu):
status: New → Confirmed
Revision history for this message
Gabriel Samfira (gabriel-samfira) wrote :

So essentially the latest upstream stable release of queens should fix this. Correct?

summary: - magnum deb v6.1.0 not containing queens/stable data
+ [SRU] magnum deb v6.1.0 not containing queens/stable data
description: updated
description: updated
description: updated
Revision history for this message
Corey Bryant (corey.bryant) wrote :

I've uploaded magnum 6.1.1 to the bionic unapproved queue where it is awaiting review by the SRU team. Note I accidentally uploaded 3 exact copies (2 failed attempts to upload to my own PPA).

https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=

Revision history for this message
Corey Bryant (corey.bryant) wrote :

I've uploaded a new version of magnum 6.1.1 that also provides a fix for https://bugs.launchpad.net/cloud-archive/+bug/1789475.

Revision history for this message
Steve Langasek (vorlon) wrote :

This is evidently an openstack package, but the upstream point release is not covered by https://wiki.ubuntu.com/OpenStackUpdates (magnum is not on the list of packages). What is the expectation here? Is magnum covered by the QA process listed on that exception page?

This bug is marked 'confirmed' for cosmic, what is the status of fixing there?

Changed in magnum (Ubuntu Bionic):
status: New → Incomplete
Revision history for this message
Robie Basak (racb) wrote : Proposed package upload rejected

An upload of magnum to bionic-proposed has been rejected from the upload queue for the following reason: "Cleaning up the queue as https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1789425/comments/5 remains unanswered.".

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.