... 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.la
** 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
** 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
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 (
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
** 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
** 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 ins
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-is
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 ...
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 |
+--+---+
| ma
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-23T
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 i
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 b
** 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)
-
--- 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 t
... 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
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 subscribe
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
** 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:
http
** 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:
ht
** 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 instan
21 matches
Mail list logo
