With the backported package the problem cannot be reproduced.
** Attachment added: "Log that shows no problem with newer version of
multipath-tools and kpartx"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+attachment/4527997/+files/reproduction_fixed.log
--
You
** Attachment added: "Log that shows the problem"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+attachment/4527996/+files/reproduction_failing.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With the backported package the problem cannot be reproduced.
** Attachment added: "Log that shows no problem with newer version of
multipath-tools and kpartx"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+attachment/4527997/+files/reproduction_fixed.log
--
You
** Attachment added: "Log that shows the problem"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+attachment/4527996/+files/reproduction_failing.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Steps taken to provoke the problem:
1.) deploy any VM instance using nova commands, that is booted from EMC VNX
series SAN connected to compute using iscsi, dm-multipath
2.) unplug/disable network connectivity on any of the active paths
3.) check multipath -ll output for faulty failed path/device
Steps taken to provoke the problem:
1.) deploy any VM instance using nova commands, that is booted from EMC VNX
series SAN connected to compute using iscsi, dm-multipath
2.) unplug/disable network connectivity on any of the active paths
3.) check multipath -ll output for faulty failed path/device
** Summary changed:
- Precise multipath-tools from precise should have been fixed together with
Trusty fixes
+ multipath-tools from precise should have been fixed together with Trusty fixes
** Summary changed:
- multipath-tools from precise should have been fixed together with Trusty fixes
+
** Summary changed:
- Precise multipath-tools from precise should have been fixed together with
Trusty fixes
+ multipath-tools from precise should have been fixed together with Trusty fixes
** Summary changed:
- multipath-tools from precise should have been fixed together with Trusty fixes
+
Public bug reported:
Using version 3.0-1~ubuntu12.04.1 it does not pick up the crash logs found in
/var/log/crash/cores/.
I suspect this is true for other versions as well and it would be helpful to
have the ability of getting these information.
root@compute-0-9:~# ls /var/log/crash/cores
I agree with you on that it's more or less being addressed in the newer
versions.
/var/log/crash/cores is a location manually configured, but I'm unsure why it
was necessary.
How can I close this bug? Should I set its status to invalid?
Thanks
--
You received this bug notification because
Public bug reported:
When in a hangout call, I cannot copy text from the chat window (on the right).
Links are clickable but nothing can be highlighted. Right click works though.
Same happens for google-chrome, logged in (extensions), and with clean config.
ProblemType: Bug
DistroRelease:
Martin,
The revert was intentional, due to a minor misunderstanding, which we
clarified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532789
Title:
Trusty multipath-tools suffering seg faults
That I can later, not now.
What I see now though is mds are not clean and resync started:
Jun 29 14:42:36 ic-skbrat2-s40pxtg mdadm[2746]: RebuildStarted event detected
on md device /dev/md2
Jun 29 14:42:36 ic-skbrat2-s40pxtg kernel: [ 279.213933] md/raid1:md0: not
clean -- starting background
Ryan,
I did some more testing and seems the issue originates from how I do
storage preparation, using the vendor's proprietary tool, during
commissioning I reconfigure all the RAID controllers, during which the
drives get disconnected and re-plugged later. This results that curtin
does not see
** Tags added: cpe-onsite
** Tags added: 4010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743966
Title:
Trusty deployments fail when custom archives are configured
To manage notifications
Public bug reported:
Using the ceph-osd charm on xenial hwe.
The charm successfully calls out for the regular ceph-disk prepare
command, but that fails since it thinks of that device being a partition
and doesn't create partition on top of bcache.
The log ends up with failing:
2018-07-24
** Changed in: curtin
Status: Incomplete => Invalid
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778704
Title:
redeployment of
curtin: Installation started. (18.1-17-gae48e86f-0ubuntu1~16.04.1)
third party drivers not installed or necessary.t
An error occured handling 'bcache0': RuntimeError - ('Unexpected old bcache
device: %s', '/dev/md2')A
('Unexpected old bcache device: %s', '/dev/md2')(
curtin: Installation
unfortunately the issue still exist on my deployment.
** Changed in: curtin
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778704
Title:
redeployment of node with
The version published in the ppa looks good so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Failed deployment: FileNotFoundError: [Errno 2] No such file or
directory:
** Tags removed: field-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Failed deployment: FileNotFoundError: [Errno 2] No such file or
directory:
it's affecting one of our customer deployments, running on xenial. I'm
curious if it's planned to release the fix on xenial, and when.
** Tags added: 4010 field-hige
** Tags removed: field-hige
** Tags added: field-high
--
You received this bug notification because you are a member of Ubuntu
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Failed deployment: FileNotFoundError: [Errno 2] No such
James, I can confirm that the fix is working properly on our sites.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814911
Title:
charm deployment fails, when using self-signed certificate, which
Public bug reported:
On eoan:
ubuntu@eoan:~$ apt list --installed simplestreams
Listing... Done
simplestreams/eoan,now 0.1.0-25-gba75825b-0ubuntu1 all [installed]
ubuntu@eoan:~$ sstream-mirror --no-verify --max=1 --progress
--path=streams/v1/index2.sjson https://streams.canonical.com/juju/tools
I've just found this piece of code change, that removes the removal of ntp when
we're running in container:
https://review.opendev.org/#/c/584051/5/lib/ceph/utils.py@a43
originating from here: NTP implementation hard-coded
;https://bugs.launchpad.net/charm-ceph-mon/+bug/1780690
Is there a way
** Description changed:
# ENVIRONMENT
MAAS version (SNAP):
- maas 2.8.2-8577-g.a3e674063 8980 2.8/stable canonical✓ -
+ maas 2.8.2-8577-g.a3e674063 8980 2.8/stable canonical✓ -
- MAAS was cleanly installed. KVM POD setup works.
+ MAAS was cleanly installed. KVM POD setup works.
Public bug reported:
Cross-posting bug: https://github.com/maas/python-libmaas/issues/261
in python3-libmaas class Subnet() does not allow setting allow_dns option.
Through the cli and gui it can be configured.
maas subnet update 2 allow_dns=false
28 matches
Mail list logo
