[Bug 1793813] Re: magnum-api not working with www_authenticate_uri
This is affecting queens as well
ii magnum-api 6.1.0-0ubuntu1~cloud0
all OpenStack containers as a service
ii magnum-common6.1.0-0ubuntu1~cloud0
all OpenStack containers as a service - API server
ii magnum-conductor 6.1.0-0ubuntu1~cloud0
all OpenStack containers as a service - conductor
ii python-magnum6.1.0-0ubuntu1~cloud0
all OpenStack containers as a service - Python library
2018-10-22 09:17:38.029 4373 ERROR wsme.api
[req-eac33901-0e82-48aa-aa15-9e1a491ee393 - - - - -] Server-side error:
"'NoneType' object has no attribute 'replace'". Detail:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/wsmeext/pecan.py", line 84, in
callfunction
result = f(self, *args, **kwargs)
File
"/usr/lib/python2.7/dist-packages/magnum/api/controllers/v1/cluster_template.py",
line 306, in get_all
action='clustertemplate:get_all')
File "/usr/lib/python2.7/dist-packages/magnum/common/policy.py", line 100, in
enforce
add_policy_attributes(target)
File "/usr/lib/python2.7/dist-packages/magnum/common/policy.py", line 110, in
add_policy_attributes
trustee_domain_id = admin_osc.keystone().trustee_domain_id
File "/usr/lib/python2.7/dist-packages/magnum/common/keystone.py", line 179,
in trustee_domain_id
access = self.domain_admin_auth.get_access(
File "/usr/lib/python2.7/dist-packages/magnum/common/keystone.py", line 145,
in domain_admin_auth
auth_url=self.auth_url,
File "/usr/lib/python2.7/dist-packages/magnum/common/keystone.py", line 47,
in auth_url
return CONF[ksconf.CFG_LEGACY_GROUP].auth_uri.replace('v2.0', 'v3')
AttributeError: 'NoneType' object has no attribute 'replace'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793813
Title:
magnum-api not working with www_authenticate_uri
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1793813/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693122] Re: mongodb starts before network on VM and standalone
I thought this was the right place to fill the bug to have the source package fixed. Where should I report it to if not here? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693122 Title: mongodb starts before network on VM and standalone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1693122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693122] Re: mongodb starts before network on VM and standalone
I mean, it is a database service and 99% of the times can be, or it is used from the network. In the mongodb configuration mongodb.conf: ... #Net net.bindIp: 127.0.0.1,10.4.78.23 net.port: 27017 ... The db tries to start binding on the 10.4.78.23 ip, that is still not up because there is no hierarchy set up when mongodb starts. The default startup process in systemd is managed by the package and therefore this change is probably to be done by your side. MongoDB is a database server and therefore need to be accessible from the network. In my case, the mongodb database is used on three standalone VMs to support the monitoring of an Openstack installation. Can you please re-open? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693122 Title: mongodb starts before network on VM and standalone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1693122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693122] [NEW] mongodb starts before network on VM and standalone
Public bug reported: Hello Installed in a VM with only mongo running, the mongodb server service in systemd does not wait for network.target for starting up. This makes mongodb.service failing when the server restart, and when started by hand (after the network is restarted) works. Workaround: add the line: After=network.target in /lib/systemd/system/mongodb.service under the section [Unit] Impact: mongodb fails to start if server restarted. Reproducibility: on VMs, mongodb standalone node. ** Affects: mongodb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693122 Title: mongodb starts before network on VM and standalone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1693122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
