[Bug 1927868] Re: vRouter not working after update to 16.3.1
@Rodolfo, We still aren't 100% certain that this particular change is the culprit but it's highly suspect because of the nature of the change compared to other commits. In this ticket you have at least 4 instances of this bug being reproducible by different people including Ubuntu maintainers and several Cloud Operators that had entire clouds go completely offline and had to roll back to previous version of Ussuri AND Train. We're now all in holding patterns and unable to upgrade to this version or beyond as long as this code exists. I do believe that there could be something specific to Ubuntu deployments and this code as I see that this change was triggered by a RHEL bug ticket, so maybe the change fixed a problem for RHEL deployments but broke things for Ubuntu deployments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
@Christian, sorry if it wasn't clear but I don't believe this is database migration related. @Rodolfo, At the very least the code that was written with timeout=3 is likely problematic and should have been at least made user configurable. It's quite possible this change is the culprit and breaks Ubuntu deployments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Our order of operations went as such: - All packages get updated to latest available Ussuri (16.3.1) for Bionic via apt-get dist-upgrade - Stop services (systemctl stop neutron-dhcp-agent; systemctl stop neutron-metadata-agent; systemctl stop neutron-ovs-cleanup; systemctl stop neutron-l3-agent; systemctl stop neutron-openvswitch-agent; systemctl stop neutron-server) - Upgrade database (neutron-db-manage current; neutron-db-manage upgrade heads) - Start services back up (systemctl start neutron-dhcp-agent; systemctl start neutron-metadata-agent; systemctl start neutron-ovs-cleanup; systemctl start neutron-l3-agent; systemctl start neutron-openvswitch-agent; systemctl start neutron-server) - All L3 agents for all routers elect to be down - Rebooted control plane several times while troubleshooting, L3 agents stay down - Found that 16.3.2 was available on staging repository, installed it, all L3 agents go to standby - Install 16.0.0 for Focal (all I could find during my scramble to fix the outage), L3 agents start to elect a master for each router - Later that week, re-attempt 16.3.1, all L3 agents go to standby - Find 16.2.0 for Bionic and downgrade to it, all L3 agents begin to elect masters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Ante: Thank you for the link to the 16.3.0 packages. We managed to find 16.2.0 before your post and are currently using them and it seems to be working fine for us. Should the opportunity arise we will install 16.3.0 since we've downloaded the deb files just in case. Billy: I guess the hunt continues for which commit introduced the bug, but I do see that this change '590551d' is a result of the following bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1929829 where this operator was complaining that his L3 agents would not enter active state. Coincidentally it may have fixed the issue for them, but introduced a bad bug on the Ubuntu side of things. Corey: It's reassuring that you were able to reproduce this bug. Thank you for your efforts! ** Bug watch added: Red Hat Bugzilla #1929829 https://bugzilla.redhat.com/show_bug.cgi?id=1929829 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Hey Ubuntu team, Is there any way for you to provide the Neutron 16.3.0 packages for Bionic? We are in emergency mode here and the current 16.0.0 we are running, although working better than 16.3.1 is causing major control plane instability. We are in desperate need of 16.3.0 packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
OK, I did find evidence that this issue did begin to happen as we upgraded our Train packages just before we upgraded to Ussuri (I believe its best practice to update all packages, THEN upgrade to a new version of OpenStack) Upgraded Neutron 15.3.0 to 15.3.3 at 16:40 EDT 2021-06-10 16:40:40 upgrade neutron-l3-agent:all 2:15.3.0-0ubuntu1~cloud2 2:15.3.3-0ubuntu1~cloud0 Evidence of gateway problems at 17:06 EDT (Might have seen this in the logs several minutes earlier but I had to purge a lot of logs from that day because of the sheer volume of them) 2021-06-10 17:06:23.440 33440 ERROR neutron.agent.l3.ha_router [-] Gateway interface for router 04a5a2c3-739f-4cf6-94bb-dd314c2a8e66 was not set up; router will not work properly Upgraded from latest Train to latest Ussuri happened at 17:12 2021-06-10 17:12:31 upgrade neutron-l3-agent:all 2:15.3.3-0ubuntu1~cloud0 2:16.3.1-0ubuntu1~cloud0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
keepalived: 1:1.3.9-1ubuntu0.18.04.2 from: http://archive.ubuntu.com/ubuntu bionic-updates/main neutron-l3-agent.log filled with the following log lines for every single router in our cluster: 2021-06-10 19:59:53.602 328191 ERROR neutron.agent.l3.ha_router [-] Gateway interface for router 9f276b0e-8581-4312-8780-ff4503c3df07 was not set up; router will not work properly We have 3 controllers and use l3 HA and usually have 1 l3 agent per controller, 2 standby, 1 active. We rolled back to 16.0.0 (only because we could not find 16.3.0 anywhere) and the issue stopped. OP was able to roll back to 16.3.0 and said the issue went away so I think we should focus on 16.3.1+ Before upgrading to Ussuri we did briefly upgrade to the latest Train packages, give me some time to see if I can see if those error messages started when we were briefly on latest Train packages. I need to do some cross-referencing for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
590551d [L3][HA] Retry when setting HA router GW status. I'm not a developer but this change does reflect the log error messages myself and the OP are seeing. https://github.com/openstack/neutron/commit/8f5a801270f81bd9fe3559fee9c1714c97849b3e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
I was not able to roll back to 16.3.0 because they are not on any repositories that I could find so I had to manually download neutron debian files for focal and thankfully they seem to kind of work on Bionic Ussuri. We are now running 16.0.0~b3~git2020041516.5f42488a9a- 0ubuntu2 which is not ideal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
I don't think so. We don't even use DVR. Our observations were basically identical to OP's which was a telltale log entry 'Gateway interface for router 02945b59-639b-41be-8237-3b7933b4e32d was not set up; router will not work properly' and also that any Layer-3 agents for a router all remained in a standby state. None of them would ever go active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
This bug appears to be present in 16.3.2 in the proposed repository as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
This is a terrible bug. 16.3.1 needs to be pulled from the repositories immediately. This will cause all Ussuri OpenStack deployments on Bionic to be completely down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845246] Re: Failed to import plugin clustering
Installed python3-senlinclient from stein-proposed root@lab-controller:~# apt-cache policy python3-senlinclient python3-senlinclient: Installed: 1.9.0-0ubuntu1~cloud0 Candidate: 1.9.0-0ubuntu1~cloud0 Version table: *** 1.9.0-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-proposed/stein/main amd64 Packages 100 /var/lib/dpkg/status 1.7.0-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages Cluster warning is now gone! root@lab-controller:~# openstack image list +--+-++ | ID | Name| Status | +--+-++ | d3de179b-96b6-4cb5-835d-a36d3d1a6169 | cirros-good | active | +--+-++ root@lab-controller:~# openstack network list +--+---+--+ | ID | Name | Subnets | +--+---+--+ | 0f93a695-7a26-4835-903c-f7c55aceba17 | collaboratory_network | 2ba49081-89b4-4cc3-9189-ee4d46550b60 | | 1513a1a7-df84-448e-ae7e-8e6ec4fbe328 | cheeseburgers | 4badc741-5d50-4fc4-a600-b47b69ecee8e | | 5d2fa413-6ce5-43d4-aa2d-646025185eb8 | lab_network | 4ef39d3f-2e81-424b-89c7-611979c9aaa1 | +--+---+--+ Thank you Corey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845246 Title: Failed to import plugin clustering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1845246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845246] Re: Failed to import plugin clustering
Hi Corey, Looks like python3-senlinclient is already installed (but we dont use senlin). I would remove it but it wants to pull out all the openstack heat packages, which we use. root@lab-controller:~# dpkg -l | grep -i python3 | grep -i client ii python3-amqp 2.4.0-1~cloud0 all Low-level AMQP client (Python3 version) ii python3-aodhclient1.0.0-0ubuntu1 all OpenStack Alarming as a Service - Python 3.x client ii python3-barbicanclient4.6.0-0ubuntu1 all OpenStack Key Management API client - Python 3.x ii python3-blazarclient 2.1.0-0ubuntu1~cloud0 all OpenStack Reservation Service API client - Python 3 ii python3-ceilometerclient 2.9.0-0ubuntu1 all Client library for Openstack Ceilometer API server - Python 3.x ii python3-cinderclient 1:4.1.0-0ubuntu1~cloud0 all Python bindings to the OpenStack Volume API - Python 3.x ii python3-designateclient 2.9.0-0ubuntu1 all client library for the OpenStack Designate API - Python 3.x ii python3-glanceclient 1:2.16.0-0ubuntu1~cloud0 all Client library for Openstack glance server - Python 3.x ii python3-gnocchiclient 7.0.1-0ubuntu1 all bindings to the OpenStack Gnocchi API - Python 3.x ii python3-heatclient1.17.0-0ubuntu1~cloud0 all client library and CLI for OpenStack Heat - Python 3.x ii python3-httplib2 0.9.2+dfsg-1ubuntu0.1 all comprehensive HTTP client library written for Python3 ii python3-keystoneclient1:3.19.0-0ubuntu1~cloud0 all client library for the OpenStack Keystone API - Python 3.x ii python3-magnumclient 2.8.0-0ubuntu1 all client library for Magnum API - Python 3.x ii python3-manilaclient 1.27.0-0ubuntu1~cloud0 all OpenStack shared file system as a service - Python 3.x client ii python3-memcache 1.59-1~cloud0 all pure Python memcached client - Python 3.x ii python3-mistralclient 1:3.3.0-0ubuntu1 all OpenStack Workflow as a Service client - Python 3.x ii python3-monascaclient 1.14.0-0ubuntu1~cloud0 all client bindings for the Monasca API - Python 3.x ii python3-neutronclient 1:6.7.0-0ubuntu1 all client API library for Neutron - Python 3.x ii python3-novaclient2:13.0.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - 3.x ii python3-octaviaclient 1.8.0-0ubuntu1~cloud0 all Octavia client for OpenStack Load Balancing - Python 3.x ii python3-openstackclient 3.18.0-0ubuntu1~cloud0 all OpenStack Command-line Client - Python 3.x ii python3-os-client-config 1.29.0-0ubuntu1 all OpenStack client configuration library - Python 3.x ii python3-osc-lib 1.12.1-0ubuntu1~cloud0 all OpenStackClient Library - Python 3.x ii python3-pymemcache1.3.2-3 all comprehensive, fast, pure Python memcached client - Python 3.x ii python3-saharaclient 2.2.0-0ubuntu1~cloud0 all Client library for Openstack Sahara API server - Python 3.x module ii python3-senlinclient 1.7.0-0ubuntu2 all OpenStack Clustering API Client Library - Python 3.x ii python3-statsd3.2.1-2 all Python client for the statsd daemon (Python 3) ii python3-suds 0.7~git20150727.94664dd-5 all Lightweight SOAP client for Python - Python 3.x ii python3-swiftclient 1:3.7.0-0ubuntu1~cloud0 all Client library for Openstack Swift API - Python 3.x ii python3-troveclient 1:2.14.0-0ubuntu1 all Client for OpenStack Database as a Service - Python 3.x ii python3-zaqarclient 1.9.0-0ubuntu1 all OpenStack Zaqar Queueing API, client and library - Python 3.x root@lab-controller:~#
[Bug 1845246] [NEW] Failed to import plugin clustering
Public bug reported: When running any openstack client command I am provided with the following error, including the correct output of the command. Example: openstack image list WARNING: Failed to import plugin clustering. +--+-++ | ID | Name| Status | +--+-++ | e7180a98-9630-4128-a457-48b272d819bb | cirros | active | | d3de179b-96b6-4cb5-835d-a36d3d1a6169 | cirros-good | active | +--+-++ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 openstack --version WARNING: Failed to import plugin clustering. openstack 3.18.0 dpkg -l | grep python3-openstackclient ii python3-openstackclient 3.18.0-0ubuntu1~cloud0 all OpenStack Command-line Client - Python 3.x ** Affects: python-openstackclient (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845246 Title: Failed to import plugin clustering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1845246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659620] Re: Panels get broken with COMPRESS_OFFLINE = True
Running Ubuntu 18.04 with openstack-dashboard 14.0.3-0ubuntu1~cloud0 and having issues with certain modals not working (create object container, create keypair, upload keypair, create server group) all popping up as blank modals. This has been a chronic issue for us for Ubuntu 16.04 and also 18.04 spanning multiple OpenStack releases but when we first upgraded to Rocky these issues were gone. We did not seem to have any issues with openstack-dashboard 14.0.2-0ubuntu4~cloud0 and this was very surprising to see however we recently upgraded to 14.0.3-0ubuntu1~cloud0 and we are now having these issues with broken modals again. The problem seems to be related to what your memcached configuration is in /etc/openstack-dashboard/local_settings.py although I have not been able to pinpoint what exactly is the relationship between memcached and the collectstatic/compress operations building good or bad javascript. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659620 Title: Panels get broken with COMPRESS_OFFLINE = True To manage notifications about this bug go to: https://bugs.launchpad.net/designate-dashboard/+bug/1659620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666853] Re: grub-probe fail when fs is larger than 2tb
Possibly related bugs: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411 https://bugs.launchpad.net/cloud-utils/+bug/1762748 We run an OpenStack cloud and provide very large instances to our users and noticed that there was possibly a breaking change made in 1762748 which resulted in my new bug submission 1812411. I'd be happy to help test this issue as it is easily reproducible in my environment. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666853 Title: grub-probe fail when fs is larger than 2tb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1666853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812411] Re: cloud-init corrupting grub
Hi Scott, Yes probably related bugs for sure. Again, I'd be happy to help test a fix if one is developed as I'm able to easily reproduce this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812411 Title: cloud-init corrupting grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812411] [NEW] cloud-init corrupting grub
Public bug reported: I believe I have discovered problems in the *recent builds* of Ubuntu 14.04 and 16.04 (NO ISSUE with 18.04 or OLDER 14.04/16.04 builds) cloud images (https://cloud-images.ubuntu.com/) for instances with very large local disks. We are using OpenStack Queens on Ubuntu 16.04 and have noticed that when our users deploy our largest instance type with ~5TB local disk that the VM deploys but when that VM is rebooted for the first time it wont boot and becomes stuck at the 'grub rescue' prompt with 'error: unknown filesystem.'. I believe the issue is happening in the growpart function of cloud-init of the first boot of the VM to grow the root partition to fit the large local disk. I have attached as much logging and output information from 14.04, 16.04 and 18.04 but I do not have a developer background so I can't pinpoint the issue entirely. I am able to easily reproduce this issue and would happy to help with the resolution of this bug in any capacity. Thank you! ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-logs-screenshot.zip" https://bugs.launchpad.net/bugs/1812411/+attachment/5230331/+files/ubuntu-logs-screenshot.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812411 Title: cloud-init corrupting grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
I did a bit more investigating and it seems to me like the contents of the defined memcached server can influence the generation of the javascript in '/var/lib/openstack-dashboard/static/dashboard/js' Is that assumption correct? If so, maybe the collect/compress should flush the memcached contents? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
Hey Corey,
I believe I have found the source of my problem with bad javascript
being generated at the compress and collect static stage and it has to
do with whats in my /etc/openstack-dashboard/local_settings.py,
specifically my memcached section. We run 3 controllers and 3 instances
of memcached. If we configure our local_settings.py with the 3 memcached
servers, bad javascript is generated at the compress and collectstatic
stage. If we just use a single memcached server, the javascript
generation is just fine. Any idea why this might be? Is our syntax for
the cache stanza incorrect? There's no examples provided on the
OpenStack site on how multiple memcached servers would look in terms of
syntax. Either way, even the 'bad' stanza as written below seems to work
in our lab (in terms of javascript generation)
GOOD:
SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': '172.25.4.17:11211',
},
}
BAD:
SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION':
['172.25.4.17:11211','172.25.4.18:11211','172.25.4.19:11211'],
},
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775170
Title:
[SRU] Fixing empty create swift container dialog after upgrading
horizon from newton to ocata
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
I don't think it's necessary to go through the process of a pike -> queens upgrade to reproduce the issue. Reason I say that is because we can take our current install and purge & install the openstack-dashboard & related packages and without our customizations we still experience the problem. That being said we are unable to reproduce this issue from a fresh install in our lab environment by taking a fresh ubuntu 16.04 install and layering on the openstack packages. This has been good and bad. Bad because we are unable to reproduce the issue in our lab. Good because we can take this working environment and copy the dynamically generated javascript files from '/var/lib/openstack- dashboard/static/dashboard/js' to our production environment so that the create container modal works properly. Is there any way to get a more verbose output from the generation (collectstatic and compress) of those javascript files to see where it might be breaking? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
Just to be clear, I've tried removing the following directories rm -rf /usr/share/openstack-dashboard/ rm -rf /var/lib/openstack-dashboard/static/ followed by an apt-get install --reinstall openstack-dashboard python- django-horizon Leaving the dashboard uncustomized, I am still getting a blank create container window. Chrome developer console when loading '/project/containers/' shows: Uncaught SyntaxError: Invalid or unexpected token for 95f4db675ac3.js:1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
We implement the following customizations of the openstack-horizon dashboard: - /usr/share/openstack-dashboard/openstack_dashboard/templates/_login_footer.html - /usr/share/openstack-dashboard/openstack_dashboard/templates/_footer.html - /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/logo.svg - /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/logo-splash.svg We serve the openstack dashboard out of '/' instead of Ubuntu's default of '/horizon' and we do so by modifying the following: - /etc/openstack-dashboard/local_settings.py WEBROOT = '/' LOGIN_URL = WEBROOT + 'auth/login/' LOGOUT_URL = WEBROOT + 'auth/logout/' - /etc/apache2/conf-available/openstack-dashboard.conf WSGIScriptAlias / /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi process-group=horizon Alias /static /var/lib/openstack-dashboard/static/ Alias /horizon/static /var/lib/openstack-dashboard/static/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
This particular bug of the container creation modal being blank has plagued us for several OpenStack releases now. We are running Queens on Ubuntu 16.04 currently (http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/queens/main amd64 Packages) python-django-horizon 3:13.0.1-0ubuntu2~cloud0 We are essentially seeing the same (or at least similar) problem. When we run python manage.py collectstatic -c && python manage.py compress some of the dynamicly generated javascript files are incomplete/truncated and causes this container creation modal to be blank. We have no idea whats causing the javascript to be generated in an incomplete way and has been very difficult for us to reproduce in a lab environment. This issue is mostly unique to our production environment however in the past we have been able to create this issue in the lab (this was probably on ocata). Does anyone have any guidance on this? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775862] Re: Missing Magnum-UI package for Ubuntu 16.04
Are there any plans to release magnum-ui as part of the Ubuntu cloud archive repository? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775862 Title: Missing Magnum-UI package for Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1775862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762748] Re: Larger than 2 TB disks not possible
I have tested cloud-guest-utils version 0.27-0ubuntu25.1 and it appears to allow instances with disks larger than 2TB to be deployed properly. My testing was to deploy an instance with a small root disk, then install the patched cloud-guest-utils on to the instance. I would then take a snapshot of the instance and re-deploy it as a larger VM with a >2TB root disk. I hope to see this patched version of cloud-guest-utils pushed to the Xenial ubuntu cloud images soon :) Thank you very much for your work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762748 Title: Larger than 2 TB disks not possible To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1762748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
@Gael from what I can tell the fix has not been released based on this bug status is still 'in progress'. I'm running Ubuntu 16.04 with vlan 1.9-3.2ubuntu1 and it still contains the 'ip link set up dev $IF_VLAN_RAW_DEVICE' on line 63 of /etc/network /if-pre-up.d/vlan . You can modify the file yourself using Dan's instructions on step 9. Works like a charm for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
