Stephane,
Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query
for that.
So this utility will need to be changed. It is in the cloud-image-utils package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Stephane, you are right. We can change Juju to use mangle the output of
the cloud-image-query to add "root.tar.xz". Is this guaranteed to always
work for all series / arch? Are there the correct root.tar.xz files on
cloud-image.ubuntu.com ?
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1459912 ***
https://bugs.launchpad.net/bugs/1459912
This issue is supposed to be fixed in the latest Juju 1.24 release
https://launchpad.net/juju-core/+milestone/1.24.5
Please re-open if the issue is still observed.
** This bug has been marked a duplicate
@Seth, with the user mode containers - lxc didn't support that when the
local provider feature was first developed. And now we have lxd on the
horizon so we will be re-tooling local provider to use lxd and this will
be delivered for Juju 1.26 around end of January 2016. We don't plan on
making any
RE: some of the issues raised in comment 48
- juju-backup shell script uses incorrect quoting method needlessly
Juju no longer uses a shell script for backup. That was a short term
implementation which has now been replaced by server side functionality
written in go.
- The local environment
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
Marked as Fixed Released, does it still occur?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications
As per the cloud init output log in comment #2, on a precise system, if
you do:
apt-get install cloud-image-utils
apt-decides it needs to remove the cloud-init package (amongst others).
Suggested fix along the lines of:
smoser we can fix that with a packaging change to cloud-init in precise.
For now, I've worked around in Juju by not explicitly installing cloud-
image-utils. Where tis matter, in local providers, I've added a check to
ensure that cloud-image-utils is installed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Changed in: juju-core
Milestone: 1.22 = 1.21-beta4
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: juju-core/1.21
Importance: Undecided = Medium
** Changed in: juju-core/1.21
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core/1.21
Milestone: None = 1.21-beta4
** Changed in: juju-core/1.21
Status: New = In Progress
--
You received
** Changed in: juju-core/1.21
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Changed in: juju-core
Milestone: None = 1.22
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Changed in: juju-core
Status: Triaged = Incomplete
** Changed in: juju-core (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Removing this bug from juju-core as the issue required a cloud init fix.
** No longer affects: juju-core
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1353008
Title:
MAAS
*** This bug is a duplicate of bug 1309207 ***
https://bugs.launchpad.net/bugs/1309207
** This bug has been marked a duplicate of bug 1309207
bad apt proxy config file in deployed nodes
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1309207 ***
https://bugs.launchpad.net/bugs/1309207
** This bug is no longer a duplicate of bug 1329051
local provider must transform localhost in apt proxy address
** This bug has been marked a duplicate of bug 1309207
bad apt proxy config file in
*** This bug is a duplicate of bug 1329051 ***
https://bugs.launchpad.net/bugs/1329051
** This bug has been marked a duplicate of bug 1329051
local charm deployment fails on git not found due to wrong apt proxy
--
You received this bug notification because you are a member of Ubuntu
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1190986
Title:
ERROR Nonce already used
To manage notifications
** Tags added: 14.10
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1329051
Title:
local charm deployment fails on git not found due to wrong apt proxy
To manage notifications
** Changed in: juju-core
Milestone: None = 1.21-alpha1
** Changed in: juju-core
Milestone: 1.21-alpha1 = 1.20.6
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Status: New = Triaged
--
You received this bug notification because you are a member
** Also affects: juju-core/1.20
Importance: Undecided
Status: New
** Changed in: juju-core/1.20
Milestone: None = 1.20.2
** Changed in: juju-core/1.20
Importance: Undecided = High
** Changed in: juju-core/1.20
Status: New = In Progress
** Changed in: juju-core
** Changed in: juju-core/1.20
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1318366
Title:
jujud on state server panic misses
** Changed in: juju-core
Assignee: (unassigned) = Nate Finch (natefinch)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
The ability to specify a different image stream to allow daily images to
be used query simpleastreams images was added in 1.17.2, but this was
for cloud nodes started by the provider directly in the cloud, not
images fetched by uvt-simplestreams-libvirt as is done when creating a
kvm container.
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you
A note from the juju side of the fence - Juju currently just syncs the
latest released image when calling uvt-simplestreams-libvirt. It could
be configured to add a --source arg to get a daily image if required.
But configuration adds complexity so if the released kvm images were
updated more
I've raised a new bug to track the mongo issue lp:1321025
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1314686
Title:
Please add support for utopic
To manage notifications
The original issue reported in the bug - the inability to generate
tools for utopic - has been fixed. The logs identify a new, separate
issue - the fact that mongo appears to have not started. We would need
to see the mongo logs to determine why that is. I'm closing this bug
again and a new bug
** Also affects: juju-core/1.18
Importance: Undecided
Status: New
** Changed in: juju-core/1.18
Milestone: None = 1.18.4
** Changed in: juju-core/1.18
Importance: Undecided = High
** Changed in: juju-core/1.18
Status: New = Triaged
--
You received this bug notification
** Changed in: juju-core/1.18
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core/1.18
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
We do need the actual series name and version number in the code. The
reason is that there's validation to ensure that simplestreams metadata
for images and tools is correct, and we need to check that the series
information encoded in the metadata is correct. We read the series info
from
** Changed in: juju-core/1.18
Assignee: Nate Finch (natefinch) = Ian Booth (wallyworld)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults
The fallback if there's no ubuntu.csv file is to look at a static map of
known series. utopic isn't there yet. AFAIK, we should only get the
error in this bug if distro-info-data pkg is not installed on the
machine wanting to use the local provider
--
You received this bug notification because
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults to i386
To manage
** Branch linked: lp:~wallyworld/juju-core/amd64plz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults to i386
To manage notifications about
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does not include
** Branch linked: lp:~wallyworld/juju-core/watcher-address-issues-trunk
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does not
** Branch linked: lp:~wallyworld/juju-core/container-provisioner-
retrywatche-1.18
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1299588
Title:
LXC permission denied issue with
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1299588
Title:
LXC permission denied issue with 1.17.7
To
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Branch linked: lp:~wallyworld/juju-core/watcher-address-issues
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does not include
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Milestone: None = 1.17.8
** Changed in: juju-core
Status: New = In Progress
** Changed in: juju-core
** Branch linked: lp:~wallyworld/juju-core/container-provisioner-
retrywatcher
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1299588
Title:
LXC permission denied issue with
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
The fix was initially developed for 1.17 and backported to 1.16. So
trusty will indeed ship with the fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1246320
Title:
Azure
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the default
Since some deployments will want the global default group added to Juju
machines and others not, we've decided to make it configurable - the
default is false so existing behaviour is preserved. But deployments
that want to use the default group can do so but changing the config
option to true.
--
** Branch linked: lp:~wallyworld/juju-core/instance-default-secgroup
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1129720
Title:
juju instances not including the default
** Changed in: juju-core
Milestone: None = 1.17.1
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju
Status: Triaged = Won't Fix
--
You received this bug notification
Quoting Thierry Carrez:
Add deb http://ppa.launchpad.net/tcarrez/ubuntu intrepid main to
/etc/apt/sources.list
Then sudo apt-get update sudo apt-get upgrade
Confirm that you are testing 3.2.3-1ubuntu3.1~ppa1
This seems to be working for me. Can now access shares on my Buffalo
Linkstation!
--
I also have this problem with shared folders on my NAS and can confirm
that the last character of the folder name is indeed truncated.
Ubuntu 8.04 does not have this problem.
Shares on Windows machines are unaffected.
NAS is Buffalo LinkStation 250GB (HD-H250LAN)
--
Cannot browse samba shares
56 matches
Mail list logo
