[Yahoo-eng-team] [Bug 1686015] [NEW] Add missing response examples for keystone OS-OAUTH1 API documentation
Public bug reported:
Add response examples to OS-OAUTH1 api documentation for the following API
(https://developer.openstack.org/api-ref/identity/v3-ext/index.html?expanded=#os-oauth1-api)
/v3/users/{user_id}/OS-OAUTH1/access_tokens/{access_token_id}/roles
/v3/users/{user_id}/OS-OAUTH1/access_tokens/{access_token_id}/roles/{role_id}
** Affects: keystone
Importance: Undecided
Assignee: Hemanth Nakkina (hemanth-n)
Status: New
** Changed in: keystone
Assignee: (unassigned) => Hemanth Nakkina (hemanth-n)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1686015
Title:
Add missing response examples for keystone OS-OAUTH1 API documentation
Status in OpenStack Identity (keystone):
New
Bug description:
Add response examples to OS-OAUTH1 api documentation for the following API
(https://developer.openstack.org/api-ref/identity/v3-ext/index.html?expanded=#os-oauth1-api)
/v3/users/{user_id}/OS-OAUTH1/access_tokens/{access_token_id}/roles
/v3/users/{user_id}/OS-OAUTH1/access_tokens/{access_token_id}/roles/{role_id}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1686015/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1674889] Re: Fix get_schema_helper bug in some case
** Changed in: networking-ovn Status: Fix Committed => Fix Released ** Changed in: neutron Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1674889 Title: Fix get_schema_helper bug in some case Status in networking-ovn: Fix Released Status in neutron: Fix Released Status in ovsdbapp: Invalid Bug description: When thread of ovn ovsdb-server is not present, then start or restart neutron-server, manager was set to openvswitch. Neutron-server can no longer connect to ovn ovsdb for occupied port 6642 unless delete manager manually. Manager "ptcp:6642:10.157.0.159" Bridge br-int fail_mode: secure This is not a bug that always exists, it's caused by some neutron recent modification. I will port idlutils.get_schema_helper from ovsdbapp to neutron, and in networking-ovn, will pass try_add_manager=False I also submitted a bug[1] in neutron a few days ago, now it is merged into this one. [1] https://bugs.launchpad.net/neutron/+bug/1672590 To manage notifications about this bug go to: https://bugs.launchpad.net/networking-ovn/+bug/1674889/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1526212] Re: [api-ref]Need to write "add dhcp agent to network" on Networking API
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1526212 Title: [api-ref]Need to write "add dhcp agent to network" on Networking API Status in neutron: Expired Bug description: Neutron supports "add dhcp agent to network" on Networking API, and tempest also is testing the API. However, the api-site doesn't contain the API description. So we need to write the API for API users. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1526212/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685977] [NEW] api-ref: wrong description for 'flavorRef' parameter in Create Server API
Public bug reported: https://developer.openstack.org/api-ref/compute/?expanded=create-server- detail#create-server In " Create Server" API, 'flavorRef' parameter is defined as follows: > The flavor reference, as a UUID or full URL, for the flavor for your server instance. But The flavor ID can be specified as not only a UUID but only any string or integer. So the description should be fixed. ** Affects: nova Importance: Undecided Assignee: Takashi NATSUME (natsume-takashi) Status: New ** Tags: doc -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1685977 Title: api-ref: wrong description for 'flavorRef' parameter in Create Server API Status in OpenStack Compute (nova): New Bug description: https://developer.openstack.org/api-ref/compute/?expanded=create- server-detail#create-server In " Create Server" API, 'flavorRef' parameter is defined as follows: > The flavor reference, as a UUID or full URL, for the flavor for your server instance. But The flavor ID can be specified as not only a UUID but only any string or integer. So the description should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1685977/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1671911] Re: Modified project information and members but unable to modify project quotas when modifying volume quota in horizon admin identity view
Reviewed: https://review.openstack.org/451679
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=3055a987632c29175c06d73e77fbad9062fcc2c4
Submitter: Jenkins
Branch:master
commit 3055a987632c29175c06d73e77fbad9062fcc2c4
Author: Radomir Dopieralski
Date: Thu Mar 30 09:17:35 2017 +0200
Don't update cinder quotas if disabled
The quotas for cinder were being updated even if they were disabled,
resulting in None being sent as the value, and an error being thrown
by the API.
This patch cleans up that code to use the same logic in all three cases
for nova, cinder and neutron.
Change-Id: I73209122df20689eee33da9dccffa994a04a3ec0
Closes-bug: #1671911
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1671911
Title:
Modified project information and members but unable to modify project
quotas when modifying volume quota in horizon admin identity view
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Description of problem:
Modified project information and members but unable to modify project quotas
when modifying volume quota in horizon admin identity view
Go to Identity -> Identity -> Projects, modify the quotas of a project
and set volumes to another value.
Spot check shows that:
- vCPUs and instances **do** update, but the error message still shows
- volumes do **not** update
Version-Release number of selected component (if applicable):
[root@overcloud-controller-0 ~]# rpm -qf
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/identity/projects/workflows.py
openstack-dashboard-10.0.1-5.el7ost.noarch
Actual results:
volumes quotas do not update, error message shows
Expected results:
update volume quotas, no error message
Additional info:
The problem in the code with integer / string conversion:
~~~
==> /var/log/cinder/api.log <==
2017-03-09 17:55:41.871 103796 DEBUG eventlet.wsgi.server [-] (103796)
accepted ('172.16.2.4', 45808) server
/usr/lib/python2.7/site-packages/eventlet/wsgi.py:867
2017-03-09 17:55:41.878 103796 INFO cinder.api.openstack.wsgi
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a
d809ec86f152486981e1782e94fa7b2d - default default] PUT
http://10.0.0.4:8776/v2/d809ec86f152486981e1782e94fa7b2d/os-quota-sets/d809ec86f152486981e1782e94fa7b2d
2017-03-09 17:55:41.879 103796 DEBUG cinder.api.openstack.wsgi
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a
d809ec86f152486981e1782e94fa7b2d - default default] Action: 'update', calling
method: >, body:
{"quota_set": {"gigabytes": null, "tenant_id":
"d809ec86f152486981e1782e94fa7b2d", "volumes": 21, "snapshots": null}}
_process_stack /usr/lib/python2.7/site-packages/cinder/api/openstack/wsgi.py:868
2017-03-09 17:55:41.977 103796 INFO cinder.api.openstack.wsgi
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a
d809ec86f152486981e1782e94fa7b2d - default default] HTTP exception thrown:
gigabytes must be an integer.
2017-03-09 17:55:41.978 103796 INFO cinder.api.openstack.wsgi
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a
d809ec86f152486981e1782e94fa7b2d - default default]
http://10.0.0.4:8776/v2/d809ec86f152486981e1782e94fa7b2d/os-quota-sets/d809ec86f152486981e1782e94fa7b2d
returned with HTTP 400
2017-03-09 17:55:41.980 103796 INFO eventlet.wsgi.server
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a
d809ec86f152486981e1782e94fa7b2d - default default] 172.16.2.4 "PUT
/v2/d809ec86f152486981e1782e94fa7b2d/os-quota-sets/d809ec86f152486981e1782e94fa7b2d
HTTP/1.1" status: 400 len: 335 time: 0.1074338
~~~
When saving the quotas from the web interface, the following happens:
~~~
POST /dashboard/identity/53f4466c084145e0b91296f68be517a6/update/ HTTP/1.1
Host: 10.0.0.4
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:51.0) Gecko/20100101
Firefox/51.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-Requested-With: XMLHttpRequest
Referer: http://10.0.0.4/dashboard/identity/
Content-Length: 1616
Cookie: login_region="http://172.16.2.10:5000/v2.0";; login_domain=;
SERVERID=overcloud-controller-0; csrftoken=8DM2AJOQIfjEN9rHBic3BzZrxoPYvnnP;
sessionid=wk7y07jc7938xe6zu0ushg3micrq3aus
Connection: keep-alive
csrfmiddlewaretoken=8DM2AJOQIfjEN9rHBic3BzZrxoPYvnnP&domain_id=default&domain_name=Default&name=service&description=Tenant+for+the+openstack+services&enabled=on&available_update_members_filter=&update_members_members_filter=&default_update_members_role=9fe2ff9ee4384b1894a90878d3e92bab&update_members_role_64f3a3e25453466cac4
[Yahoo-eng-team] [Bug 1680810] Re: Error if admin logs in when identity dashboard is not registered.
Reviewed: https://review.openstack.org/454671 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=87b2a0544a19e81bd1351fc77d54295132dda8f9 Submitter: Jenkins Branch:master commit 87b2a0544a19e81bd1351fc77d54295132dda8f9 Author: Dale Smith Date: Fri Apr 7 11:47:13 2017 +0100 Fix regression when identity panel is not registered. When the admin user logs in and the identity dashboard is not registered we should simply get the default dashboard instead. This fixes a regression introduced in I27300e928855ec10ca5d2a623d636e50d756b698 Closes-Bug: #1680810 Change-Id: I9199d2f5a61925fb86763b0f80152d260906991e ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1680810 Title: Error if admin logs in when identity dashboard is not registered. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: If the identity dashboard is not registered in Horizon and an admin user logs in they will get a 'Something went wrong' page and are not able to progress further. Relevant logs: http://paste.openstack.org/raw/605730/ The issue appears to have been introduced when fixing https://bugs.launchpad.net/horizon/+bug/1659818 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1680810/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1588071] Re: IPv6 filter action should be hidden if OPENSTACK_NEUTRON_NETWORK.enable_ipv6 is set to False
Reviewed: https://review.openstack.org/335159 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=ff42a42c3de6ca98484bd430f4639a98a515d211 Submitter: Jenkins Branch:master commit ff42a42c3de6ca98484bd430f4639a98a515d211 Author: Eddie Ramirez Date: Wed Jun 22 16:55:05 2016 + Hide IPv6 filter choice if enable_ipv6 is set to False This patch hides filter choice IPv6 under Project->Instances and Admin->Instances if OPENSTACK_NEUTRON_NETWORK.enable_ipv6 is set to False Closes-bug: #1588071 Change-Id: Ibdccb94c2cbc07a8dbbe02f72ca7c8b6a36360f7 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1588071 Title: IPv6 filter action should be hidden if OPENSTACK_NEUTRON_NETWORK.enable_ipv6 is set to False Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In the Admin > Instances panel, one of the filter options is "IPv6 Address =". By overriding the init function, we can hide this option based on the value of OPENSTACK_NEUTRON_NETWORK.enable_ipv6 in local_settings. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1588071/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1683262] Re: workflow step does not support allowed()
Reviewed: https://review.openstack.org/457177 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=fd55569ab0a087e5518e235c770ae86244257baf Submitter: Jenkins Branch:master commit fd55569ab0a087e5518e235c770ae86244257baf Author: Akihiro Motoki Date: Mon Apr 17 08:09:31 2017 + Support allowed() in workflows.Step There are cases where we want to display workflow Step conditionally. Change-Id: I71ae3ed270d9472190430ac5b4a34682ce3b3f29 Closes-Bug: #1683262 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1683262 Title: workflow step does not support allowed() Status in OpenStack Dashboard (Horizon): Fix Released Bug description: allowed() method is a common way in horizon to control if a component can be displayed. It is supported in table action and tab, but it is not supported for workflows.Step. There is a case where a step wants to be shown conditionally. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1683262/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685939] [NEW] Speed up yaml parsing using libYAML C-bindings
Public bug reported: We can speed up cloud init yaml loading and parsing by using the C-bindings instead of python bindings. ** Affects: cloud-init Importance: Undecided Assignee: Chad Smith (chad.smith) Status: In Progress ** Tags: bitesize ** Tags added: bitesize ** Changed in: cloud-init Assignee: (unassigned) => Chad Smith (chad.smith) ** Changed in: cloud-init Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1685939 Title: Speed up yaml parsing using libYAML C-bindings Status in cloud-init: In Progress Bug description: We can speed up cloud init yaml loading and parsing by using the C-bindings instead of python bindings. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1685939/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685935] [NEW] make deb breaks due to missing debuild script
Public bug reported: On a newly installed lxc, I cannot make deb easily because of missing dependencies. ... restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'debuild' We should probably aid this process a bit for new developers trying to package their own deb. ** Affects: cloud-init Importance: Undecided Assignee: Chad Smith (chad.smith) Status: In Progress ** Tags: bitesize ** Changed in: cloud-init Status: New => In Progress ** Changed in: cloud-init Assignee: (unassigned) => Chad Smith (chad.smith) ** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/323076 ** Tags added: bitesize -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1685935 Title: make deb breaks due to missing debuild script Status in cloud-init: In Progress Bug description: On a newly installed lxc, I cannot make deb easily because of missing dependencies. ... restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'debuild' We should probably aid this process a bit for new developers trying to package their own deb. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1685935/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685930] [NEW] model query hooks cleanup breaks UTs
Public bug reported: The change Ib6c2134d29e1764de627c3355f6cdee789d6301e in neutron cleans up model query hooks registered after each tests is run. This cleanup has been added in tests/base.py In net-bgpvpn, some features rely on those hooks, and UTs for those features are now broken, as we can see in : http://logs.openstack.org/01/458101/2/check/gate-networking-bgpvpn- python27-ubuntu-xenial/24a6b18/testr_results.html.gz It appears that if a failing UT is run alone, it passes. However, if the entire test module is run, then it breaks. for instance, the test test_db_list_bgpvpn_filtering_associated_resources passes if it is run alone, but it fails when it is run after other tests in the same module, with the following command : $ ostestr networking_bgpvpn.tests.unit.db.test_db.BgpvpnDBTestCase by removing the cleanup line, as proposed in https://review.openstack.org/#/c/459400/ , all UTs are passing in net- bgpvpn ** Affects: bgpvpn Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1685930 Title: model query hooks cleanup breaks UTs Status in networking-bgpvpn: New Status in neutron: New Bug description: The change Ib6c2134d29e1764de627c3355f6cdee789d6301e in neutron cleans up model query hooks registered after each tests is run. This cleanup has been added in tests/base.py In net-bgpvpn, some features rely on those hooks, and UTs for those features are now broken, as we can see in : http://logs.openstack.org/01/458101/2/check/gate-networking-bgpvpn- python27-ubuntu-xenial/24a6b18/testr_results.html.gz It appears that if a failing UT is run alone, it passes. However, if the entire test module is run, then it breaks. for instance, the test test_db_list_bgpvpn_filtering_associated_resources passes if it is run alone, but it fails when it is run after other tests in the same module, with the following command : $ ostestr networking_bgpvpn.tests.unit.db.test_db.BgpvpnDBTestCase by removing the cleanup line, as proposed in https://review.openstack.org/#/c/459400/ , all UTs are passing in net- bgpvpn To manage notifications about this bug go to: https://bugs.launchpad.net/bgpvpn/+bug/1685930/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685881] Re: l3-agent-router-add doesn't error/warn about router already existing on agent
Adding neutron as it doesn't appear that this is charm related. The error command that should error/warn is from the neutron cli itself. ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1685881 Title: l3-agent-router-add doesn't error/warn about router already existing on agent Status in OpenStack neutron-api charm: New Status in neutron: New Bug description: we had an incident on a network that ended up with random packet dropping between nodes within the cloud, and outside of cloud when crossing l3-routers. Steps to reproduce: juju set neutron-api min-agents-per-router=2 juju set neutron-api max-agents-per-router=2 juju set neutron-api l2-population=false juju set neutron-api enable-l3ha=true for i in $(neutron router-list -f value -c id); do neutron router-update $i --admin-state=up=false neutron router-update $i --ha=true neutron router-update $i --admin-state=up=true done juju set neutron-api max-agents-per-router=3 neutron for i in $(neutron router-list -f value -c id); do neutron l3-agent-list-hosting-router $i for j in $(neutron agent-list -f value -c id); do neutron l3-agent-router-add $j $i done done sleep 120 #for settle for i in $(neutron router-list -f value -c id); do neutron l3-agent-list-hosting-router $i done Potentially you may see two active l3-agents for a given router. (We saw this corresponded to rabbitmq messaging failures concurrent with this activity). Our environment had 9 active routers. You'll notice that there's no error that comes out of adding a router to an agent it's already running on. After making these updates, we found that ssh and RDP sessions to the floating IPs associated with VMs across several different networks/routers were exhibiting random session drops as if the route were hosted in multiple locations and we were getting an asymmetric route issue. We had to revert to --ha=false and enable-l3ha=false before we could gather deeper info/SOS reports. May be able to reproduce in lab at some point in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-api/+bug/1685881/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1672670] Re: Unit tests fail with current os-brick master
Yeah the os-brick method is returning a 2-item tuple now instead of a list. That's fine since it's an internal method to os-brick, and the unit test in nova should be moved to os-brick (it's legacy code from when nova was changed to use os-brick for the libvirt driver, not all of the unit tests were moved over). In fact, there is even a todo in the test code to move it to os-brick. ** Changed in: os-brick Status: New => Invalid ** Changed in: nova Status: New => Triaged ** Changed in: nova Assignee: (unassigned) => Matt Riedemann (mriedem) ** Changed in: nova Importance: Undecided => High ** Changed in: os-brick Status: Invalid => New ** Changed in: os-brick Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1672670 Title: Unit tests fail with current os-brick master Status in OpenStack Compute (nova): In Progress Status in os-brick: Invalid Bug description: When running Nova unit tests using the current os-brick from master, nova.tests.unit.virt.libvirt.volume.test_iscsi.LibvirtISCSIVolumeDriverTestCase.test_iscsiadm_discover_parsing fails . How to reproduce: 1- setup virtualenv with Nova test-requirements 2- pip install --upgrade git+https://github.com/openstack/os-brick 3- ostestr -r nova.tests.unit.virt.libvirt.volume.test_iscsi.LibvirtISCSIVolumeDriverTestCase.test_iscsiadm_discover_parsing Got the following traceback: nova.tests.unit.virt.libvirt.volume.test_iscsi.LibvirtISCSIVolumeDriverTestCase.test_iscsiadm_discover_parsing -- Captured traceback: ~~~ Traceback (most recent call last): File "nova/tests/unit/virt/libvirt/volume/test_iscsi.py", line 47, in test_iscsiadm_discover_parsing self.assertEqual(targets, out) File "/tmp/venv/lib/python2.7/site-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/tmp/venv/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = [['192.168.204.82:3260,1', 'iqn.2010-10.org.openstack:volume-f9b12623-6ce3-4dac-a71f-09ad4249bdd3'], ['192.168.204.82:3261,1', 'iqn.2010-10.org.openstack:volume-f9b12623-6ce3-4dac-a71f-09ad4249bdd4']] actual= (['192.168.204.82:3260,1', '192.168.204.82:3261,1'], ['iqn.2010-10.org.openstack:volume-f9b12623-6ce3-4dac-a71f-09ad4249bdd3', 'iqn.2010-10.org.openstack:volume-f9b12623-6ce3-4dac-a71f-09ad4249bdd4']) https://review.openstack.org/433104 looks like the most probable cause. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1672670/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685875] [NEW] Swapping encrypted volumes leaves an encrypted volume attached to the instance
Public bug reported: Description === Swapping encrypted volumes via `nova volume-update` currently results in the new volume being attached to the instance still encrypted and the original volume still connected to the host. Steps to reproduce == # cinder type-create LUKS # cinder encryption-type-create --cipher aes-xts-plain64 \ --key_size 512 --control_location front-end LUKS \ nova.volume.encryptors.luks.LuksEncryptor # cinder create --volume-type LUKS 1 # cinder create --volume-type LUKS 1 # nova boot --image cirros-0.3.5-x86_64-disk --flavor 2 test # nova volume-attach 445a811f-ca80-49d3-b3bd-156cb492c96c \ d7c43bc8-dbc4-4668-950a-a57397af7cbf # nova volume-update 445a811f-ca80-49d3-b3bd-156cb492c96c \ d7c43bc8-dbc4-4668-950a-a57397af7cbf \ f998a062-8227-41b4-8400-d82a0f223ec3 Expected result === The original volume is disconnected from the host, the new volume is decrypted and attached to the instance. Actual result = f998a062, the new volume is now attached to the instance but without being decrypted : $ sudo virsh domblklist 445a811f-ca80-49d3-b3bd-156cb492c96c Target Source vda /opt/stack/data/nova/instances/445a811f-ca80-49d3-b3bd-156cb492c96c/disk vdb /dev/disk/by-path/ip-192.168.122.224:3260-iscsi-iqn.2010-10.org.openstack:volume-f998a062-8227-41b4-8400-d82a0f223ec3-lun-1 d7c43bc8, the original volumes is still connected and decrypted on the host : $ iscsiadm -m session tcp: [5] 192.168.122.224:3260,1 iqn.2010-10.org.openstack:volume-d7c43bc8-dbc4-4668-950a-a57397af7cbf (non-flash) tcp: [6] 192.168.122.224:3260,1 iqn.2010-10.org.openstack:volume-f998a062-8227-41b4-8400-d82a0f223ec3 (non-flash) $ ll /dev/disk/by-path/ip-192.168.122.224\:3260-iscsi-iqn.2010-10.org.openstack\:volume-d7c43bc8-dbc4-4668-950a-a57397af7cbf-lun-1 lrwxrwxrwx. 1 root root 123 Apr 24 12:39 /dev/disk/by-path/ip-192.168.122.224:3260-iscsi-iqn.2010-10.org.openstack:volume-d7c43bc8-dbc4-4668-950a-a57397af7cbf-lun-1 -> /dev/mapper/crypt-ip-192.168.122.224:3260-iscsi-iqn.2010-10.org.openstack:volume-d7c43bc8-dbc4-4668-950a-a57397af7cbf-lun-1 $ ll /dev/mapper/crypt* lrwxrwxrwx. 1 root root 7 Apr 24 12:40 /dev/mapper/crypt-ip-192.168.122.224:3260-iscsi-iqn.2010-10.org.openstack:volume-d7c43bc8-dbc4-4668-950a-a57397af7cbf-lun-1 -> ../dm-2 Environment === 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ $ git rev-parse HEAD 0039231719d2a02c59e7cd76631e2ff03cc86b0d 2. Which hypervisor did you use? (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...) What's the version of that? Libvirt + KVM 2. Which storage type did you use? (For example: Ceph, LVM, GPFS, ...) What's the version of that? LVM/iSCSI 3. Which networking type did you use? (For example: nova-network, Neutron with OpenVSwitch, ...) N/A Logs & Configs == n-cpu.log 2017-04-24 12:41:00.740 ERROR nova.compute.manager [req-95448809-bf98-4468-82cf-f4681678a8a4 admin admin] [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] Failed to swap volume d7c43bc 8-dbc4-4668-950a-a57397af7cbf for f998a062-8227-41b4-8400-d82a0f223ec3 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] Traceback (most recent call last): 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] File "/opt/stack/nova/nova/compute/manager.py", line 4936, in _swap_volume 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] resize_to) 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 1328, in swap_volume 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] self._disconnect_volume(old_connection_info, disk_dev) 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 1176, in _disconnect_volume 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] vol_driver.disconnect_volume(connection_info, disk_dev) 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c] File "/opt/stack/nova/nova/virt/libvirt/volume/iscsi.py", line 74, in disconnect_volume 2017-04-24 12:41:00.740 TRACE nova.compute.manager [instance: 445a811f-ca80-49d3-b3bd-156cb492c96c]
[Yahoo-eng-team] [Bug 1683542] Re: After configuing Ubuntu Core system still displays subiquity wizard
** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Milestone: None => 2.2.0rc3 ** Changed in: maas Importance: Undecided => Wishlist ** Changed in: maas Status: New => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1683542 Title: After configuing Ubuntu Core system still displays subiquity wizard Status in cloud-init: Won't Fix Status in MAAS: Triaged Bug description: After deploying Ubuntu-Core using MAAS the console-conf wizard still runs on the deployed system. With it a person with physical/console access can change networking configuration and add a user which has sudo access. When cloud-init runs and creates a user console-conf should be disabled as cloud-init has already created a user. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1683542/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685831] [NEW] pylint: cloudinit.util 'closing' has no 'read' member
Public bug reported: Tip style checker [1] discovered the following errors, but I believe this is a false positive: * Module cloudinit.util cloudinit/util.py:480: [E1101(no-member), decomp_gzip] Instance of 'closing' has no 'read' member cloudinit/util.py:482: [E1101(no-member), decomp_gzip] Instance of 'closing' has no 'read' member Offending code [2] and upstream bug filed [3] [1] https://paste.ubuntu.com/24448453/ [2] https://paste.ubuntu.com/24448487/ [3] https://github.com/PyCQA/pylint/issues/1444 ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1685831 Title: pylint: cloudinit.util 'closing' has no 'read' member Status in cloud-init: New Bug description: Tip style checker [1] discovered the following errors, but I believe this is a false positive: * Module cloudinit.util cloudinit/util.py:480: [E1101(no-member), decomp_gzip] Instance of 'closing' has no 'read' member cloudinit/util.py:482: [E1101(no-member), decomp_gzip] Instance of 'closing' has no 'read' member Offending code [2] and upstream bug filed [3] [1] https://paste.ubuntu.com/24448453/ [2] https://paste.ubuntu.com/24448487/ [3] https://github.com/PyCQA/pylint/issues/1444 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1685831/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685822] [NEW] AttributeError in Edit Extra Spec form.
Public bug reported: Env: devstack master branch Steps to reproduce: 1. Go to admin/volume Volume Types panel 2. Volume Types -> Click View Extra Specs -> Click Edit 3. Remove the 'Value' value (which is a required field). On form submit Error info: Internal Server Error: /admin/volume_types/b780ccbf-b45d-4b80-ac6d-d5e84eb993cc/extras/volume_backend_name/edit/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 52, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 84, in dec return view_func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/edit.py", line 217, in post return self.form_invalid(form) File "/opt/stack/horizon/openstack_dashboard/dashboards/admin/volume_types/extras/views.py", line 125, in form_invalid context = self._populate_context(context) AttributeError: 'EditView' object has no attribute '_populate_context' [24/Apr/2017 15:26:58] "POST /admin/volume_types/b780ccbf-b45d-4b80-ac6d-d5e84eb993cc/extras/volume_backend_name/edit/ HTTP/1.1" 500 142967 ** Affects: horizon Importance: Undecided Assignee: wei.ying (wei.yy) Status: New ** Changed in: horizon Assignee: (unassigned) => wei.ying (wei.yy) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1685822 Title: AttributeError in Edit Extra Spec form. Status in OpenStack Dashboard (Horizon): New Bug description: Env: devstack master branch Steps to reproduce: 1. Go to admin/volume Volume Types panel 2. Volume Types -> Click View Extra Specs -> Click Edit 3. Remove the 'Value' value (which is a required field). On form submit Error info: Internal Server Error: /admin/volume_types/b780ccbf-b45d-4b80-ac6d-d5e84eb993cc/extras/volume_backend_name/edit/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 52, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 84, in dec return view_func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/edit.py", line 217, in post return self.form_invalid(form) File "/opt/stack/horizon/openstack_dashboard/dashboards/admin/volume_types/extras/views.py", line 125, in form_invalid context = self._populate_context(context) AttributeError: 'EditView' object has no attribute '_populate_context' [24/Apr/2017 15:26:58] "POST /admin/volume_types/b780ccbf-b45d-4b80-ac6d-d5e84eb993cc/extras/volume_backend_name/edit/ HTTP/1.1" 500 142967 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1685822/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685810] [NEW] nova-lxd needs to read 'product_name' in environment, not 'platform'
Public bug reported: It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs: * bug 1661797: identify lxd-nova platform to enable Openstack datasource ** Affects: cloud-init Importance: High Assignee: Scott Moser (smoser) Status: Confirmed ** Tags: dsid ** Description changed: It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable + While: + $ sudo cat /proc/1/environ | tr '\0' '\n' + product_name=OpenStack Nova + container=lxc + Related bugs: - * bug 1661797: identify lxd-nova platform to enable Openstack datasource + * bug 1661797: identify lxd-nova platform to enable Openstack datasource -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1685810 Title: nova-lxd needs to read 'product_name' in environment, not 'platform' Status in cloud-init: Confirmed Bug description: It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs: * bug 1661797: identify lxd-nova platform to enable Openstack datasource To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1685810/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685664] Re: Block Device Mapping is Invalid (add/attache lvm volume)
Appears you are just missing the tgtadm utility on the node running cinder-volume : Apr 22 14:31:42 storage cinder-volume: 2017-04-22 14:31:42.284 50710 ERROR oslo_messaging.rpc.server Stderr: u'/usr/bin/cinder-rootwrap: Executable not found: tgtadm (filter match = tgtadm)\n' ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1685664 Title: Block Device Mapping is Invalid (add/attache lvm volume) Status in OpenStack Compute (nova): Invalid Bug description: Description === Hi, I am setting up multi node environment (controller, Nova, nuetron and cinder). For now, I am able to create the blank Server and when I try to add or attach volume ( from cinder - volume from volume group) it fails. Without volume I am able to launch machine. Steps to reproduce == 1. Setup environment as Description area briefed 2. Try to build new instance In this I don't know why it triggers tgtadm whereas I configured lvm as cinder. sudo cinder-rootwrap /etc/cinder/rootwrap.conf tgtadm --lld iscsi --op show --mode target execute /usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py:344 Apr 22 14:31:42 storage cinder-volume: 2017-04-22 14:31:42.282 50710 DEBUG oslo_concurrency.processutils [req-70d6c927-9969-4dfb-b27e-94b7c95ed816 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - default default] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf tgtadm --lld iscsi --op show --mode target" returned: 96 in 0.096s execute /usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py:374 Error is below from logs: Failed to perform requested operation on instance "", the instance has an error status: Please try again later [Error: Build of instance aborted: Block Device Mapping is Invalid.]. Nova Compute Logs: 2017-04-22 14:31:48.517 14044 DEBUG nova.compute.claims [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] [instance: 79f65f4e-365c-45f7-808b-e9966de61681] Aborting claim: [Claim: 2048 MB memory, 20 GB disk] abort /usr/lib/python2.7/site-packages/nova/compute/claims.py:123 2017-04-22 14:31:48.517 14044 DEBUG oslo_concurrency.lockutils [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] Lock "compute_resources" acquired by "nova.compute.resource_tracker.abort_instance_claim" :: waited 0.000s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:270 2017-04-22 14:31:48.521 14044 DEBUG oslo_messaging._drivers.amqpdriver [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] CALL msg_id: 97be26cf170c4df48cefab8812b7acbd exchange 'nova' topic 'conductor' _send /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:448 2017-04-22 14:31:48.594 14044 DEBUG oslo_messaging._drivers.amqpdriver [-] received reply msg_id: 97be26cf170c4df48cefab8812b7acbd __call__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:296 2017-04-22 14:31:48.598 14044 DEBUG oslo_messaging._drivers.amqpdriver [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] CALL msg_id: 3c68a6ad11b44754be89faab6f65c98b exchange 'nova' topic 'conductor' _send /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:448 2017-04-22 14:31:48.617 14044 DEBUG oslo_messaging._drivers.amqpdriver [-] received reply msg_id: 3c68a6ad11b44754be89faab6f65c98b __call__ /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:296 2017-04-22 14:31:48.618 14044 DEBUG oslo_concurrency.lockutils [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] Lock "compute_resources" released by "nova.compute.resource_tracker.abort_instance_claim" :: held 0.101s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:282 2017-04-22 14:31:48.619 14044 DEBUG nova.compute.manager [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] [instance: 79f65f4e-365c-45f7-808b-e9966de61681] Build of instance 79f65f4e-365c-45f7-808b-e9966de61681 aborted: Block Device Mapping is Invalid. _build_and_run_instance /usr/lib/python2.7/site-packages/nova/compute/manager.py:1937 2017-04-22 14:31:48.619 14044 WARNING nova.image.glance [req-a1d191d7-d426-4f25-82ef-bf92663f3d18 dc27f505a62c4181a0d03382fb99d744 67d52715de2244b1b32c9a34c914572d - - -] No protocol specified in for api_server 'http://10.0.1.80:9292', please update [glance] api_servers with fully qualified url including sc
[Yahoo-eng-team] [Bug 1685773] [NEW] Delete instance popup shows "." as selected instance name
Public bug reported: When deleting an instance from the detail page for that instance, the popup says "You have selected: . Please confirm your selection. Deleted instances are not recoverable." Same behaviour for stable/ocata and current master. Expected behaviour: Show the name of the instance that is to be deleted. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1685773 Title: Delete instance popup shows "." as selected instance name Status in OpenStack Dashboard (Horizon): New Bug description: When deleting an instance from the detail page for that instance, the popup says "You have selected: . Please confirm your selection. Deleted instances are not recoverable." Same behaviour for stable/ocata and current master. Expected behaviour: Show the name of the instance that is to be deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1685773/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1685764] [NEW] neutron filters of OpenContrail not work
Public bug reported:
OpenStack : Liberty
OpenContrail:3.0.3
I use this cmd to want to filter the subnet I want ,but it seems just
work with the condition of network_id
curl -i -k -v -H "X-Auth-Token:1c3dd3b51c6c48a4830cbdbb2e6b3116"
http://189.43.133.201:9696/v2.0/subnets?network_id=6abaaf14-d0b5-4f4a-a436-7b728ab66c69\&cidr=2001:db2::/48\&enable_dhcp=true\&gateway_ip=null
The response is
{"subnets": [{"name": "", "enable_dhcp": true, "network_id":
"6abaaf14-d0b5-4f4a-a436-7b728ab66c69", "tenant_id":
"c5fadfacec6148eb81a6fd1585763dde", "dns_nameservers": [],
"ipv6_ra_mode": null, "allocation_pools": [{"start": "182.16.0.10",
"end": "182.16.0.100"}], "gateway_ip": "182.16.0.254",
"ipv6_address_mode": null, "ip_version": 4, "host_routes": [], "cidr":
"182.16.0.0/16", "id": "74bdee0a-1e09-4d74-97ac-7d48faada404"}, {"name":
"test", "enable_dhcp": true, "network_id":
"6abaaf14-d0b5-4f4a-a436-7b728ab66c69", "tenant_id":
"c5fadfacec6148eb81a6fd1585763dde", "dns_nameservers": [],
"ipv6_ra_mode": null, "allocation_pools": [{"start": "2001:db2::2",
"end": "2001:db2:0:::::fffe"}], "gateway_ip":
"2001:db2::1", "ipv6_address_mode": null, "ip_version": 6,
"host_routes": [], "cidr": "2001:db2::/48", "id":
"5840f97e-8574-4841-bca2-2ed492c0b124"}]}
Just the condition of network_id seems work and reported me two subnets
of the network.
The log on neutron is
2017-04-24 17:30:57.482 650 DEBUG keystoneclient.session [-] REQ: curl -g -i -X
GET http://189.43.133.172:35357/v3/auth/tokens -H "X-Subject-Token:
{SHA1}ac10054fc4ef440481adecddfc2556ac163cd6a0" -H "User-Agent:
python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token:
{SHA1}7782e1f4c7813c70198660e1b26cff3092dd3f5e" _http_log_request
/usr/lib/python2.7/dist-packages/keystoneclient/session.py:198
2017-04-24 17:30:57.549 650 DEBUG keystoneclient.session [-] RESP: [200]
Content-Length: 4236 X-Subject-Token:
{SHA1}ac10054fc4ef440481adecddfc2556ac163cd6a0 Vary: X-Auth-Token Keep-Alive:
timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: Keep-Alive Date:
Mon, 24 Apr 2017 17:30:57 GMT x-openstack-request-id:
req-7d41df19-f0ce-464d-b349-0da7e480d1a7 Content-Type: application/json
X-Distribution: Ubuntu
RESP BODY: {"token": {"methods": ["password", "token"], "roles": [{"id":
"9fe2ff9ee4384b1894a90878d3e92bab", "name": "_member_"}, {"id":
"5cd4cb4a977f4c348621996e8ba7daa0", "name": "admin"}, {"id":
"25acf9ff434f44d2a1a320cb1918d5c2", "name": "Member"}], "expires_at":
"2017-04-24T18:28:32.00Z", "project": {"domain": {"id": "default", "name":
"Default"}, "id": "c5fadfacec6148eb81a6fd1585763dde", "name": "CloudEdge"},
"catalog": "", "extras": {}, "user": {"domain": {"id": "default",
"name": "Default"}, "id": "7496e29fc1c141a081301bd9484f59c3", "name":
"CloudEdge"}, "audit_ids": ["GTVlubKPR7qQYbZqkYOnjg"], "issued_at":
"2017-04-24T17:28:32.963663"}}
_http_log_response
/usr/lib/python2.7/dist-packages/keystoneclient/session.py:215
2017-04-24 17:30:57.678 650 DEBUG
neutron_plugin_contrail.plugins.opencontrail.contrail_plugin
[req-7104ac89-1938-4856-9916-0a4999ab96b1 7496e29fc1c141a081301bd9484f59c3
c5fadfacec6148eb81a6fd1585763dde - - -] get_subnet(): filters: {u'network_id':
[u'6abaaf14-d0b5-4f4a-a436-7b728ab66c69'], u'cidr': [u'2001:db2::/48'],
u'gateway_ip': [u'null'], u'enable_dhcp': [True]} data: [{u'name': u'',
u'enable_dhcp': True, u'network_id': u'6abaaf14-d0b5-4f4a-a436-7b728ab66c69',
u'tenant_id': u'c5fadfacec6148eb81a6fd1585763dde', u'dns_nameservers': [],
u'gateway_ip': u'182.16.0.254', u'ipv6_ra_mode': None, u'allocation_pools':
[{u'start': u'182.16.0.10', u'end': u'182.16.0.100'}], u'host_routes': [],
u'shared': False, u'ip_version': 4, u'ipv6_address_mode': None, u'cidr':
u'182.16.0.0/16', u'id': u'74bdee0a-1e09-4d74-97ac-7d48faada404'}, {u'name':
u'test', u'enable_dhcp': True, u'network_id':
u'6abaaf14-d0b5-4f4a-a436-7b728ab66c69', u'tenant_id':
u'c5fadfacec6148eb81a6fd1585763dde', u'dns_nameser
vers': [], u'gateway_ip': u'2001:db2::1', u'ipv6_ra_mode': None,
u'allocation_pools': [{u'start': u'2001:db2::2', u'end':
u'2001:db2:0:::::fffe'}], u'host_routes': [], u'shared': False,
u'ip_version': 6, u'ipv6_address_mode': None, u'cidr': u'2001:db2::/48', u'id':
u'5840f97e-8574-4841-bca2-2ed492c0b124'}] _list_resource
/usr/lib/python2.7/dist-packages/neutron_plugin_contrail/plugins/opencontrail/contrail_plugin.py:331
2017-04-24 17:30:57.679 650 INFO neutron.wsgi
[req-7104ac89-1938-4856-9916-0a4999ab96b1 7496e29fc1c141a081301bd9484f59c3
c5fadfacec6148eb81a6fd1585763dde - - -] 189.43.133.201 - - [24/Apr/2017
17:30:57] "GET
/v2.0/subnets?network_id=6abaaf14-d0b5-4f4a-a436-7b728ab66c69&cidr=2001:db2::/48&enable_dhcp=true&gateway_ip=null
HTTP/1.1" 200 1065 0.198209
I can see the condition has send by neutron , but it doesn't work
** Affects: opencontrail
Importance: Undecided
Status: New
** Project changed: horizon => opencontrail
--
You received thi
[Yahoo-eng-team] [Bug 1685732] [NEW] create_keystone_accounts error on latest devstack ocata branch(Ubuntu 16.04 LTS)
Public bug reported: Hi All, Im seeing this error on latest stable/ocata branch. I tried multiple reclones with repeated "./unstack.sh; ./clean.sh; ./stack.sh", but the issue is not getting fixed. I have raised the same issue in ask openstack(https://ask.openstack.org/en/question/105736 /create_keystone_accounts-error-on-latest-devstack-ocata- branchubuntu-1604-lts/) Logs below: ./stack.sh Error logs: + 2017-04-24 12:09:09.942 INFO keystone.cmd.cli [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created user admin 2017-04-24 12:09:10.008 INFO keystone.cmd.cli [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created role admin 2017-04-24 12:09:10.075 INFO keystone.cmd.cli [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Granted admin on admin to user admin. 2017-04-24 12:09:10.199 INFO keystone.cmd.cli [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created region RegionOne 2017-04-24 12:09:10.366 INFO keystone.cmd.cli [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created admin endpoint http://192.168.0.103/identity_admin 2017-04-24 12:09:10.451 INFO keystone.cmd.cli [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created public endpoint http://192.168.0.103/identity 2017-04-24 12:09:10.455 INFO keystone.assignment.core [req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Creating the default role 9fe2ff9ee4384b1894a90878d3e92bab because it does not exist. +./stack.sh:main:1076 create_keystone_accounts +lib/keystone:create_keystone_accounts:328 local admin_project ++lib/keystone:create_keystone_accounts:329 openstack project show admin -f value -c id Failed to discover available identity versions when contacting http://192.168.0.103/identity_admin. Attempting to parse version from URL. Could not determine a suitable URL for the plugin +lib/keystone:create_keystone_accounts:329 admin_project= +lib/keystone:create_keystone_accounts:1 exit_trap +./stack.sh:exit_trap:492 local r=1 ++./stack.sh:exit_trap:493 jobs -p +./stack.sh:exit_trap:493 jobs= +./stack.sh:exit_trap:496 [[ -n '' ]] +./stack.sh:exit_trap:502 kill_spinner +./stack.sh:kill_spinner:388 '[' '!' -z '' ']' +./stack.sh:exit_trap:504 [[ 1 -ne 0 ]] +./stack.sh:exit_trap:505 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:506 generate-subunit 1493015271 684 fail +./stack.sh:exit_trap:507 [[ -z /opt/stack/logs ]] +./stack.sh:exit_trap:510 /home/stack/openstack-repo/stable/ocata/tools/worlddump.py -d /opt/stack/logs World dumping... see /opt/stack/logs/worlddump-2017-04-24-063916.txt for details +./stack.sh:exit_trap:516 exit 1 Other logs: ++ stack@controller:/etc/apache2$ grep -rn identity* | grep wsgi sites-available/keystone-wsgi-admin.conf:1:ProxyPass "/identity_admin" "unix:/var/run/uwsgi/keystone-wsgi-admin.socket|uwsgi://uwsgi-uds-keystone-wsgi-admin/" retry=0 sites-available/keystone.conf:56:Alias /identity /usr/bin/keystone-wsgi-public sites-available/keystone.conf:66:Alias /identity_admin /usr/bin/keystone-wsgi-admin sites-available/keystone-wsgi-public.conf:1:ProxyPass "/identity" "unix:/var/run/uwsgi/keystone-wsgi-public.socket|uwsgi://uwsgi-uds-keystone-wsgi-public/" retry=0 stack@controller:/etc/apache2$ ps -ef | grep wsgi stack 4071 3900 0 12:09 pts/20 00:00:00 /usr/local/bin/uwsgi --ini /etc/keystone/keystone-uwsgi-public.ini stack 4129 4071 1 12:09 pts/20 00:00:02 /usr/local/bin/uwsgi --ini /etc/keystone/keystone-uwsgi-public.ini stack 4130 4071 1 12:09 pts/20 00:00:02 /usr/local/bin/uwsgi --ini /etc/keystone/keystone-uwsgi-public.ini stack 4263 0 12:09 pts/21 00:00:00 /usr/local/bin/uwsgi --ini /etc/keystone/keystone-uwsgi-admin.ini stack 4461 1 12:09 pts/21 00:00:03 /usr/local/bin/uwsgi --ini /etc/keystone/keystone-uwsgi-admin.ini stack 4462 1 12:09 pts/21 00:00:03 /usr/local/bin/uwsgi --ini /etc/keystone/keystone-uwsgi-admin.ini stack 5320 5977 0 12:12 pts/17 00:00:00 grep --color=auto wsgi stack@controller:/etc/apache2$ sudo netstat | grep 35357 stack@controller:/etc/apache2$ Please let me know if anymore info is required. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1685732 Title: create_keystone_accounts error on latest devstack ocata branch(Ubuntu 16.04 LTS) Status in OpenStack Identity (keystone): New Bug description: Hi All, Im seeing this error on latest stable/ocata branch. I tried multiple reclones with repeated "./unstack.sh; ./clean.sh; ./stack.sh", but the issue is not getting fixed. I have raised the same issu
