group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1717615@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package python-heatclient - 1.8.0-0ubuntu3

---------------
python-heatclient (1.8.0-0ubuntu3) zesty; urgency=medium

  * d/p/dont-encode-path-separators.patch: Cherry-pick patch from upstream
    stable/pike branch to stop encoding of path separators as the are
    refused by Apache with 404s (LP: #1717615).

 -- Corey Bryant <corey.bryant@xxxxxxxxxxxxx>  Thu, 05 Oct 2017 13:56:03
-0400

** Changed in: python-heatclient (Ubuntu Zesty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1717615

Title:
  encoded slashes being blocked by Apache

Status in OpenStack heat charm:
  Invalid
Status in Charm Helpers:
  Invalid
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in OpenStack Heat:
  Invalid
Status in python-heatclient package in Ubuntu:
  Fix Released
Status in python-heatclient source package in Xenial:
  Fix Released
Status in python-heatclient source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  We came across a situation where we were unable to view resources in a stack inside Horizon. We traced it down to a communication problem with the Heat Apache frontend and Heat. After adjusting the log level for Apache, we came across the following error in the logs:

  [client 213.173.193.177:33920] AH00026: found %2f (encoded '/') in URI
  (decoded='/v1/c064a39d602d4f42bc49e09057c97683/stacks/heat_test_foo/b5c125a3-d452-49a1-
  a12e-03e098fbb38c/resources/foo_vm-01'), returning 404

  As a workaround, we currently added the following line to the
  /etc/apache/sites-enabled/openstack-https_frontend.conf on our Heat
  instance:

  AllowEncodedSlashes On

  It is worth noting we tried to use the NoDecode option as well and
  that is didn't resolve the problem.

  [Test Case]
  1. Deploy OpenStack with Juju
  2. Enable Keystone v3: juju config keystone preferred-api-version=3
  3. Enable SSL:         juju config keystone https-service-endpoints=True
  4. Add heat:
     - juju deploy heat
     - juju add-relation heat keystone
     - juju add-relation heat percona-cluster
     - juju add-relation heat rabbitmq-server
     - juju run-action heat/0 domain-setup
  5. Deploy a stack: 
      openstack stack create --parameter admin_pass=Ubuntu \
                             --parameter image=cirros-0.4.0 \
                             --parameter key_name=test \
                             --parameter network=network \
                             -t heat-basic.yaml heat_basic
  6. Verify that it deploys: openstack stack list
  7. Verify that heat works in OpenStack Dashboard
  8. Verify that displaying Heat resources tab in OpenStack Dashboard does
     NOT work.

  [Regression Potential]
  Low. The patch being backported is from the upstream stable/pike branch. There were some minor adjustments required to apply the patch to earlier releases, but the patches are nearly identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-heat/+bug/1717615/+subscriptions