[Bug 2012073] Re: [SRU] SwiftSignalHandle fails due to python2-3 decode error

[Steve Langasek]

Hello Rodrigo, or anyone else affected,

Accepted heat into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/heat/1:19.0.0-0ubuntu1.2 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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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: heat (Ubuntu Kinetic)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

** Changed in: heat (Ubuntu Jammy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  [SRU] SwiftSignalHandle fails due to python2-3 decode error

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive yoga series:
  Triaged
Status in Ubuntu Cloud Archive zed series:
  Triaged
Status in heat package in Ubuntu:
  Fix Released
Status in heat source package in Jammy:
  Fix Committed
Status in heat source package in Kinetic:
  Fix Committed

Bug description:
  Storyboard link: https://storyboard.openstack.org/#!/story/2010485

  ============
  SRU TEMPLATE
  ============

  [Impact]

  The issue impact stack creation workflows where swift signals are
  used. There is no workaround for the issue other than not using swift
  signals. The fix is a conditional one-liner that performs a type-check
  before running the code change.

  [TestCase]

  1. Setting up env
  1a. Deploy an environment with ceph-rgw and heat
  1b. Make sure rgw-swift-versioning-enabled=true

  2. Reproducing the bug

  2a. Create a stack using the following template:

  ---
  heat_template_version: 2021-04-16

  resources:
    signal:
      type: OS::Heat::SwiftSignal
      properties:
        handle: {get_resource: signal_handle}
        timeout: 300

    signal_handle:
      type: OS::Heat::SwiftSignalHandle

    instance_port:
      type: OS::Neutron::Port
      properties:
        network: private
        fixed_ips:
          - subnet_id: private_subnet

    the_server:
      type: OS::Nova::Server
      properties:
        name: test
        image: cirros2
        flavor: m1.cirros
        networks:
          - port: { get_resource: instance_port }
        user_data_format: RAW
        user_data:
          str_replace:
            template: |
              #!/bin/sh

              # Simple success signal
              wc_notify --data-binary '{"status": "SUCCESS"}'
            params:
              wc_notify: { get_attr: [signal_handle, curl_cli] }

  2b. Use command "openstack stack create test -t template.yaml

  2c. Wait for stack creation to fail using command "openstack stack
  list"

  2d. Once failed, display the details using command "openstack stack
  show test"

  2e. Confirm error with the message:

  | stack_status_reason   | Resource CREATE failed: Error:
  resources.signal: Failed to parse JSON data: b'in progress'

  3. Cleanup not really needed

  4. Install package that contains the fixed code

  5. Confirming fix: Repeat steps 2a-2e and confirm stack creation is
  either successful or fails with a different message for another reason

  [Regression Potential]

  Since there is a type-check included in the fix, the regression
  potential is minimal, as if the condition is not fulfilled, then the
  original code is run.

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