Public bug reported:
This is kind of a halfway between Nova and Infra, but I'm adding it here
for tracking purposes. Basically we have a tool for bug reporting in
Nova that should be hosted in an Infra resource so that we're not
dependent on whoever is running the bugs team to host it.
Bug reporter was not able to repro behavior in the nova console; this
only happens when using Horizon. marking as invalid for Nova and adding
Horizon to the bug report.
** Also affects: horizon
Importance: Undecided
Status: New
** Changed in: nova
Status: Incomplete => Invalid
Based on your config, your devstack is using Neutron for networking.
Nova-network commands won't work.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
Please clarify what documentation updates are needed so others can work
on updating them.
** Changed in: nova
Status: Expired => Incomplete
** Changed in: nova
Assignee: (unassigned) => Lucian Petrut (petrutlucian94)
--
You received this bug notification because you are a member of
Public bug reported:
I was running unit tests on a bare bones vm that didn't have genisoimage
installed and the test_rescue_config_drive test failed.
==
Failed 1 tests - output below:
==
I'm going to update the status of this bug as wontfix per comments
regarding Cellsv1 freeze above. If you find further information that
suggests this is unrelated to Cellsv1 then feel free to reopen this bug
with that new information.
** Changed in: nova
Status: Confirmed => Won't Fix
**
Marking this bug as invalid because it was determined to be a feature
request and would be resolved by current specs under review.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
I'm going to mark this as Invalid for now. I asked in the nova irc
channel and it looks like my previous comment is accurate. If you have
further information per my comment above, please feel free to add it and
reopen this bug.
** Tags removed: needs-attention
** Changed in: nova
Status:
I agree that if this is a use case that needs to be documented then this
is a valid bug. I've also added the openstack-manuals project to get
someone from the docs team to make sure there isn't anything in the
admin guide or anywhere else that would also benefit from this
information.
** Also
The decision to abort is made via the should_abort() method using the
progress_timeout and the completion_timeout in the same method. The
issue reported here is that if the ephemeral disk is very full, the
progress part ends up taking too long, and the completion_timeout check
in the
I feel like this is bordering on a feature request and should be
associated with a blueprint rather than a bug. The documentation
specifically states that the expectation is an admin user:
http://docs.openstack.org/admin-guide/cli-set-compute-quotas.html
Neutron client supports a "quota-show"
** Changed in: nova
Status: Confirmed => 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/1463372
Title:
nova secgroup-list-rules shows empty table
** Changed in: nova
Status: Confirmed => Fix Released
** Changed in: nova
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This looks like a feature request and not a bug. Please propose this as
a blueprint instead, https://wiki.openstack.org/wiki/Blueprints
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
This looks more like a feature request. If you would like to introduce
this behavior into Nova, please propose a blueprint.
https://wiki.openstack.org/wiki/Blueprints
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
This looks like you have an error in your api-paste.ini file. Check your
settings. If you need further assistance, feel free to send a question
to the openstack mailing list or on the #openstack irc channel.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification
lid
** Changed in: nova
Assignee: Augustina Ragwitz (auggy) => (unassigned)
--
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/1613199
Title:
nova does not accept ssh certi
*** This bug is a duplicate of bug 1555065 ***
https://bugs.launchpad.net/bugs/1555065
** This bug is no longer a duplicate of bug 1064386
Image stays in Saving State if any error occurs while snapshotting an
instance
** This bug has been marked a duplicate of bug 1555065
Image goes to
*** This bug is a duplicate of bug 1555065 ***
https://bugs.launchpad.net/bugs/1555065
** This bug is no longer a duplicate of bug 1064386
Image stays in Saving State if any error occurs while snapshotting an
instance
** This bug has been marked a duplicate of bug 1555065
Image goes to
Since the Mitaka cycle we use the direct release model, which means this
should be Fix Released.
** Changed in: nova
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
A previous comment indicated this bug had been addressed by
https://review.openstack.org/#/c/148904/ so marking this as Fix
Released.
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
This looks like a possible configuration issue, according to your logs I
see the following:
>From nova compute manager:
ConnectFailure: Unable to establish connection to
http://192.168.10.59:9696/v2.0/ports.json?tenant_id=a28c7b4b55034254a2d912fe6bfb49ad_id=21a97ef7-7ae8-4f...
And from the
Hi Erwin, thanks for taking the time to file a bug with Nova. For
support requests, please try the openstack mailing list or the
#openstack channel in IRC.
It looks like some requests made to on cloud.edpsystem.com are timing
out. That looks like a server configuration issue based on the snippet
Thanks for the reply! Because Kilo is at end of life, we are not
supporting it any further. Since you don't see this issue in Mitaka, I
will close this as Invalid. If it turns out this issue is not fixed in
Mitaka or current master, please feel free to reopen and report your
findings.
** Changed
The parameters for os-security-groups have already been validated as
part of the api-ref effort. If you have information that parameters are
missing, please reopen this bug and provide more detail like where you
see these parameters in code or some output that shows them.
Related change was abandoned and it's not clear that this is really a
bug, more like a feature request. Marking as invalid. Please follow the
specless blueprint process if you still want this feature.
** Changed in: nova
Assignee: ChangBo Guo(gcb) (glongwave) => (unassigned)
** Changed in:
This is not a bug, it is a feature request and will be tracked as a
blueprint. Marking as invalid.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
Marking this as invalid - please resubmit as a blueprint/spec.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
The patch was abandoned because it was determined these values should be
validated/filtered in the GlanceImageServiceV2 class. Also this issue is
no longer blocking Glance v2 compatibility per
https://review.openstack.org/#/c/321551/
Marking this as invalid, please reopen if I'm mistaken.
**
Based on the comment in the abandoned change, it looks like this bug is
invalid. Please reopen if I'm mistaken.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Requested information was not provided and bug was marked for
expiration, so marking as invalid. If this is still an issue for you,
please provide the requested information and reopen it.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you
Marked as invalid, OP indicated they had resolved the issue.
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: cinder
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Marking this as invalid, it looks like the OP resolved their issue by
updating their configuration.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
Based on the limited information you've provided, this looks like a
configuration issue. If you need help configuring Keystone correctly,
please reach out to the OpenStack mailing list for support.
If this install worked previously and suddenly started displaying this
behavior, please feel free
Make sure you've got the latest version of oslo.messaging installed,
otherwise this is most likely a configuration issue. If you can get a
stack trace of the specific issue causing the timeout on the
oslo.messaging side, feel free to reopen this bug and provide that
information. Otherwise you can
I've added Horizon to this bug and am marking invalid since everything
appears to be working correctly in Nova. If there is an issue the Nova
team needs to address, please provide those details and feel free to
reopen this issue for Nova.
** Also affects: horizon
Importance: Undecided
Marking this bug as invalid for Nova. If this turns out to be a Nova
specific issue, please file a new bug with Nova specific information
(including reproduction steps) and reference this one.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because
It's been almost 3 months with no activity on this issue. I'm closing
this out as we don't have enough information to reproduce it. Please
feel free to reopen this bug or file a new one once you are able to
provide us with the additional information we've requested.
** Changed in: nova
Marking this as invalid for Nova per last comment.
** Changed in: nova
Status: Incomplete => 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/1561310
Title:
While I agree the message wording comes across awkward, the message is
vague by design to avoid revealing password information to the API
caller. There will be more useful information in your logs. If you are
unable to troubleshoot the issue after checking your logs and believe
this is a bug,
Thanks Michael! I'm going to close this out for Nova, and add this as an
issue to the doc team to update that documentation.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: nova
Status: Incomplete => Invalid
** Summary changed:
- Incorrect
This looks like it should be proposed as a spec.
More information about blueprints and specs available here:
https://wiki.openstack.org/wiki/Blueprints
For an example spec, see here: https://specs.openstack.org/openstack
/nova-specs/specs/ocata/template.html
** Changed in: nova
Status:
Closing this out as invalid because it's been incomplete for a few
months and we don't have enough information to reproduce or even
identify an issue to fix.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
** Changed in: nova
Status: Incomplete => Won't Fix
** Changed in: nova
Status: Won't Fix => 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/1542302
Marked as fix released, per OP's comment, a fix has been released for
python-novaclient that resolves this issue.
** Changed in: nova
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
We are seeing some bug reports coming in where users experience an
"Unexpected Exception" error when neutronclient fails. This is not
particularly helpful for anyone experiencing this issue and it would be
nice to have something more specific to aid in troubleshooting.
We
I see some errors in your api log that look like you should double check
your configuration (pasted below). Maybe see this bug and see if it's
relevant - https://bugs.launchpad.net/nova/+bug/1534273.
Once you've verified your config, if you still feel this is a valid bug, please
update the bug
*** This bug is a duplicate of bug 1534273 ***
https://bugs.launchpad.net/bugs/1534273
** Summary changed:
- It prompt:Error：Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID:
I moved this over to Kolla since this looks specific to that project and
I'm not working in that repo, so I can't reproduce this. If this turns
out to be a Nova specific issue, please update the bug with Nova-
specific reproduction steps and we'll take a look at it.
** Also affects: kolla
sed
** Changed in: nova
Assignee: (unassigned) => Augustina Ragwitz (auggy)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370496
Title:
Failed to establish authenticated ssh conn
nee: (unassigned) => Augustina Ragwitz (auggy)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1349617
Title:
SSHException: Error reading SSH protocol banner[Errno 104] Connection
reset by peer
Documentation that talks about allocation ratio need to be updated.
For instance, this:
http://docs.openstack.org/openstack-ops/content/compute_nodes.html#overcommit
Here is the added help text for the cli:
https://review.openstack.org/#/c/277953/11/nova/compute/resource_tracker.py
** Also
This is a feature request. If you'd like to move forward with using
4-byte unicode characters on the backend, please submit a spec for doing
so. If the issue is that the returned error is confusing and you'd like
that improved, that is a valid bug and this issue can be reopened with
that as the
the whole thing!
** Affects: nova
Importance: Medium
Assignee: Augustina Ragwitz (auggy)
Status: Confirmed
** Tags: testing
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (no
been replaced with u''.
Not sure if this is in nova itself or just the test framework, more
research needed.
I'm creating this bug to make sure I don't forget to come back and
troubleshoot this issue.
** Affects: nova
Importance: Medium
Assignee: Augustina Ragwitz (auggy)
Status:
Marked as invalid, this is a feature request.
** 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/1509304
Title:
Add
*** This bug is a duplicate of bug 1534273 ***
https://bugs.launchpad.net/bugs/1534273
** This bug has been marked a duplicate of bug 1534273
Keystone configuration options for nova.conf missing from Redhat/CentOS
install guide
--
You received this bug notification because you are a
Thanks for taking the time to report this issue! Please double check your setup
and try troubleshooting via support channels like #openstack on irc or mailing
lists. If you determine this isn't a configuration issue, please reopen this
bug and provide the following information:
- OS type and
Thanks for taking the time to file a bug! That message can be a little
misleading, unfortunately. Try troubelshooting your setup through
#openstack or the mailing list first. If you discover more information
that indicates this is a bug and not a configuration issue, then feel
free to update this
Thanks for taking the time to file a bug! Unfortunately this like a
configuration issue. Try searching the web for the error I pasted above
for articles that may offer solutions. You can also try our support
channels like the #openstack channel on irc.freenode.org or the mailing
list. If you
Thanks for taking the time to submit a bug! Unfortunately the error
message you get is a bit misleading. Please verify your configuration
and if you find something more specific that looks like a bug related to
this issue, feel free to reopen it by setting the Status as New.
** Changed in: nova
See http://docs.openstack.org/openstack-ops/content/flavors.html for an
explanation. The dashboard simulates editing a flavor by deleting the
old one and creating a new one, which is why the id changed. Your VM is
still associated with the original flavor because the original flavor
was never
Juno is EOL [1] so we aren't doing fixes for it anymore. I've cosed this
as invalid, but if you still have this issue in a later, supported
release, please feel free to reopen this issue and provide the updated
version details of your environment in the description.
References:
--
[1]
Juno is EOL [1] so we aren't doing fixes for it anymore. I've closed
this as invalid, but if you still have this issue in a later, supported
release, please feel free to reopen this issue and provide the updated
version details of your environment in the description.
References:
--
Juno is EOL [1] so we aren't doing fixes for it anymore. I've cosed this
as invalid, but if you still have this issue in a later, supported
release, please feel free to reopen this issue and provide the updated
version details of your environment in the description.
References:
--
[1]
*** This bug is a duplicate of bug 1526721 ***
https://bugs.launchpad.net/bugs/1526721
** Also affects: horizon
Importance: Undecided
Status: New
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1526721
The test "test_get_console_output_with_unlimited_size" doesn't live in
the Nova codebase and based on the path, it looks like it's in Tempest.
I checked http://ci-watch.tintri.com/project?project=nova and found one
change with the failure mentioned in this bug, but subsequent changes
passed
This looks like a configuration error. Please validate your config, make
sure the "compute_driver" line isn't commented out and contains the
correct driver for your VM. If this is not the case or you've validated
that this is indeed not a configuration option, please provide detailed
steps to
*** This bug is a duplicate of bug 1534273 ***
https://bugs.launchpad.net/bugs/1534273
If you were following the RDO installation docs, the nova configuration
is missing a few fields. Please see the following for the correct
configuration - https://bugzilla.redhat.com/show_bug.cgi?id=1219890
I looked into this and while Nova could revisit how it handles these
"API Errors" I don't see any obvious functionality issues. I have
however linked the openstack-manuals project because it looks like the
RDO manual might be missing Keystone configuration information. This is
based on the
*** This bug is a duplicate of bug 1534273 ***
https://bugs.launchpad.net/bugs/1534273
** This bug has been marked a duplicate of bug 1534273
Keystone configuration options missing from Redhat/CentOS install guide
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
When running GENERATE_SAMPLES=True tox -e functional, the
GENERATE_SAMPLES value is still set to False (the default). I also tried
setting it in my session before running tox and still got False.
To reproduce:
Add a line to api_sample_base.py [1] to print the value of
72 matches
Mail list logo
