So I don't seem to be able to reproduce this any more. I did recently
boot windows on my laptop, and then ran updates. I no longer seem to be
able to reproduce this issue.
One of the important updates was an update to the IMEI firmware on my
machine. Can someone else on this bug please upgrade
In case anyone else hits this on their laptop and would like to disable
the auto-suspend, I installed dconf-editor, and changed critical-
battery-action to nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry hit post too quickly.
Anyhow, so it looks like upgrading the IMEI firmware now allows my
amt/vpro capable laptop to reach low-power power pc-states.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So I recently had to run a certain Microsoft OS while debugging another
issue. I ran a number updates during that session. The most important
of which was an IMEI firmware update. I can't prove for certain that
the IMEI firmware update resolved this issue, but it is the mostly
likely
@Greg
Our Haswell servers aren't seeing this, but one of my desktops is.
By chance do you happen to have an nvidia card in that machine? I've
been meaning to rip it out of my desktop and try again, but I haven't
found the time.
Also please run apport-collect and upload the logs to this case.
fantastically. Shame on me for suspecting our beloved
OS.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: upower (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed i
Here's a log of me pulling power, and plugging it back in.
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "upower.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588944/+attachment/4679103/+files/upower.out
--
You received this
Running 4.4.0-23-generic, I see the same errors as
https://bugs.freedesktop.org/show_bug.cgi?id=89055
I see
[ 1248.953987] PM: early resume of devices complete after 6.795 msecs
[ 1248.956059] rtc_cmos 00:02: System wakeup disabled by ACPI
[ 1249.227488] usb 1-8: reset high-speed USB device
So as I haven't really messed with power monitoring, I discovered upower
--monitor-detail.
After having been unplugged for a few minutes the below state change
occurred. I'm open to advice on how to continue looking into this. My
first guess is to open the upower sources to see where it's
** Summary changed:
- Incorrect low-battery detected forcing suspend
+ Incorrect 0% remaining battery detected forcing suspend
** Changed in: indicator-power (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry Joe, this may be related to userspace as well, as I was able to
reproduce this with other kernels as well. Although not as reliably.
** Also affects: indicator-power (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
Ubuntu is detecting that my battery has depleted to low or 0% which
results in the OS forcing suspend. Normally this would be correct
behavior, but in my case the battery has closer to 90% of remaining
battery left.
I have experienced this with 4.4.0-22 and 4.4.0-23, and am
@cyphermox
Here's the debug output we worked on today. I removed most everything
from before I suspended the machine. Everything remaining is either
from the suspend or the resume.
The output was achieved by adding --log-level=debug to
/lib/systemd/system/NetworkManager.service at the
I went tested the patches for 1585863, but still saw the issue.
** This bug is no longer a duplicate of bug 1585863
WiFi malfunction after suspend & resume stress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The above patches do not resolve this issue for my machine. de-duping
1576747.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585863
Title:
WiFi malfunction after suspend & resume stress
To
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863
This appears to be getting some progress via 1585863, so I'm marking it
as a dupe, even though this one is older.
** This bug has been marked a duplicate of bug 1585863
WiFi malfunction after suspend &
This really should have been worked via one of the myriad of other older
open bugs related to this, like 1576747. I'll start duping against this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'll move this to Fix Released, if this is not resolved via the above
mentioned fix please switch it back to confirmed.
** Changed in: irqbalance (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: irqbalance (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug
Can you please test version 1.0.6-2ubuntu0.14.04.4 from
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214
This is now available in the most recent trusty archives.
The bug doesn't look to be too related, but the underlying change
modifies the way numa nodes are processed.
I just tried 1.2.0-0ubuntu0.16.04.2, shutdown, started up, suspended
resumed, and still see this issue.
I'm sorry, I haven't had more time to debug this myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@aeaeaeaeaeae, virbr0 is owned/created by libvirt as the default network
for kvm. This issue very likely unrelated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576747
Title:
Network manager
** Patch added: "partman-auto-lvm.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1581595/+attachment/4664867/+files/partman-auto-lvm.merge.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "partman-auto-lvm.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1581595/+attachment/4664860/+files/partman-auto-lvm.merge.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "partman-auto-lvm.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1581595/+attachment/4664860/+files/partman-auto-lvm.merge.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Merge from debian partman-auto-lvm 59
** Affects: partman-auto-lvm (Ubuntu)
Importance: Low
Assignee: Dave Chiluk (chiluk)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: cifs-utils (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: cifs-utils (Ubuntu)
Importance: Undecided => Low
** Changed in: cifs-utils (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are
Fixed per review.
** Patch added: "Outlined remaining ubuntu diffs in changelog."
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1581141/+attachment/4661435/+files/cifs-utils.merge2.debdiff
** Patch removed: "cifs-utils.merge.debdiff"
Public bug reported:
Merge from debian cifs-utils_6.5-2.
** Affects: cifs-utils (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "cifs-utils.merge.debdiff"
https://bugs.launchpad.net/bugs/1581141/+attachment/4661389/+files/cifs-utils.merge.debdiff
--
You
Well under further review. Moving wifi zones does not seem to be
necessary, but sleeping for some extended time may be.
I can also confirm that killing and restarting nm-applet is another
less-hammerlike workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
sudo powerstat -Rag 1 480.
** Attachment added: "powerstat2.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917/+attachment/4660277/+files/powerstat2.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's a screen cap of powertop. Notice that the package never reaches
any powerstate above pc2.
** Attachment added: "powertop.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917/+attachment/4660278/+files/powertop.txt
--
You received this bug notification because you are a
powerstat -za 1 480
When the machine from 7 -> 4 watts usage is roughly when the display
went to sleep.
** Attachment added: "powerstat.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917/+attachment/4660276/+files/powerstat.out
--
You received this bug notification because
Per request. fwts cstates
** Attachment added: "results.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917/+attachment/4660039/+files/results.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think it's unrelated, but in the off chance this is firmware related,
I have also tried the 1.14 version of Lenovo's bios with no improvement
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579917
** Summary changed:
- Skylake processor with NVMe drive never reaches low power package states on
X1 Carbon gen 4
+ Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe
drive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Reproducer
1. Find a skylake machine. - in my case Lenovo x1 carbon gen 4. In my case with
an NVME drive.
2. run powertop, and switch to idle stats tab
3. do nothing. *(as in let the machine idle till the cores regularly reach low
power states.
4. Watch the watts fly. On
So it looks as though I'm able to reproduce this by
1. Connecting to wifi access point
2. Suspend
3. Move out of range, but in range of another saved access point.
4. Resume.
My computer automatically connected to the new access point, but does
not show any information to that effect.
I'm not
It's possible. I'll mark this as a dupe once we know more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576747
Title:
Network manager unable to control wifi after suspend in 16.04
To manage
Public bug reported:
After resume from suspend network manager no longer allows me to control
my wifi card, view available wireless networks, or select new ones.
Oddly enough, I'm still able to communicate on the network that I was
connected to prior to suspend.
Running
# sudo service
Reproduced on
maas1.9.0+bzr4533-0ubuntu1~trusty1
python-curtin 0.1.0~bzr314-0ubuntu1
Attached is the output requested.
http://paste.ubuntu.com/15855923/
** Attachment added: "node-config.txt"
This may also affect initramfs-tools, as that will likely be the place
that any fix needs to be implemented.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Reproducer
1. Deploy trusty on a multipath rooted machine *(tested on ppc64el, may affect
x86 as well).
2. Install 3.16 kernel *(has not been verified with other kernels).
3. sudo apt-get install linux-crashdump
4. Set USE_KDUMP=1 in /etc/default/kdump-tools
5. Set
I just verified on x86 + 14.04, and it looks like any changes to the
GRUB_CMDLINE_LINUX_DEFAULT do not end up making their way into
/boot/grub/grub.cfg.
It turns out /etc/default/grub.d/50-curtin-settings.cfg
sets GRUB_CMDLINE_LINUX_DEFAULT=""
I'm not exactly sure why this is, but I'll move
So it looks like this crashkernel argument is not resulting in any reserved
memory.
The correct crashkernel argument should look like this.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M
Additionally my earlier failures here were the result of no reserved
memory
With
ubuntu@modoc:~$ cat /proc/cmdline
root=/dev/mapper/mpath0-part2 ro console=hvc0
crashkernel=2G-4G:320M@32M,4G-32G:512M@32M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M
I get the following console log
[ 191.833046] SysRq : Trigger a crash
[ 191.833117] Unable to handle kernel
Apparently update-grub was using kexec-tools.cfg, and completely
ignoring /etc/default/grub as I expected. So that's the workaround, but
setting in /etc/default/grub should still work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It turns out I was hitting issues related to the following bug.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1569567
I will rerun my test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567539
M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M"
** Affects: grub2 (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I can confirm that the following settings for crashkernel on powernv result in
the following console log.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
I will now test with @32M options.
modoc login: [ 1374.418348] SysRq : Trigger a crash
[ 1374.418424] Unable to
I received another update from the end user.
"A fresh 14.04.4 DVD Ubuntu install with updates (3.16.0-69 kernel) in a
diskful setup (no NFS, no aufs, 1T swap disk) also fails to kdump, either hangs
or OOMS."
My understanding is that it OOMS on too little crashkernel assignment,
hangs if
This really seems to be an issue with packer, and not the Ubuntu
installer.
May I suggest a better alternative. Instead of using packer why not use the
ubuntu cloud images available
http://cloud-images.ubuntu.com/
or use virt-install and the netboot installers a.la.
virt-install \
According to
https://wiki.ubuntu.com/ppc64el/Recommendations#Crash_Kernel_recommendations
it looks like the following should be used.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
These should be made as defaults for crash on ppc64 at the very least.
--
You
It was also suggested that
nr_cpus=1 and or kvm_cma_resv_ratio=0 should be considered for defaults for
the crash kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567539
Title:
Failure to
Other kernel combinations may also be affected.
** Description changed:
Test case
# sudo apt-get install linux-crashdump
set USE_KDUMP=1 in /etc/default/kdump-tools
+
+ # sudo shutdown -r now
+
echo 1 | sudo tee /proc/sys/kernel/sysrq
echo c | sudo tee /proc/sysrq-trigger
It
Public bug reported:
Test case
# sudo apt-get install linux-crashdump
set USE_KDUMP=1 in /etc/default/kdump-tools
echo 1 | sudo tee /proc/sys/kernel/sysrq
echo c | sudo tee /proc/sysrq-trigger
It looks like there was insufficient memory devoted to the crash kernel.
The defaults were used, and
So I've been doing a lot of work in this area recently. After looking
closely through partman-partitioning, and create_new_label forces a gpt
partition table if the volume is above 2TB. This makes sense, since
disks >2TB tend to have issue with msdos partition tables.
Unfortunately my slightly
I deployed a trusty vm, and checked the logs for the error, and did not
see it so I'm marking this verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I accidentally added a blank location followed by an actual location to
the "Time in other locations", choose locations dialog box. I then
clicked sort by time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
directory (when it not readable or not executable)
steps to reproduce
DIR=`mktemp -d`
cd $DIR
mkdir -p 1/1 2
+ chmod a-rw 2
cd 2
find $DIR/1 -type d -exec echo {} \;
find $DIR/1
Yes, it is available in the following kernel version
3.13.0-78
3.16.0-61
3.19.0-50
4.2.0-28
I am now pulling my PPA as the kernels in -proposed contain this fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fantastic! Thank you Thomas. That was really helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533043
Title:
AUFS can hang up; Please update to v20160111
To manage notifications about this
Thanks apw for the backport and pushing the patches to the kernel-team
mailing list.
I have packaged up apw's backport for the trusty kernels, and put them in a ppa
for testing
https://launchpad.net/~chiluk/+archive/ubuntu/1533043/+packages
I will push kernels for vivid and wily to that ppa as
The upstream fix for this issue is available here.
https://github.com/sfjro/aufs4-linux/commit/5e439ff30c92143d9a9ee3401a84e34c9852533b
I will work on building test kernels tomorrow once I've had a few hours
of sleep.
--
You received this bug notification because you are a member of Ubuntu
Ok here's the debdiff again, now that I root-caused the source of the
uuid lines.
** Patch added: "lp1535349.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+attachment/4558609/+files/lp1535349.trusty.debdiff
--
You received this bug notification because you
The fix for initramfs-tools appears to be spread out accross commits
f135e7cf, be18fee1, f1d6fb37 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349
Title:
`df /dev/sda1` no longer reports
*** This bug is a duplicate of bug 1535349 ***
https://bugs.launchpad.net/bugs/1535349
** This bug has been marked a duplicate of bug 1535349
`df /dev/sda1` no longer reports information for /dev/sda1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: initramfs
It looks like the issue of reporting the uuid device instead of the
actual device is a initramfs issue. Basically df will report whatever
is in /proc/self/mountinfo, and this appears to be an issue with how
fstab is processed. I still have to fully root cause that.
--
You received this bug
I have been doing some more testing with this, and would appreciate some
more eyes on this before upload.
I have created a ppa with test packages here.
https://launchpad.net/~chiluk/+archive/ubuntu/df
Thanks ahead of time to anyone who can test the PPA.
I've already noticed that on one of my
It looks like the addition of "resolve_device" to initramfs-
tool/scripts/functions and to local fixes the uuid mount that I was
seeing on my trusty machine. I will have to do additional work to get
initramfs-tools resolved, but it looks like the patch is good.
--
You received this bug
d => High
** Changed in: apache2 (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAA
d => High
** Changed in: apache2 (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect
** Changed in: coreutils (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349
Title:
`df /dev/sda1` no longer reports information for /dev/sda1
To
** Patch removed: "lp1535349.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+attachment/4556038/+files/lp1535349.trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's an updated patch with proper attribution, and references to the
upstream commits. I decided to do a backport of the relevant portions
of df.c from vivid as that is already known to work well rather than
attempt to follow the endless trail of patches that exist upstream.
That being said I
** Description changed:
- It appears that the latest version of coreutils uploaded to trusty-
- updates has a regression in it. We have scripting that checks how much
- space we have left on a partition using `df /dev/sda1`. Using coreutils
- 8.21-1ubuntu5.1, we can do the following:
+ [Impact]
** Changed in: coreutils (Ubuntu)
Milestone: None => trusty-updates
** Changed in: coreutils (Ubuntu Trusty)
Milestone: None => trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's a first go of the patch. I need to clean it up and show
attribution, and what-not. I just wanted to share that there is
progress. I have also confirmed that it resolves the issue mentioned in
this bug as well as successfully completing the available testcases.
** Patch added:
** Changed in: coreutils (Ubuntu)
Status: New => Confirmed
** Changed in: coreutils (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349
Title:
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449372
Title:
Scsi kernel messages are being printed on separate lines.
To
** Tags added: regression-update sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349
Title:
`df /dev/sda1` no longer reports information for /dev/sda1
To manage notifications about this bug
Ack thanks for the bug.
Verified incorrect behavior exists in trusty, xenial is not experiencing
the issue though. I will take a closer look tomorrow when I'm back from
vacation.
** Changed in: coreutils (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: coreutils (Ubuntu Trusty)
User reported this was resolved with a test kernel, unfortunately 5 days
is not long enough to reproduce this issue. So I'm marking this
verification-done so that the fix is not dropped.
** Tags removed: verification-needed-trusty verification-needed-utopic
verification-needed-vivid
Verification complete. My test Apache is still up for maas after 2
days.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Verification complete. My test Apache is still up for maas after 2
days.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Yep, I just tested it should depend on both phonon4qt5-backend-gstreamer
with kde-runtime-data.
It didn't occur to me that the sounds might not exist. in #7. Anyhow,
I'll package up the change to depends unless caribou or ddstreet want to
take credit.
--
You received this bug notification
added: "lp1484696.trusty.debdiff"
https://bugs.launchpad.net/maas/+bug/1484696/+attachment/4549491/+files/lp1484696.trusty.debdiff
** Changed in: apache2 (Ubuntu)
Status: New => In Progress
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chi
added: "lp1484696.trusty.debdiff"
https://bugs.launchpad.net/maas/+bug/1484696/+attachment/4549491/+files/lp1484696.trusty.debdiff
** Changed in: apache2 (Ubuntu)
Status: New => In Progress
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chi
** Description changed:
- I have a set of servers that were transferred over to another maas
- servers so that the power credentials were no longer valid when back on
- our maas server. While to trying to get them working, I would see that
- check power state hangs because of the credentials
** Description changed:
- I have a set of servers that were transferred over to another maas
- servers so that the power credentials were no longer valid when back on
- our maas server. While to trying to get them working, I would see that
- check power state hangs because of the credentials
** Changed in: apache2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAAS/ws
To manage
** Changed in: apache2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAAS/ws
To manage notifications about
Tested that the apache fix appears to resolve the issue even after
removing the workaround from wolsen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to:
Tested that the apache fix appears to resolve the issue even after
removing the workaround from wolsen.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to
Updated dep3 header information per arges' review.
** Patch removed: "lp1484696.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1484696/+attachment/4549491/+files/lp1484696.trusty.debdiff
** Patch added: "lp1484696.trusty.debdiff"
Updated dep3 header information per arges' review.
** Patch removed: "lp1484696.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1484696/+attachment/4549491/+files/lp1484696.trusty.debdiff
** Patch added: "lp1484696.trusty.debdiff"
@blake-rouse
After this fix is committed the maas team should strongly reconsider their
stance to disable the apache proxy on port 80.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
@blake-rouse
After this fix is committed the maas team should strongly reconsider their
stance to disable the apache proxy on port 80.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
I'll work on getting the usptream fix SRU'd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAAS/ws
To manage notifications about this bug go to:
I'll work on getting the usptream fix SRU'd.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAAS/ws
To manage notifications about this
301 - 400 of 1000 matches
Mail list logo
