[Yahoo-eng-team] [Bug 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
Reviewed: https://review.openstack.org/499169 Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=f7dc03324971e11e26822558a62509f8bd15ab66 Submitter: Jenkins Branch:master commit f7dc03324971e11e26822558a62509f8bd15ab66 Author: Thomas Morin Date: Wed Aug 30 15:06:44 2017 +0200 Drop MANIFEST.in - it's not needed by pbr This patch removes `MANIFEST.in` file as pbr generates a sensible manifest and therefore there is no need for an explicit 'MANIFEST.in' file. Change-Id: Ie6275ffb65af340c066d5b4a557d8179a59d8002 Closes-Bug: 1608980 ** Changed in: bgpvpn Status: In Progress => 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/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in anvil: Invalid Status in networking-bgpvpn: Fix Released Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Glance: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in BaGPipe: Fix Released Status in networking-midonet: Fix Released Status in networking-odl: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Fix Released Status in octavia: Fix Released Status in os-vif: Fix Released Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in storlets: In Progress Status in Swift Authentication: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tacker: Fix Released Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1608980/+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 1715066] [NEW] Cannot launch instance with Django Launch Instance form when two or more networks
Public bug reported: When LAUNCH_INSTANCE_LEGACY_ENABLED is set to True and the Django launch instance form is used, a user cannot launch an instance when there is multiple networks. I selected network(s) and submitted the form, but the launch instance workflow was shown again. The selected networks are reset and all networks are shown in the Available Networks. As a result, users cannot launch instances with the Django Launch Instance form. It seems something has changed in Django 1.11. Previously network ID is shown with a small gray characters but now "(undefined)" is shown, so it looks like generate_html() JS function does not work expectedly. ** Affects: horizon Importance: High Status: New ** Tags: pike-backport-potential ** Tags added: pike-backport-potential ** Changed in: horizon Importance: Undecided => High -- 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/1715066 Title: Cannot launch instance with Django Launch Instance form when two or more networks Status in OpenStack Dashboard (Horizon): New Bug description: When LAUNCH_INSTANCE_LEGACY_ENABLED is set to True and the Django launch instance form is used, a user cannot launch an instance when there is multiple networks. I selected network(s) and submitted the form, but the launch instance workflow was shown again. The selected networks are reset and all networks are shown in the Available Networks. As a result, users cannot launch instances with the Django Launch Instance form. It seems something has changed in Django 1.11. Previously network ID is shown with a small gray characters but now "(undefined)" is shown, so it looks like generate_html() JS function does not work expectedly. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1715066/+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 1698110] Re: aggregate-add-host but instances' az unmodified
[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.] ** Changed in: nova Status: Incomplete => Expired -- 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/1698110 Title: aggregate-add-host but instances' az unmodified Status in OpenStack Compute (nova): Expired Bug description: we use "nova aggregate-add-host" to change host's az, but instances on this host didn't update az, the db field "availablity_zone" in "instances" table. Steps to reproduce == 1. nova aggregate-create test test 2. assume 'host1' belong to 'nova' az, and has instance 'inst1' on it. 3. nova aggregate-add-host test host1 Expected result === in db, field 'instances.availablity_zone' for 'inst1' should be 'test' Actual result = in db, field 'instances.availablity_zone' for 'inst1' is 'nova' Nova version == $ rpm -qa | grep nova python-novaclient-2.30.1-1.el7.noarch openstack-nova-conductor-12.0.0-1.el7.centos.noarch python-nova-12.0.0-1.el7.centos.noarch openstack-nova-scheduler-12.0.0-1.el7.centos.noarch openstack-nova-novncproxy-12.0.0-1.el7.centos.noarch openstack-nova-api-12.0.0-1.el7.centos.noarch openstack-nova-common-12.0.0-1.el7.centos.noarch openstack-nova-cert-12.0.0-1.el7.centos.noarch openstack-nova-console-12.0.0-1.el7.centos.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1698110/+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 1714416] Re: Incorrect response returned for invalid Accept header
** Changed in: masakari Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1714416 Title: Incorrect response returned for invalid Accept header Status in Cinder: Won't Fix Status in Glance: New Status in OpenStack Heat: New Status in OpenStack Identity (keystone): New Status in masakari: Won't Fix Status in neutron: New Status in OpenStack Compute (nova): New Bug description: As of now, when user passes 'Accept' header in request other than JSON and XML using curl command then it returns 200 OK response with json format data. In api-ref guide [1] also it's not clearly mentioned about what response it should return if invalid value for 'Accept' header is specified. IMO instead of 'HTTP 200 OK' it should return 'HTTP 406 Not Acceptable' response. Steps to reproduce: Request: curl -g -i -X GET http://controller/volume/v2/c72e66cc4f1341f381e0c2eb7b28b443/volumes/detail -H "User-Agent: python-cinderclient" -H "Accept: application/abc" -H "X-Auth-Token: cd85aff745ce4dc0a04f686b52cf7e4f" Response: HTTP/1.1 200 OK Date: Thu, 31 Aug 2017 07:12:18 GMT Server: Apache/2.4.18 (Ubuntu) x-compute-request-id: req-ab48db9d-f869-4eb4-95f9-ef8e90a918df Content-Type: application/json Content-Length: 2681 x-openstack-request-id: req-ab48db9d-f869-4eb4-95f9-ef8e90a918df Connection: close [1] https://developer.openstack.org/api-ref/block-storage/v2/#list-volumes-with-details To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1714416/+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 1715042] [NEW] Flavor list is not in order when booting instance
Public bug reported: Currently, the flavor list is not in order when booting instance. It would be nice to list them by vcpu and ram by default. ** Affects: horizon Importance: Undecided Assignee: Fei Long Wang (flwang) Status: In Progress -- 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/1715042 Title: Flavor list is not in order when booting instance Status in OpenStack Dashboard (Horizon): In Progress Bug description: Currently, the flavor list is not in order when booting instance. It would be nice to list them by vcpu and ram by default. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1715042/+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 1713095] Re: Nova compute driver init happens before conductor is ready
Reviewed: https://review.openstack.org/497966 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=361287debf7c2cd5751517cedda8c960c5b5eb66 Submitter: Jenkins Branch:master commit 361287debf7c2cd5751517cedda8c960c5b5eb66 Author: Dan Smith Date: Fri Aug 25 08:48:49 2017 -0700 Move hash ring initialization to init_host() for ironic The hash ring initialization code requires calling to conductor over RPC. Nova's service startup initializes the manager and the virt driver, then goes into a polling loop waiting for a conductor to respond to make sure it is ready. Finally, it calls init_host() once things are expected to be working. That is where we should do our initialization that requires conductor to be up. This patch moves the initial refresh into the Ironic driver's init_host() routine. Change-Id: If92f4b1df061f91a7900532a978649efb933 Closes-Bug: #1713095 ** Changed in: nova Status: In Progress => Fix Released -- 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/1713095 Title: Nova compute driver init happens before conductor is ready Status in OpenStack Compute (nova): Fix Released Bug description: In nova/service.py we poll for conductor readiness before we allow normal service startup behavior. The ironic driver does RPC to conductor in its _refresh_hash_ring() code, which may expect conductor be up before it's not. If so, we'll fail to start up because we called to conductor, waited a long time, and then timed out. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1713095/+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 1714416] Re: Incorrect response returned for invalid Accept header
Further discussion was here: http://lists.openstack.org/pipermail/openstack- dev/2017-September/121778.html I do agree with the consensus there. Worth having the discussion and increasing the visibility with this bug, but at least for Cinder I am going to mark this as Won't Fix unless there is a more compelling argument to change it. Thanks for bringing it up. ** Changed in: cinder Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1714416 Title: Incorrect response returned for invalid Accept header Status in Cinder: Won't Fix Status in Glance: New Status in OpenStack Heat: New Status in OpenStack Identity (keystone): New Status in masakari: New Status in neutron: New Status in OpenStack Compute (nova): New Bug description: As of now, when user passes 'Accept' header in request other than JSON and XML using curl command then it returns 200 OK response with json format data. In api-ref guide [1] also it's not clearly mentioned about what response it should return if invalid value for 'Accept' header is specified. IMO instead of 'HTTP 200 OK' it should return 'HTTP 406 Not Acceptable' response. Steps to reproduce: Request: curl -g -i -X GET http://controller/volume/v2/c72e66cc4f1341f381e0c2eb7b28b443/volumes/detail -H "User-Agent: python-cinderclient" -H "Accept: application/abc" -H "X-Auth-Token: cd85aff745ce4dc0a04f686b52cf7e4f" Response: HTTP/1.1 200 OK Date: Thu, 31 Aug 2017 07:12:18 GMT Server: Apache/2.4.18 (Ubuntu) x-compute-request-id: req-ab48db9d-f869-4eb4-95f9-ef8e90a918df Content-Type: application/json Content-Length: 2681 x-openstack-request-id: req-ab48db9d-f869-4eb4-95f9-ef8e90a918df Connection: close [1] https://developer.openstack.org/api-ref/block-storage/v2/#list-volumes-with-details To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1714416/+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 1535918] Re: instance.host not updated on evacuation
This bug was fixed in the package nova - 2:13.1.4-0ubuntu3 --- nova (2:13.1.4-0ubuntu3) xenial; urgency=medium * Fix evacuation error when nova-compute is down just after VM is started. - d/p/make-sure-to-rebuild-claim-on-recreate.patch (backported from newton 0f2d874, upstream a2b0824) - d/p/Send-events-to-all-relevant-hosts-if-migrating.patch (LP: #1535918) (backported from a5b920) -- Seyeong Kim Fri, 04 Aug 2017 04:46:40 +0900 ** Changed in: nova (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1535918 Title: instance.host not updated on evacuation Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Committed Status in OpenStack Compute (nova): Fix Released Status in nova-powervm: Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Xenial: Fix Released Status in nova source package in Zesty: Fix Released Status in nova source package in Artful: Fix Released Bug description: [Impact] I created several VM instances and checked they are all ACTIVE state after creating vm. Right after checking them, shutdown nova-compute on their host(to test in this case). Then, I tried to evacuate them to the other host. But it is failed with ERROR state. I did some test and analysis. I found two commits below are related.(Please refer to [Others] section) In this context, migration_context is DB field to pass information when migration or evacuation. for [1], This gets host info from migration_context. if migration_context is abnormal or empty, migration would be fail. actually, with only this patch, migration_context is empty. so [2] is needed. I touched self.client.prepare part in rpcapi.py from original patch which is replaced on newer version. because it is related newer functionality, I remained mitaka's function call for this issue. for [2], This moves recreation check code to former if condition. and it calls rebuild_claim to create migration_context when recreate state not only scheduled. I adjusted test code which are pop up from backport process and seems to be needed. Someone want to backport or cherrypick code related to this, they could find it is already exist. Only one patch of them didn’t fix this issue as test said. [Test case] In below env, http://pastebin.ubuntu.com/25337153/ Network configuration is important in this case, because I tested different configuration. but couldn't reproduce it. reproduction test script ( based on juju ) http://pastebin.ubuntu.com/25360805/ [Regression Potential] Existing ACTIVE instances or newly creating instances are not affected by this code because these commits are only called when doing migration or evacuation. If there are ACTIVE instances and instances with ERROR state caused by this issue in one host, upgrading to have this fix will not affect any existing instances. After upgrading to have this fix and trying to evacuate problematic instance again, ERROR state should be fixed to ACTIVE. I tested this scenario on simple env, but still need to be considered possibility in complex, crowded environment. [Others] In test, I should patch two commits, one from https://bugs.launchpad.net/nova/+bug/1686041 Related Patches. [1] https://github.com/openstack/nova/commit/a5b920a197c70d2ae08a1e1335d979857f923b4f [2] https://github.com/openstack/nova/commit/0f2d87416eff1e96c0fbf0f4b08bf6b6b22246d5 ( backported to newton from below original) - https://github.com/openstack/nova/commit/a2b0824aca5cb4a2ae579f625327c51ed0414d35 ( original) [Original description] I'm working on the nova-powervm driver for Mitaka and trying to add support for evacuation. The problem I'm hitting is that instance.host is not updated when the compute driver is called to spawn the instance on the destination host. It is still set to the source host. It's not until after the spawn completes that the compute manager updates instance.host to reflect the destination host. The nova-powervm driver uses instance events callback mechanism during plug VIF to determine when Neutron has finished provisioning the network. The instance events code sends the event to instance.host and hence is sending the event to the source host (which is down). This causes the spawn to fail and also causes weirdness when the source host gets the events when it's powered back up. To temporarily work around the problem, I hacked in setting instance.host = CONF.host; instance.save() in the compute driver but that's not a good solution. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1535918/+subscriptions -- Maili
[Yahoo-eng-team] [Bug 1714987] [NEW] description in _create_backup.html only assumes object storage service
Public bug reported:
Actually cinder-backup driver can be something other than object
storage, such as Ceph, NFS. So mentioning "object storage service must
be enabled" is confusing to end users. The description below could have
some space for improvement.
[./openstack_dashboard/dashboards/project/backups/templates/backups/_create_backup.html]
{% block modal-body-right %}
{% trans "Volume Backup:" %} {% trans "Volume Backups are
stored using the Object Storage service. You must have this service activated
in order to create a backup." %}
{% trans "If no container name is provided, a default container named
volumebackups will be provisioned for you. Backups will be the same size as the
volume they originate from." %}
{% endblock %}
** 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/1714987
Title:
description in _create_backup.html only assumes object storage service
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Actually cinder-backup driver can be something other than object
storage, such as Ceph, NFS. So mentioning "object storage service must
be enabled" is confusing to end users. The description below could
have some space for improvement.
[./openstack_dashboard/dashboards/project/backups/templates/backups/_create_backup.html]
{% block modal-body-right %}
{% trans "Volume Backup:" %} {% trans "Volume Backups
are stored using the Object Storage service. You must have this service
activated in order to create a backup." %}
{% trans "If no container name is provided, a default container named
volumebackups will be provisioned for you. Backups will be the same size as the
volume they originate from." %}
{% endblock %}
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1714987/+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 1714864] Re: [RFE]: Add support for multiple resource classes to ironic nodes
** Changed in: ironic Status: New => Confirmed ** Changed in: ironic Importance: Undecided => Wishlist ** Also affects: nova Importance: Undecided Status: New ** Tags added: needs-spec rfe -- 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/1714864 Title: [RFE]: Add support for multiple resource classes to ironic nodes Status in Ironic: Confirmed Status in OpenStack Compute (nova): New Bug description: This bug proposes to add support for multiple resource classes to ironic nodes. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1714864/+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 1702855] Re: Next steps in Installation Guide - "https://docs.openstack.org/admin-guide/dashboard-sessions.html" does not work
Reviewed: https://review.openstack.org/500074 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d44f1c7e1498e29d7040f04b28056f663bc647e1 Submitter: Jenkins Branch:master commit d44f1c7e1498e29d7040f04b28056f663bc647e1 Author: Petr Kovar Date: Fri Sep 1 16:35:00 2017 +0200 [doc] Fix broken links Change-Id: I58de603276913ab4b1c05f675738bcb20711f9ef Closes-Bug: #1702855 Closes-Bug: #1702854 ** 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/1702855 Title: Next steps in Installation Guide - "https://docs.openstack.org/admin- guide/dashboard-sessions.html" does not work Status in OpenStack Dashboard (Horizon): Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: "https://docs.openstack.org/admin-guide/dashboard-sessions.html"; link does not work. - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 0.1 on 2017-06-29 19:44 SHA: 3d8cb4ddcef823e5edab04e30ca1a6678c6a8ecd Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-next-steps.rst URL: https://docs.openstack.org/newton/install-guide-ubuntu/horizon-next-steps.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1702855/+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 1702854] Re: Next steps in Installation Guide - Customize the dashboard link does not work
Reviewed: https://review.openstack.org/500074 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d44f1c7e1498e29d7040f04b28056f663bc647e1 Submitter: Jenkins Branch:master commit d44f1c7e1498e29d7040f04b28056f663bc647e1 Author: Petr Kovar Date: Fri Sep 1 16:35:00 2017 +0200 [doc] Fix broken links Change-Id: I58de603276913ab4b1c05f675738bcb20711f9ef Closes-Bug: #1702855 Closes-Bug: #1702854 ** 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/1702854 Title: Next steps in Installation Guide - Customize the dashboard link does not work Status in OpenStack Dashboard (Horizon): Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: Customize the dashboard. link does not work. (https://docs.openstack.org/admin-guide/dashboard-customize-configure.html) - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 0.1 on 2017-06-29 19:44 SHA: 3d8cb4ddcef823e5edab04e30ca1a6678c6a8ecd Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-next-steps.rst URL: https://docs.openstack.org/newton/install-guide-ubuntu/horizon-next-steps.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1702854/+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 1714961] [NEW] Incorrect description on Flavor Access tab
Public bug reported: It reads: "Select the projects where the flavors will be used. If no projects are selected, then the flavor will be available in all projects." This is only true when the flavor is public, in that case the selection of projects isn't relevant anyway. When the flavor is private and no projects are selected, the flavor is not available in any project. ** 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/1714961 Title: Incorrect description on Flavor Access tab Status in OpenStack Dashboard (Horizon): New Bug description: It reads: "Select the projects where the flavors will be used. If no projects are selected, then the flavor will be available in all projects." This is only true when the flavor is public, in that case the selection of projects isn't relevant anyway. When the flavor is private and no projects are selected, the flavor is not available in any project. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1714961/+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 1714937] [NEW] keystone returns 500 on password change
Public bug reported:
$ openstack user set --password-prompt demo
User Password:
Repeat User Password:
An unexpected error prevented the server from fulfilling your request. (HTTP
500) (Request-ID: req-175ea0bf-02d3-4d73-a3ca-662612c36543)
$
Although there is an error, the password has been changed, though.
Traceback from keystone log:
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG
keystone.common.authorization [None req-175ea0bf-02d3-4d73-a3ca-662612c36543
None None] RBAC: Authorizing
identity:update_user(user_id=30f37144f2494fd5b46d97acb72de22c,
user={u'password': u'***', u'enabl
ed': True}) {{(pid=1804) _build_policy_check_credentials
/opt/stack/keystone/keystone/common/authorization.py:137}}
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG
keystone.policy.backends.rules [None req-175ea0bf-02d3-4d73-a3ca-662612c36543
None None] enforce identity:update_user: {'is_delegated_auth': False,
'access_token_id': None, 'user_id': u'd55b3e8a3e084ba6a
061b73c33112b05', 'roles': [u'admin'], 'user_domain_id': u'default',
'consumer_id': None, 'trustee_id': None, 'is_domain': False,
'is_admin_project': True, 'trustor_id': None, 'token': , 'project_id': u'a42a75e7ca804a6288f3eb51c0fd9eb7',
'trust_id': None, 'project_domain_id': u'default'} {{(pid=1804) enforce
/opt/stack/keystone/keystone/policy/backends/rules.py:33}}
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG
oslo_policy.policy [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None None]
The policy file policy.json could not be found. {{(pid=1804) load_rules
/usr/local/lib/python2.7/dist-packages/oslo_policy/pol
icy.py:532}}
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG
keystone.common.authorization [None req-175ea0bf-02d3-4d73-a3ca-662612c36543
None None] RBAC: Authorization granted {{(pid=1804) check_policy
/opt/stack/keystone/keystone/common/authorization.py:240}}
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG
keystone.notifications [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None
None] Invoking callback _user_callback for event identity
invalidate_user_tokens internal for {'resource_info': u'30f37144f2494f
d5b46d97acb72de22c'} {{(pid=1804) notify_event_callbacks
/opt/stack/keystone/keystone/notifications.py:297}}
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: DEBUG
keystone.notifications [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None
None] Invoking callback _delete_user_tokens_callback for event identity
invalidate_user_tokens internal for {'resource_info': u'
30f37144f2494fd5b46d97acb72de22c'} {{(pid=1804) notify_event_callbacks
/opt/stack/keystone/keystone/notifications.py:297}}
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: WARNING
stevedore.named [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None None] Could
not load blah
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi [None req-175ea0bf-02d3-4d73-a3ca-662612c36543 None None]
(u'Unable to find %(name)r driver in %(namespace)r.', {'namespace':
'keystone.token.persistence', 'name': 'blah'}): ImportEr
ror: (u'Unable to find %(name)r driver in %(namespace)r.', {'namespace':
'keystone.token.persistence', 'name': 'blah'})
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi Traceback (most recent call last):
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/common/wsgi.py", line
228, in __call__
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi result = method(req, **params)
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi File
"/opt/stack/keystone/keystone/common/controller.py", line 94, in inner
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi return f(self, request, *args, **kwargs)
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi File
"/opt/stack/keystone/keystone/identity/controllers.py", line 255, in update_user
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi return self._update_user(request, user_id, user)
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi File
"/opt/stack/keystone/keystone/identity/controllers.py", line 248, in
_update_user
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi user_id, user, initiator=request.audit_initiator
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/common/manager.py",
line 110, in wrapped
Sep 04 11:36:44 jh-devstack-02 devstack@keystone.service[1797]: ERROR
keystone.common.wsgi __ret_val = __f(*args, **kwargs)
Sep 04 1
[Yahoo-eng-team] [Bug 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
Reviewed: https://review.openstack.org/499409 Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=33a43f7d54fee141479b0ec61426a4ae8972c62d Submitter: Jenkins Branch:master commit 33a43f7d54fee141479b0ec61426a4ae8972c62d Author: luqitao Date: Thu Aug 31 09:23:31 2017 +0800 Drop MANIFEST.in - it's not needed by pbr Tacker already uses PBR:- setuptools.setup( setup_requires=['pbr>=2.0.0'], pbr=True) This patch removes `MANIFEST.in` file as pbr generates a sensible manifest from git files and some standard files and it removes the need for an explicit `MANIFEST.in` file. Change-Id: Ia90ea3018b42c2536af899af77de9c4c651c9b6f Closes-Bug: #1608980 ** Changed in: tacker Status: In Progress => 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/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in anvil: Invalid Status in networking-bgpvpn: In Progress Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Glance: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in BaGPipe: Fix Released Status in networking-midonet: Fix Released Status in networking-odl: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Fix Released Status in octavia: Fix Released Status in os-vif: Fix Released Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in storlets: In Progress Status in Swift Authentication: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tacker: Fix Released Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1608980/+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 1714924] [NEW] placement api fails when nova tries to delete resource allocation after failed evacuation
Public bug reported:
During the investigation of bug #1713783 (After failed evacuation the
recovered source compute tries to delete the instance) we noticed that
nova tries to PUT an empty '{}' allocations for an instance and that
fails on the placement side. As bug #1713783 now seems to be solved by
keeping the existing behavior, i.e. deleting the instance after failed
evacuation. We have to fix nova not to try to PUT the allocation but
actually DELETE the allocation of the instance in placement.
The problem can be reproduced with the regression test proposed in
https://review.openstack.org/#/c/498482/ which produce the following
stack trace:
2017-09-04 11:33:24,989 INFO [nova.service] Starting compute node (version
16.0.1)
2017-09-04 11:33:25,005 INFO [nova.compute.manager] Deleting instance as it
has been evacuated from this host
2017-09-04 11:33:25,060 INFO [nova.api.openstack.placement.requestlog]
127.0.0.1 "GET /placement/allocations/4d056cc0-b227-4f79-baab-f3e3cd1a6d00"
status: 200 len: 134 microversion: 1.0
2017-09-04 11:33:25,066 INFO [nova.api.openstack.placement.requestlog]
127.0.0.1 "PUT /placement/allocations/4d056cc0-b227-4f79-baab-f3e3cd1a6d00"
status: 400 len: 651 microversion: 1.10
2017-09-04 11:33:25,067 WARNING [nova.scheduler.client.report] Failed to
save allocation for 4d056cc0-b227-4f79-baab-f3e3cd1a6d00. Got HTTP 400:
400 Bad Request
400 Bad Request
The server could not comply with the request since it is either malformed
or otherwise incorrect.
JSON does not validate: {} does not have enough properties
Failed validating 'minProperties' in
schema['properties']['allocations']['items']['properties']['resources']:
{'additionalProperties': False,
'minProperties': 1,
'patternProperties': {'^[0-9A-Z_]+$': {'minimum': 1,
'type': 'integer'}},
'type': 'object'}
On instance['allocations'][0]['resources']:
{}
2017-09-04 11:33:25,067 ERROR [nova.compute.resource_tracker] Failed to
clean allocation of evacuated instance on the source node
bc78aa7f-07df-4e06-bb77-71aec7d92e5c
** Affects: nova
Importance: Undecided
Status: New
** Tags: evacuate placement
** Tags added: evac
** Tags removed: evac
** Tags added: evacuate placement
--
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/1714924
Title:
placement api fails when nova tries to delete resource allocation
after failed evacuation
Status in OpenStack Compute (nova):
New
Bug description:
During the investigation of bug #1713783 (After failed evacuation the
recovered source compute tries to delete the instance) we noticed that
nova tries to PUT an empty '{}' allocations for an instance and that
fails on the placement side. As bug #1713783 now seems to be solved by
keeping the existing behavior, i.e. deleting the instance after failed
evacuation. We have to fix nova not to try to PUT the allocation but
actually DELETE the allocation of the instance in placement.
The problem can be reproduced with the regression test proposed in
https://review.openstack.org/#/c/498482/ which produce the following
stack trace:
2017-09-04 11:33:24,989 INFO [nova.service] Starting compute node
(version 16.0.1)
2017-09-04 11:33:25,005 INFO [nova.compute.manager] Deleting instance as
it has been evacuated from this host
2017-09-04 11:33:25,060 INFO [nova.api.openstack.placement.requestlog]
127.0.0.1 "GET /placement/allocations/4d056cc0-b227-4f79-baab-f3e3cd1a6d00"
status: 200 len: 134 microversion: 1.0
2017-09-04 11:33:25,066 INFO [nova.api.openstack.placement.requestlog]
127.0.0.1 "PUT /placement/allocations/4d056cc0-b227-4f79-baab-f3e3cd1a6d00"
status: 400 len: 651 microversion: 1.10
2017-09-04 11:33:25,067 WARNING [nova.scheduler.client.report] Failed to
save allocation for 4d056cc0-b227-4f79-baab-f3e3cd1a6d00. Got HTTP 400:
400 Bad Request
400 Bad Request
The server could not comply with the request since it is either
malformed or otherwise incorrect.
JSON does not validate: {} does not have enough properties
Failed validating 'minProperties' in
schema['properties']['allocations']['items']['properties']['resources']:
{'additionalProperties': False,
'minProperties': 1,
'patternProperties': {'^[0-9A-Z_]+$': {'minimum': 1,
'type': 'integer'}},
'type': 'object'}
On instance['allocations'][0]['resources']:
{}
2017-09-04 11:33:25,067 ERROR [nova.compute.resource_tracker] Failed to
clean allocation of evacuated instance on the source node
bc78a
[Yahoo-eng-team] [Bug 1714915] [NEW] dns nameserver
Public bug reported: In master, There is no any dns server in subnet, and I don't want any dns server in VM, I found I have no methods to accomplish their goal， The nameserver in VM is DHCP address. ** Affects: neutron Importance: Undecided Assignee: QunyingRan (ran-qunying) Status: New ** Changed in: neutron Assignee: (unassigned) => QunyingRan (ran-qunying) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1714915 Title: dns nameserver Status in neutron: New Bug description: In master, There is no any dns server in subnet, and I don't want any dns server in VM, I found I have no methods to accomplish their goal， The nameserver in VM is DHCP address. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1714915/+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 1714901] [NEW] gate-rally-dsvm-neutron-neutron-ubuntu-xenial failing 100% in NeutronTrunks.create_and_list_trunk_subports
Public bug reported:
This has started about two days ago:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NeutronTrunks.create_and_list_trunk_subports%5C%22%20AND%20message%3A%5C%22FAIL%5C%22
Sample failure log:
http://logs.openstack.org/61/500261/2/check/gate-rally-dsvm-neutron-
neutron-ubuntu-xenial/f5742a5/rally-plot/detailed.txt.gz
Task fe68e403-0694-4016-be5d-e02f67cb04fd has 4 error(s)
NotFound: The resource could not be found.
Neutron server returns request_ids: ['req-ff94c196-cb60-41d6-9e2c-42f780960d69']
Traceback (most recent call last):
File "/opt/stack/new/rally/rally/task/runner.py", line 72, in
_run_scenario_once
getattr(scenario_inst, method_name)(**scenario_kwargs)
File "/home/jenkins/.rally/plugins/plugins/trunk_scenario.py", line 41, in run
trunk = self._create_trunk(trunk_payload)
File "/opt/stack/new/rally/rally/task/atomic.py", line 85, in
func_atomic_actions
f = func(self, *args, **kwargs)
File "/home/jenkins/.rally/plugins/plugins/trunk_scenario.py", line 53, in
_create_trunk
return self.clients("neutron").create_trunk({'trunk': trunk_payload})
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 2067, in create_trunk
return self.post(self.trunks_path, body=body)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 357, in post
headers=headers, params=params)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 292, in do_request
self._handle_fault_response(status_code, replybody, resp)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 268, in _handle_fault_response
exception_handler_v20(status_code, error_body)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 92, in exception_handler_v20
request_ids=request_ids)
NotFound: The resource could not be found.
Neutron server returns request_ids: ['req-ff94c196-cb60-41d6-9e2c-42f780960d69']
** 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/1714901
Title:
gate-rally-dsvm-neutron-neutron-ubuntu-xenial failing 100% in
NeutronTrunks.create_and_list_trunk_subports
Status in neutron:
New
Bug description:
This has started about two days ago:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NeutronTrunks.create_and_list_trunk_subports%5C%22%20AND%20message%3A%5C%22FAIL%5C%22
Sample failure log:
http://logs.openstack.org/61/500261/2/check/gate-rally-dsvm-neutron-
neutron-ubuntu-xenial/f5742a5/rally-plot/detailed.txt.gz
Task fe68e403-0694-4016-be5d-e02f67cb04fd has 4 error(s)
NotFound: The resource could not be found.
Neutron server returns request_ids:
['req-ff94c196-cb60-41d6-9e2c-42f780960d69']
Traceback (most recent call last):
File "/opt/stack/new/rally/rally/task/runner.py", line 72, in
_run_scenario_once
getattr(scenario_inst, method_name)(**scenario_kwargs)
File "/home/jenkins/.rally/plugins/plugins/trunk_scenario.py", line 41, in
run
trunk = self._create_trunk(trunk_payload)
File "/opt/stack/new/rally/rally/task/atomic.py", line 85, in
func_atomic_actions
f = func(self, *args, **kwargs)
File "/home/jenkins/.rally/plugins/plugins/trunk_scenario.py", line 53, in
_create_trunk
return self.clients("neutron").create_trunk({'trunk': trunk_payload})
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 2067, in create_trunk
return self.post(self.trunks_path, body=body)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 357, in post
headers=headers, params=params)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 292, in do_request
self._handle_fault_response(status_code, replybody, resp)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 268, in _handle_fault_response
exception_handler_v20(status_code, error_body)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py",
line 92, in exception_handler_v20
request_ids=request_ids)
NotFound: The resource could not be found.
Neutron server returns request_ids:
['req-ff94c196-cb60-41d6-9e2c-42f780960d69']
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714901/+subscriptions
--
Mailing list: https://launchpad.net/~yaho
[Yahoo-eng-team] [Bug 1714895] [NEW] Instance failed to create when numa node has enough free vcpus but has not enough sibling vcpus
Public bug reported: Instance failed to create when numa node has enough free vcpus but has not enough sibling vcpus. eg: Host has following numa topology: node 0: 0-7,16-23 node 1: 8-15,24-31 vcpu_pin_set is 1-7,16-23,7-15,24-31 I want to create an instance with 30 vcpus with flavor which has extra_specs: hw:cpu_policy=dedicated and hu:numa_nodes=2. But it failed for the following condition in _get_pinning function: if threads_no * len(sibling_set) < ( len(instance_cores) + num_cpu_reserved): return None, None because: threads_no=1 len(sibling_set)=7 len(instance_cores)=15 and threads_no=2 len(sibling_set)=7 len(instance_cores)=15 ** Affects: nova Importance: Undecided Status: New -- 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/1714895 Title: Instance failed to create when numa node has enough free vcpus but has not enough sibling vcpus Status in OpenStack Compute (nova): New Bug description: Instance failed to create when numa node has enough free vcpus but has not enough sibling vcpus. eg: Host has following numa topology: node 0: 0-7,16-23 node 1: 8-15,24-31 vcpu_pin_set is 1-7,16-23,7-15,24-31 I want to create an instance with 30 vcpus with flavor which has extra_specs: hw:cpu_policy=dedicated and hu:numa_nodes=2. But it failed for the following condition in _get_pinning function: if threads_no * len(sibling_set) < ( len(instance_cores) + num_cpu_reserved): return None, None because: threads_no=1 len(sibling_set)=7 len(instance_cores)=15 and threads_no=2 len(sibling_set)=7 len(instance_cores)=15 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1714895/+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 1711149] Re: Install and configure (Ubuntu) in glance
This is not a bug, is'n it? ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1711149 Title: Install and configure (Ubuntu) in glance Status in Glance: Invalid Bug description: Lack of steps to create a glance database in 'Prerequisites' This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 15.0.0.0rc2.dev2 on 'Fri Aug 11 01:06:58 2017, commit e612a90' SHA: e612a90092edc619c93324d3f5334243c64571be Source: https://git.openstack.org/cgit/openstack/glance/tree/doc/source/install/install-ubuntu.rst URL: https://docs.openstack.org/glance/pike/install/install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1711149/+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
