In an addition to the MP issues, LVM was misconfigured. We attempt
to repair this on one of the blades but the config file just wouldn't *take*.
I suspect there was something else going, especially since we didn't
even have direct access to the console and was forced to relay
directives to the cust
** Branch linked: lp:~peter-petrakis/ubuntu/lucid/multipath-
tools/lp-641151
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/641151
Title:
multipath flush always returns 1
It's an indirect crash, if we're script driven, since the output is always
1, the user decided that the return value meant nothing and that
removing the actual path member was OK. Instead a crash occurred.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
:10.04
apt-cache policy multipath-tools | grep Insta
Installed: 0.4.8-14ubuntu4.10.04.2.1
** Branch linked: lp:~peter-petrakis/ubuntu/maverick/multipath-tools/lp-641151
** Branch linked: lp:~peter-petrakis/ubuntu/natty/multipath-
tools/lp-641151
--
You received this bug notification
SRU Justification:
* During development where a customer is aiming to automate storage
provisioning that includes a multipath component. Politely tearing
down the dm table before physically removing the device is part of
best practices for removing devices at runtime. Since multipath -f/-F
alw
** Changed in: multipath-tools (Ubuntu)
Assignee: Ubuntu Storage Development Team (ubuntu-storage-dev) =>
(unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/8247
Hi James,
Thanks for the feedback. Will track bug 789229 and rebase/propose
accordingly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/641151
Title:
multipath flush always
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete => Invalid
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/716659
Title:
[EMC Clarion
Public bug reported:
The problem:
I can clearly see that a machine is allocated in response to the bootstrap
request and that the
same machine is destroyed when the env is trashed, yet, I can't get a handle on
the environment.
Odd thing is this problem cropped up all of a sudden. I've been prov
juju-core appears to be a non-starter.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
2013-
Do I literally need to be on saucy to get these tools? I pinned the
saucy version and it still doesn't work.
ubuntu@bysen:~$ dpkg -l juju-core
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (St
Changed the env series, same result.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
2013-10
@John, I don't dispute that the tools aren't there, but I'm starting to think
juju-core
isn't able to find it.
I created a saucy VM to try and drive this MAAS, it still won't find the
arm tools.
@John (anyone), have you actually seen this work?
ubuntu@saucy:~$ uname -a
Linux saucy 3.11.0-8-ge
101 - 113 of 113 matches
Mail list logo
