This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This needs to change the API response, so we need bump a new
microversion. And we need a nova-spec for this kind of API change. But
this is very low priority
** Changed in: nova
Status: In Progress => Confirmed
** Changed in: nova
Importance: Low => Wishlist
** Changed in: nova
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
Fix Released in Ocata:
https://review.openstack.org/#/c/349959/
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This bug was fixed in the package nova - 2:13.1.3-0ubuntu2
---
nova (2:13.1.3-0ubuntu2) xenial; urgency=medium
* Fix exception due to BDM race in get_available_resource() (LP: #1602057)
- d/p/fix-exception-due-to-bdm-race-in-get_available_resou.patch
-- Edward Hope-Morley
Reviewed: https://review.openstack.org/465125
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=37b84c4c7375302e331fd4d779a732fa18cb09c8
Submitter: Jenkins
Branch:master
commit 37b84c4c7375302e331fd4d779a732fa18cb09c8
Author: Matt Riedemann
Date:
Public bug reported:
The enabled files for the developer dashboard and theme preview panel
have been moved to contrib so the documentation should be updated.
https://docs.openstack.org/developer/horizon/topics/styling.html#theme-
preview-page
** Affects: horizon
Importance: Low
Reviewed: https://review.openstack.org/458954
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=0392b36a0d7d3e7cc479b357245da04c949924de
Submitter: Jenkins
Branch:master
commit 0392b36a0d7d3e7cc479b357245da04c949924de
Author: Kristi Nikolla
Date:
** Changed in: keystone/ocata
Status: Fix Committed => Fix Released
--
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/1662762
Title:
Authentication for LDAP
Public bug reported:
Steps to reproduce:
openstack server create --flavor m1.tiny --security-group default --image
cirros-0.3.5-x86_64-disk myinstance
$ openstack server add security group myinstance default
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and
attach
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** No longer affects: cloud-init (Ubuntu)
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init
Status: Confirmed => Fix
This was reverted -
https://github.com/openstack/keystone/commit/4a82ab9065a659bbcb838240da113a0509f651aa
** Changed in: keystone
Status: Fix Released => In Progress
** Changed in: keystone
Milestone: pike-1 => None
--
You received this bug notification because you are a member of
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
Like 1800 881 9970 Hp printer customer service phone number 1800 881 9970 HP
laser printer support Like 1800 881 9970 Hp printer customer service phone
number 1800 881 9970 HP laser printer support Like 1800 881 9970 Hp printer
customer service phone number 1800 881
** Changed in: keystone
Status: In Progress => Fix Released
** Changed in: keystoneauth
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
Free 1800 881 9970 Hp printer customer service phone number Free 1800 881 9970
Hp printer customer service phone number Free 1800 881 9970 Hp printer
customer service phone number Free 1800 881 9970 Hp printer customer service
phone number Free 1800 881 9970 Hp
Public bug reported:
http://logs.openstack.org/20/464020/5/check/gate-tempest-dsvm-neutron-
linuxbridge-ubuntu-xenial/a4d35a8/logs/testr_results.html.gz
Traceback (most recent call last):
File "tempest/api/network/test_dhcp_ipv6.py", line 230, in
test_dhcpv6_64_subnets
subnet_slaac =
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
Help 1881 881 9970 Hp printer customer service phone number Help 1881 881 9970
Hp printer customer service phone number Help 1881 881 9970 Hp printer
customer service phone number Help 1881 881 9970 Hp printer customer service
phone number
Hp printer customer service
This change affects keystone but I think it makes sense to only track
the fix against the oslo.cache library. There isn't much keystone can do
for this fix since the options are generated from oslo.cache and
rendered in the sample configuration file.
Improvement to the configuration option help
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
1+8+0+0 560 4135 mac Apple customer service number 1800 560 4135 mac
Apple support phone number
1+8+0+0 560 4135 mac Apple customer service number 1800 560 4135 mac
Apple support phone number
1+8+0+0 560 4135 mac Apple customer service number 1800 560 4135 mac
Apple
Tenants are able to delete most ports on a network they own, including
the dhcp ports, but excluding the router ports (must use router-
interface-delete for that). If they couldn't then a net-create/net-
delete would fail since the DHCP port is auto-allocated at creation
time.
** Changed in:
Public bug reported:
Description
===
If an instance has had an attached volume volume-updated twice in a
"round-trip" - ie, volume-update $vol1 $vol2, then volume-update $vol2
$vol1 - it cannot be live-migrated.
Steps to reproduce
==
1. Create two iscsi volumes.
#
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
DeeP 1800 560 4135 mac Apple customer service number 1800 560 4135 mac Apple
support phone number
DeeP 1800 560 4135 mac Apple customer service number 1800 560 4135 mac Apple
support phone number
DeeP 1800 560 4135 mac Apple customer service number 1800 560 4135 mac Apple
Public bug reported:
Xen's console is attached to hvc0 in PV guests [1]. If an image does set
it up on its grub configuration, the instance may not boot properly.
Nova could set the os_cmdline for that guest as it is doing for other
hypervisors (for example for LXC), adding the console setup
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
ervice number 1800 560 4135 mac Apple support phone number
FuDDu 1800 560 4135 mac help number 1800 560 4135 apple mac customer support
number
ervice number 1800 560 4135 mac Apple support phone number
FuDDu 1800 560 4135 mac help number 1800 560 4135 apple mac customer
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Seen here:
http://logs.openstack.org/59/383859/22/experimental/gate-tempest-dsvm-
neutron-pg-full-ubuntu-
xenial/b2f29e9/console.html.gz#_2017-04-21_14_20_13_438646
NOTE: THIS DOES NOT APPEAR TO BE CAUSED BY POSTGRESQL AT ALL, IT'S A
TIMING ISSUE
This test is creating two
Private bug reported:
macbook pro tech support phone number
macbook pro customer support phone number
macbook pro technical support phone number
macbook pro support number
macbook pro customer service phone number
Apple customer number
Apple customer support number
Apple customer care number
Public bug reported:
Description
===
QEMU support a number of different backends for code generation.
Qemu with the TCG(tiny code generator) backend does not support
cpu affinity. the TCG backened is used when the nova
virt_type is set to qemu.
Currently by default when we
request a
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Project changed: nova => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Private bug reported:
HelpDesK:=18005604135==) MAC support phone number MAC phone number
HelpDesK:=18005604135==) MAC support phone number MAC phone number
HelpDesK:=18005604135==) MAC support phone number MAC phone number
HelpDesK:=18005604135==) MAC tech support phone number MAC phone number
Private bug reported:
18005604135==) MAC support phone number MAC phone number
HelpDesK:=18005604135==) MAC support phone number MAC phone number
HelpDesK:=18005604135==) MAC tech support phone number MAC phone number
HelpDesK:=18005604135==) MAC tech support phone number MAC phone number
Public bug reported:
As reported by user niluje, the ifi the initramfs tools write a config
that has static networking, then cloud-init would not populate the
address field in its rendered network config (_klibc_to_config_entry).
The result would be incomplete or invalid configuration, and
Public bug reported:
Description:
Due to overload situation in our storage one NFS mount went into stale mode.
All other mount points where accessible and working.
Deletion of a VM on this hypervisor was not possible since nova-compute wasn't
reactive.
The agent was flagged as:
>
Public bug reported:
We believe that each test should not depend on other tests.
python -m testtools.run neutron.tests.tempest.scenario.test_floatingip
Ran 4 tests in 139.164s
OK
python -m testtools.run
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSameNetwork.test_east_west
** Also 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/1599225
Title:
Can't create volume from volume
Public bug reported:
After the ocata upgrade we are seeing some errors while authenticating
users using v2 api and ec2 credentials
Same as reported in here:
https://ask.openstack.org/en/question/106557/swift3s3-api-errors-when-authenticating-with-ec2-keys/
2017-05-11 16:05:22.453 6081 INFO
** Changed in: nova
Status: Triaged => Opinion
** Changed in: nova
Importance: Low => Wishlist
--
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/1579876
Title:
Setting to invalid, as unable to reproduce in newton/ocata
** Changed in: horizon
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
This already fixed by this feature patch
https://review.openstack.org/#/c/415142/
** 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).
Public bug reported:
Using "neutron port-delete /" command, user is able to
delete the port whose device-type is "network:dhcp".
When user tries to delete the port whose device type is "network:dhcp",
neutron-server is allowing to delete that port and later it is re-creating the
same port with
Reviewed: https://review.openstack.org/464589
Committed:
https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c5e36a29662e82713084b6dbea21c69545664edc
Submitter: Jenkins
Branch:master
commit c5e36a29662e82713084b6dbea21c69545664edc
Author: Rodolfo Alonso Hernandez
Public bug reported:
The content of keystone/api-ref/source/v3/samples/admin/get-role-
inferences-response.json is as below:
{
"role_inference": {
"prior_role": {
"id": "7ceab6192ea34a548cc71b24f72e762c",
"links": {
"self":
Public bug reported:
The resolv.conf gets populated with whatever the last interface that
came up over DHCP provided.
Even if the 2nd network/subnet in neutron doesn’t define DNS, it still
overwrites resolv.conf.
By default the dnsmasq agent will use itself, and it's pairs as DNS servers if
no
** Project changed: neutron => networking-ovn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1689880
Title:
The "neutron_sync_mode = repair" option breaks the whole cloud!
Status in
74 matches
Mail list logo