This is not a charm bug, its a limitation/bug in the way that nova
handles the BDM devices.
** 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).
This does not appear to be a charm issue, but rather it appears to
potentially be a nova issue. I can confirm that setting the
rx_queue_size and tx_queue_size results in the nova.conf file being
updated by the charm, but that the resulting hard rebooted guest does
not get the tx_queue_size, only
Agree that this likely isn’t a charm issue. I’ll mark invalid for now,
but feel free to reopen if evidence suggests otherwise.
** Changed in: charm-designate
Status: New => Invalid
** Changed in: charm-designate
Status: Invalid => Incomplete
--
You received this bug notification
Marking charm tasks as invalid on this particular bug as these aren't
related to the charms and were chased down to other components.
** Changed in: charm-nova-compute
Status: New => Invalid
** Changed in: openstack-bundles
Status: New => Invalid
--
You received this bug
Queens and Rocky are both extended maintenance and have had the proposed
patches merged. Updating tasks to mark as fix released.
** Changed in: nova/rocky
Status: New => Fix Released
** Changed in: nova/queens
Status: New => Fix Released
--
You received this bug notification
** Description changed:
- it was working in queens but fails in train. nova compute at the target
- aborts with the exception:
+ [Impact]
+
+ Live migration of instances in an environment that uses neutron backends
+ that do not support multiple port bindings will fail with error
+
Further discussion with Jeff indicated that replacing the { and } with (
and ) resolved the issue.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
Since this doesn't appear to be an issue with the charms, I'm going to
remove the project from being affected by this bug and the field
critical designation. However, feel free to re-add it should evidence
present itself otherwise.
** No longer affects: charm-neutron-api
--
You received this
** Also 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/1820612
Title:
Logging is hard to read if there is a
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
** Also affects: horizon (Ubuntu)
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/1613900
Title:
Unable to use 'Any'
** Also affects: cloud-archive
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/1613900
Title:
Unable to use 'Any'
Public bug reported:
[Issue]
After rebooting a 16.04 AWS instance (ami-1d4e7a66) with several
external disks attached, formatted, and added to /etc/fstab - systemd
mount targets fail to mount with:
● media-v.mount - /media/v
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active:
** Also affects: cloud-archive
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/1668410
Title:
[SRU] Infinite loop trying to delete deleted HA
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
I saw this last night, and can indeed confirm its related to DNS issues.
It was suggested by a colleague that it may be related to the sudo call
returning an error indicating that the hostname could not be found,
though I spent no time exploring this option today. Restarting the
openvswitch-switch
Based on Brad's comment in #9, there were actions that were missing for
the openstack orchestration service. I believe this to no longer be a
valid bug, therefore I'm marking remaining tasks as invalid.
** Changed in: python-openstackclient
Status: New => Invalid
** Changed in: keystone
Public bug reported:
OpenStack service endpoints are created for the heat service, but the
openstack client cannot find the endpoints to issue the query against. I
suspect this is due to the domain auth tokens included in the initial
authentication doesn't include any endpoints with the
Uploading debdiff based on what is currently available in trusty-
proposed since that has been verified and pending release.
** Description changed:
+ [Impact]
+
We have customers that typically add a few hundred security group rules
or more. We also typically run 30+ VMs per compute node.
Public bug reported:
Maintaining the user token list and the revocation list in the memcached
persistence backend (kvs) is inefficient for larger amounts of tokens
due to the use of a linear algorithm for token list maintenance.
Since the list is unordered, each token within the list must be
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Also affects: nova (Ubuntu)
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/1554227
Title:
DHCP unicast requests are not
Marking this is confirmed against the Ubuntu Cloud Archive for Kilo,
Juno, and Trusty which are still supported from the Ubuntu perspective
and is known not to include the os-brick library dependencies.
Certainly, the testing for the change to os-brick needs to be verified
that the problem is
** Also affects: cloud-archive
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/1374999
Title:
iSCSI volume detach does not
This fix was made available in 1:2014.2.4-0ubuntu1~cloud4 of nova in the
Ubuntu Cloud Archive for Juno.
** Changed in: cloud-archive/juno
Status: In Progress => Fix Committed
** Changed in: cloud-archive/juno
Status: Fix Committed => Fix Released
--
You received this bug
be examined in a worst case scenario. The added
performance overhead is an order of magnitude in difference (~.5 seconds
versus ~.05 seconds at 1500 ports).
** Affects: neutron
Importance: Undecided
Assignee: Billy Olsen (billy-olsen)
Status: In Progress
** Changed in: neutron
27 matches
Mail list logo
