Setting to invalid for now as a lot of fence agents rely on the fence-
agents code. Returning an exit code of 2 while querying the power
status for OFF but 0 for ON is questionable behavior and may want to be
addressed at some point.
** Changed in: fence-agents (Ubuntu)
Status: New => Inva
Looking at the source code for fence-agents method fence_action has:
elif options["-o"] == "status":
print "Status: " + status.upper()
if status.upper() == "OFF":
result = 2
Thus, this is not a fence_cdu bug and rather an artifact
Public bug reported:
When doing a query of the status of the Sentry Switched CDU, it returns
with an exit status of 2 if the unit is powered OFF.
$ /usr/sbin/fence_cdu -a 10.228.0.29 -n Master_16 -l -p -o status;
echo $?
Status: OFF
2
$ /usr/sbin/fence_cdu -a 10.228.0.29 -n Master_16
Akash,
Ah, didn't catch that you had only commissioned the node. Thanks Mike!
On Mon, Jan 4, 2016 at 4:39 PM, Akash Chandrashekar <
akash.chandrashe...@canonical.com> wrote:
> Newell,
>
> I worked with mpontillo today, and figured out that I had completed a
> task in the 'wrong order of events'
Akash,
You should file this as a new bug. Additionally, it would be
interesting to see if you could get this working in MAAS 1.10 or MAAS
trunk as that has the latest AMT power driver code.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
After testing the updated grub, I was able to manually enlist the
xgene-2 SOC without the above stacktrace error.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/1508087
Title:
It should be noted that the above issue with PXE booting was only seen
after upgrading the APM firmware. Before we were able to get further in
the PXE booting process with MAAS. I am going to investigate using the
above grub with a seperate DHCP and TFTP server.
--
You received this bug notific
Ming,
I tried using the above bootnetaa64.efi but the firmware won't allow me
to PXE boot:
TianoCore 2.0.0 UEFI 2.4.0 Sep 1 2015 12:48:07
CPU: APM ARM 64-bit Strega Rev A2 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 66MHz
Board: X-
** Changed in: freeipmi (Ubuntu Wily)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838
Title:
ipmi-locate causes synchronous external
strace log
** Attachment added: "strace.txt"
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+attachment/4479306/+files/strace.txt
** Description changed:
ipmi-locate throws a synchronous external abort error on Cavium Thunder
crb ARM64 hardware.
A fix for this is ne
Patch attached
** Description changed:
+ ipmi-locate throws a synchronous external abort error on Cavium Thunder
+ crb ARM64 hardware.
+
+ A fix for this is needed because other programs, such as MAAS (where it
+ was first noticed), rely upon it.
+
strace shows you what is going on. The relev
mmap(NULL, 65536, PROT_READ, MAP_PRIVATE, 3, 0xf) = 0x8a0c2000
close(3)= 0
--- SIGBUS {si_signo=SIGBUS, si_code=SI_USER, si_pid=18446744071730634752,
si_uid=65535} ---
+++ killed by SIGBUS (core dumped) +++
ubuntu@cvm1:~$ dmesg
[61820.238001] Unhandled fault
I tested
https://launchpad.net/ubuntu/+archive/primary/+files/overlayroot_0.25ubuntu1.14.04.1_all.deb
and the issue was resolved.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not w
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not w
** Description changed:
I was trying to deploy an image based on an Ubuntu Desktop 14.04 install
using MAAS 1.7.0~beta2+bzr2967-0ubuntu1~ppa1 on Ubuntu 14.04 server.
I made a "curtin-compatible" tar.gz which includes cloud-init, put it in
place of root-tgz in my maas server, and tried t
** Description changed:
I was trying to deploy an image based on an Ubuntu Desktop 14.04 install
using MAAS 1.7.0~beta2+bzr2967-0ubuntu1~ppa1 on Ubuntu 14.04 server.
I made a "curtin-compatible" tar.gz which includes cloud-init, put it in
place of root-tgz in my maas server, and tried t
** Description changed:
As reported by Gabriel (and Blake)
- There is a small [but crippling] bug in:
-
** Description changed:
I noticed this when installing ppc64el, as boot would fail. It would fail
because no /boot/grub/grub.cfg existed.
I'm not entirely sure when we need to run update-grub.
I know that the 'install_grub' was choosing to *not* run update-grub
because sometimes dpkg
Apache should have write permissions so that it can rewrite the file.
On Wed, Jul 30, 2014 at 11:48 AM, Robie Basak <1350...@bugs.launchpad.net>
wrote:
> I'm assuming the file was deleted by accident, rather than by some other
> problem?
>
> I'm not sure if this is a bug. Traditionally when user
Public bug reported:
/var/log/maas/maas.log was deleted and even when apache2 is restarted,
it still doesn't come back.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
I ran into the problem mentioned (on install) and I also ran into the
same problem when trying to remove maas packages:
ubuntu@maas:~$ sudo apt-get autoremove maas maas-dhcp maas-dns
[sudo] password for ubuntu:
Reading package lists... Done
Building dependency tree
Reading state informatio
22 matches
Mail list logo
