[Bug 2155247] Re: [SRU] magnum-api-wsgi missing from Ubuntu package

[Nick Rosbrook]

Hello Guillaume, or anyone else affected,

Accepted magnum into resolute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/magnum/22.0.0-0ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
resolute to verification-done-resolute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-resolute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: magnum (Ubuntu Resolute)
       Status: New => Fix Committed

** Tags added: verification-needed-resolute

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/2155247

Title:
  [SRU] magnum-api-wsgi missing from Ubuntu package

Status in Ubuntu Cloud Archive gazpacho series:
  New
Status in magnum package in Ubuntu:
  Fix Released
Status in magnum source package in Resolute:
  Fix Committed
Status in magnum source package in Stonking:
  Fix Released

Bug description:
  [ Impact ]

   * In Resolute, Apache/mod_wsgi deployments that use `magnum-api` expect
     `/usr/bin/magnum-api-wsgi`, but the package does not install it. Apache
     therefore cannot load the Magnum API and reports that the WSGI target is
     missing.

   * This makes the Magnum API unavailable in affected deployments.

   * The upload installs a small compatibility WSGI script at the expected path.
     It imports Magnum's current `magnum.wsgi.api.application` entry point.

  [ Test Plan ]

   * Use a disposable Resolute Magnum controller configured to serve `magnum-api`
     through Apache/mod_wsgi.

   * Before enabling `resolute-proposed`, install `magnum-api` and confirm the
     affected package does not own `/usr/bin/magnum-api-wsgi`:

         sudo apt update
         sudo apt install magnum-api
         dpkg-query -L magnum-api | grep -Fx /usr/bin/magnum-api-wsgi

     The command must produce no output. Restart Apache and confirm its log
     contains the missing WSGI-target error.

   * Enable `resolute-proposed`, install the candidate `magnum-api` package, and
     record the installed versions of `magnum-api` and `magnum-common`.

   * Confirm that the candidate owns an executable compatibility script and that
     it imports the WSGI application:

         dpkg-query -S /usr/bin/magnum-api-wsgi
         test -x /usr/bin/magnum-api-wsgi
         python3 -c 'from magnum.wsgi.api import application; assert callable(application)'

   * Restart Apache without changing its configuration. Confirm it remains
     active, its log no longer reports the missing-script error, and an
     authenticated `openstack coe service list` request reaches the Magnum API.

  [ Where problems could occur ]

   * An incorrect script path, module import, or WSGI callable would leave the
     API unavailable. Apache startup failures, Python tracebacks, or HTTP 5xx
     responses would show the regression.

   * The new script and generated Python dependency could be placed in the wrong
     binary package or make package upgrades unsatisfiable. Verify ownership,
     installation, and upgrades of `magnum-api` and `magnum-common` together.

   * A future upstream version may restore the same script path. Future merges
     must check that the packaging rule does not overwrite an upstream script.

  [ Other Info ]

   * LP: #2155247 records the missing Apache WSGI target. This update is a
     packaging compatibility fix; it does not change Magnum API behaviour.

  magnum-api no longer ships /usr/bin/magnum-api-wsgi after upstream
  removed the PBR wsgi_scripts entry point.

  Existing mod_wsgi based deployments expect this path and fail because
  the WSGI script is missing.

  Error:
  2026-06-04T12:40:27.510Z [wsgi-magnum-api] 2026-06-04 12:40:27.510368 Target WSGI script not found or unable to stat: /usr/bin/magnum-api-wsgi

  Reference:
  https://governance.openstack.org/tc/goals/completed/2025.2/migrate-
  from-wsgi-scripts-to-module-paths.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/gazpacho/+bug/2155247/+subscriptions