GitHub user remibergsma opened a pull request:

    https://github.com/apache/cloudstack/pull/1402

    Check the existence of 'forceencap' parameter before use

    Check the existence of 'forceencap' parameter before use.
    
    Error seen:
    
    ```
    Traceback (most recent call last):
      File "/opt/cloud/bin/update_config.py", line 140, in <module>
        process_file()
      File "/opt/cloud/bin/update_config.py", line 54, in process_file
        finish_config()
      File "/opt/cloud/bin/update_config.py", line 44, in finish_config
        returncode = configure.main(sys.argv)
      File "/opt/cloud/bin/configure.py", line 1003, in main
        vpns.process()
      File "/opt/cloud/bin/configure.py", line 488, in process
        self.configure_ipsec(self.dbag[vpn])
      File "/opt/cloud/bin/configure.py", line 544, in configure_ipsec
        file.addeq(" forceencaps=%s" % CsHelper.bool_to_yn(obj['encap']))
    KeyError: 'encap'
    ```


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/remibergsma/cloudstack forceencap_check

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1402.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1402
    
----
commit 4ad05d1ade9d98e3a1bd268bcc1d7a0f0767d26d
Author: Remi Bergsma <git...@remi.nl>
Date:   2016-02-05T15:58:01Z

    Check the existence of 'forceencap' parameter before use

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to