[Bug 1826419] Re: dhcp agent configured with mismatching domain and host entries
Hoping someone with more history on the dns_domain/domain can chime in on this one. It's not clear to me if this is a bug or potentially a new RFE to change behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826419 Title: dhcp agent configured with mismatching domain and host entries To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1826419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)
Thanks for the comment. This area of the code is new to me, so I'm waiting for some neutron folks to come on-line that can help me triage this. Based on what I do know, I'm a little confused. How is neutron supposed to change the port.device_id in the clean node case so that it no longer has the ironic node id as the port.device_id? Is there a event/call from nova or other that's supposed to update it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state) To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1656010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)
Still looking into this... Based on the code I see, the port.device_id is used as the server_uuid in the notification which corresponds to the logs provided above. It's not yet clear to me why/how this should be different for this ironic case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state) To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1656010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066099] [NEW] python-gnutls - Segmentation fault running examples
Public bug reported: Running on Ubuntu 12.04 and I've installed the python-gnutls (1.2.0-2.1) package. As per the python-gnutls documentation, I should be able to run any of the examples which by default are installed with the package under: /usr/share/doc/python-gnutls/examples However all of the example produce a seg fault (core dumped)... For example: boden@be:/usr/share/doc/python-gnutls/examples$ python crypto.py Segmentation fault (core dumped) I've tried downloading the latest version of python-gnutls from the authors site (http://pypi.python.org/pypi/python-gnutls/), building them from scratch and running, but obtained the same result. A few more details: boden@be:/usr/share/doc/python-gnutls/examples$ gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. boden@be:/usr/share/doc/python-gnutls/examples$ python --version Python 2.7.3 ** Affects: python-gnutls (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/1066099 Title: python-gnutls - Segmentation fault running examples To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gnutls/+bug/1066099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
