[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
... after discussing with IBM ** Changed in: openstack (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-z-systems Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Attachment removed: "sosreport-part-10" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804032/+files/sosreport.LP1644785-part-10 ** Attachment removed: "sosreport-part-11" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804033/+files/sosreport.LP1644785-part-11 ** Attachment removed: "sosreport-part-12" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804034/+files/sosreport.LP1644785-part-12 ** Attachment removed: "sosreport-part-13" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804035/+files/sosreport.LP1644785-part-13 ** Attachment removed: "sosreport-part-14" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804036/+files/sosreport.LP1644785-part-14 ** Attachment removed: "sosreport-part-15" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804037/+files/sosreport.LP1644785-part-15 ** Attachment removed: "sosreport-part-02" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805322/+files/sosreport.LP1644785-part-02 ** Attachment removed: "sosreport-part-04" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805323/+files/sosreport.LP1644785-part-04 ** Attachment removed: "sosreport-part-05" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805324/+files/sosreport.LP1644785-part-05 ** Attachment removed: "sosreport-part-06" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805325/+files/sosreport.LP1644785-part-06 ** Attachment removed: "sosreport-part-07" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805326/+files/sosreport.LP1644785-part-07 ** Attachment removed: "sosreport-part-08" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805327/+files/sosreport.LP1644785-part-08 ** Attachment removed: "sosreport-part-15" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805334/+files/sosreport.LP1644785-part-15 ** Attachment removed: "sosreport-part-14" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805333/+files/sosreport.LP1644785-part-14 ** Attachment removed: "sosreport-part-13" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805332/+files/sosreport.LP1644785-part-13 ** Attachment removed: "sosreport-part-12" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805331/+files/sosreport.LP1644785-part-12 ** Attachment removed: "sosreport-part-11" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805330/+files/sosreport.LP1644785-part-11 ** Attachment removed: "sosreport-part-10" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805329/+files/sosreport.LP1644785-part-10 ** Attachment removed: "sosreport-part-09" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4805328/+files/sosreport.LP1644785-part-09 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Attachment removed: "sosreport-part-05" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4786475/+files/sosreport.LP1644785-part-05 ** Attachment removed: "sosreport-part-05" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804027/+files/sosreport.LP1644785-part-05 ** Attachment removed: "sosreport-part-06" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804028/+files/sosreport.LP1644785-part-06 ** Attachment removed: "sosreport-part-07" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804029/+files/sosreport.LP1644785-part-07 ** Attachment removed: "sosreport-part-08" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804030/+files/sosreport.LP1644785-part-08 ** Attachment removed: "sosreport-part-09" https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+attachment/4804031/+files/sosreport.LP1644785-part-09 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
As I'm looking at the data some more, I see in the sos reports provided that there may be heavy pressure for the async I/O and that may actually be what's causing the problems here. In the syslog, I see the following events getting reported from multipathd soon after the the device is discovered (its part of the udev event hooks I believe): Jan 12 22:02:49 ub01 multipathd[179286]: sdch: add path (uevent) Jan 12 22:02:49 ub01 multipathd[179286]: io_setup failed Jan 12 22:02:49 ub01 multipathd[179286]: uevent trigger error The io_setup is a system call into the kernel which can fail for a few different reasons, but one of the reasons it will fail is if the number of async io requests are greater than the current amount. It will error out with an EAGAIN, but there's explicit documentation in the multipath that one of the reasons that the io_setup may fail in this case is due to the settings of the fs.aio-nr-max, which is essentially the maximum number of events for all currently active aio contexts. Checking the value collected I see these values: # Quick check on the box today fs.aio-max-nr = 65536 fs.aio-nr = 124928 # From the sosreport provided on 12/01 fs.aio-max-nr = 65536 fs.aio-nr = 131072 As you can see the aio-nr is well above the aio-max-nr. I'm not entirely sure what is causing this, but there are a large number of async io events queued up. I think the plan of action should be to: a) configure multipath to ignore the iscsi devices presented between cinder and nova b) cleanup any errors in the current paths used by multipath, so that we know that disk i/o to the actul backend is not an issue c) Possibly consider increasing the fs.aio-max-nr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
I too noticed the: Nov 23 03:17:47 ub01 multipathd[179286]: io_setup failed Nov 23 03:17:47 ub01 multipathd[179286]: uevent trigger error Errors - and they continue to persist in recent recreate attempts. I think it would be good to configure multipath such that the devices provided by Cinder are excluded. Likely the best approach would be a general blacklist of all devices and provide exclusions for the known backends that you have for other storage devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Billy Olsen (billy-olsen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Changed in: ubuntu-z-systems Assignee: Ryan Beisner (1chb1n) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
As Ryan indicated in his previous comment, the reason that the instances are unable to launch is due to the libvirt error: libvirtError: internal error: process exited while connecting to monitor: 2016-11-23T08:18:06.762943Z qemu-system-s390x: -drive file=/dev/disk/by-path/ip-148.100.42.50:3260-iscsi- iqn.2010-10.org.openstack:volume-f36c890c-1313-41de-b56d-991a2ece094c- lun-1,format=raw,if=none,id=drive-virtio-disk0,serial=f36c890c-1313 -41de-b56d-991a2ece094c,cache=none,aio=native: The device is not writable: Bad file descriptor This indicates that the block device mapped by the file path /dev/disk /by-path ... has a bad file descriptor. Bad file descriptor suggests to me either that the device came and went away, the device is (for some reason) visible as read-only, or that the device hasn't yet been fully attached. This error messages is provided by the qemu code and only logged when checking to ensure the block-device's file descriptor is writable. I think it'd be useful to get a bit more data from the compute and cinder nodes. Can you collect a bunch of data regarding the system using a tool called sosreport (in the xenial archives)? It will collect various logs, metrics, and system configuration which is useful to perform diagnostics. Just make sure to run the sosreport tool with the -a command to ensure that all of the information is captured (more efficient to get it the first go 'round). Before collecting the sosreport, it probably makes sense to increase the debug logging for the nova and qemu services prior to collecting the data. Setting logging levels for both to debug would provide lots of useful information. Also note: the 2.2 GB partition isn't an issue AIUI. The volume is created by: 1. downloading the image from glance 2. expanding and writing the block-level content to the cinder volume (where content is expanded from 320 MB to 2.2 GB). 3. When cloud-init runs on startup of the VM, the code detects the underlying disk is bigger than what is currently seen and will attempt to expand the partition and filesystem to consume the full content of the disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
Just as a side note: The background for asking about the quota was because this issue may have something to do with crossing some kind of a 1 TB boundary. Given the fact that storage in partly calculated using different factors (e.g. 1000 or 1024) and 51 * 20480MB is surprisingly close to 1TB ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
I wonder if that is caused by one of the quota/limits in place. One thing to check would be Cinder. It has a default of 1000MB for maxTotalVolumeGigabytes. $ cinder absolute-limits +--+---+ | Name | Value | +--+---+ | maxTotalBackupGigabytes | 1000 | | maxTotalBackups | 10 | |maxTotalSnapshots | 10 | | maxTotalVolumeGigabytes | 1000 | | maxTotalVolumes | 10 | | totalBackupGigabytesUsed | 0 | | totalBackupsUsed | 0 | |totalGigabytesUsed| 0 | |totalSnapshotsUsed| 0 | | totalVolumesUsed | 0 | +--+---+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
Thanks for the logs. Nova conductor is reporting "NoValidHost: No valid host was found. There are not enough hosts available." when attempting to schedule and spawn an instance. That is a somewhat generic failure message. But the specific failure seems to be a backing storage issue: 2016-11-23T08:17:48.103748Z qemu-system-s390x: -drive file=/dev/disk/by- path/ip-148.100.42.50:3260-iscsi-iqn.2010-10.org.openstack:volume- cfbc521f-4d9f-4ecc-8feb-777d1e5446e1-lun-1,format=raw,if=none,id=drive- virtio-disk0,serial=cfbc521f-4d9f-4ecc-8feb- 777d1e5446e1,cache=none,aio=native: The device is not writable: Bad file descriptor ... 2016-11-23 03:17:54.654 6858 WARNING nova.scheduler.utils [req-ed481e89-154a-4002-b402-30002ed6a80b 7cce79da15be4daf9189541d1d5650be 63958815625d4108970e78bacf578e32 - - -] [instance: 89240ffa-7dcf-444d-8a8f-b751cd8b5e19] Setting instance to ERROR state. 2016-11-23 03:17:58.965 6833 ERROR nova.scheduler.utils [req-ed481e89-154a-4002-b402-30002ed6a80b 7cce79da15be4daf9189541d1d5650be 63958815625d4108970e78bacf578e32 - - -] [instance: 0cb365ea-550f-4720-a630-93821d50d43b] Error from last host: ub01 (node ub01.marist.edu): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1926, in _do_build_and_run_instance\nfilter_properties)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2116, in _build_and_run_instance\ninstance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance 0cb365ea-550f-4720-a630-93821d50d43b was re-scheduled: internal error: process exited while connecting to monitor: 2016-11-23T08:17:48.103748Z qemu-system-s390x: -drive file=/dev/disk/by-path/ip-148.100.42.50:3260-iscsi-iqn.2010-10.org.openstack:volume-cfbc521f-4d9f-4ecc-8feb-777d1e5446e1-lun-1,format=raw,if=none,id=drive-virtio-disk 0,serial=cfbc521f-4d9f-4ecc-8feb-777d1e5446e1,cache=none,aio=native: The device is not writable: Bad file descriptor\n'] 2016-11-23 03:17:59.011 6833 WARNING nova.scheduler.utils [req-ed481e89-154a-4002-b402-30002ed6a80b 7cce79da15be4daf9189541d1d5650be 63958815625d4108970e78bacf578e32 - - -] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 150, in inner return func(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py", line 104, in select_destinations dests = self.driver.select_destinations(ctxt, spec_obj) File "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py", line 74, in select_destinations raise exception.NoValidHost(reason=reason) NoValidHost: No valid host was found. There are not enough hosts available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
Apologies, I missed the comment which stated that the deployment was done manually without Juju. Unfortunately, that will make it very difficult to try to reproduce, and reinforces the need for logs to triage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
Before I can do much with this, I need more information. How were the applications/services deployed? Please provide a Juju bundle and Juju status output, sanitized. What are the specs of the machine(s)? Logs from api and compute services should be indicative. Are those available or can those be analyzed, then post relevant errors and tracebacks? Thank you. ** Changed in: ubuntu-z-systems Status: Triaged => Incomplete ** Changed in: openstack (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => Critical ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Ryan Beisner (1chb1n) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
--- Comment From heinz-werner_se...@de.ibm.com 2016-11-30 04:17 EDT--- Raised Priority to "Block" to highlight the urgency! ** Tags removed: severity-high ** Tags added: severity-critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
... and please also the status about the disk utilization before and after you hit that situation? Thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
Can we please get juju status output from this deployment? That, plus the bundle used to deploy, will be helpful in understanding which applications are where, and how they are configured. 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/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
Can we please get juju status output from this deployment? That, plus the bundle used to deploy, will be helpful in understanding which services are where, and how they are configured. 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/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Tags added: s390x uosci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Tags added: openstack-ibm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644785] Re: Ubuntu Openstack Mitaka can only deploy up to 52 instances
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16041 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644785 Title: Ubuntu Openstack Mitaka can only deploy up to 52 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1644785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
