Public bug reported:
etckeeper on xenial does not kick initial commit on its fresh install.
It seems ubuntu patch has debian/etckeeper.postinst over debian/postinst
which has a logic to kick `etckeeper init`.
$ ls -1 etckeeper-1.18.1*/debian/*postinst
etckeeper-1.18.1/debian/postinst
Attached debdiff fixes the issue by properly merging ubuntu's preinst
and postinst with the original ones.
** Changed in: etckeeper (Ubuntu)
Status: New => In Progress
** Changed in: etckeeper (Ubuntu)
Assignee: (unassigned) => Nobuto Murata (nobuto)
** Patch
** Tags added: cpec
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1481216
Title:
unreadable text color in confirmation dialog with ubuntu theme
To manage notifications about this
Public bug reported:
With 0.3.0-0ubuntu1~cloud0 from trusty-kilo repo, --os-endpoint-type
will be ignored. If the client has no connectivity to the public
endpoint, heatclient just gets timeout.
This issue was fixed in 0.4.0
https://bugs.launchpad.net/python-heatclient/+bug/1422487
Public bug reported:
The same symptom appeared as LP: #1308651.
When deleting an instance or other resources, confirmation dialog will
be shown up. Background color and text color of confirm button are
orange/orange. Firefox calculated css rules are as follows (color:
#DD4814, background-color:
Screenshot.
** Attachment added: unreadable_text.png
https://bugs.launchpad.net/cloud-archive/+bug/1481216/+attachment/4438782/+files/unreadable_text.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
*** This bug is a duplicate of bug 1469744 ***
https://bugs.launchpad.net/bugs/1469744
It looks like this bug is superseded by LP: #1469744
** This bug has been marked a duplicate of bug 1469744
[needs-packaging] 1.22.6 is not packaged in trusty
--
You received this bug notification
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1459046
Title:
nova-* services do not start if rsyslog is not yet
** Package changed: python-flake8 (Ubuntu) = pep8 (Ubuntu)
** No longer affects: python-hacking (Ubuntu)
** Also affects: pep8 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788132
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Bug: #1354694 with a patch attached looks similar.
--
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/1356208
Title:
groups syntax broken
To manage notifications about this bug go
Right. v2 patch is in the sponsor queue and waiting for a sponsor at this
moment.
http://reqorts.qa.ubuntu.com/reports/sponsoring/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
ah, the traceback occurs only if python3-hacking package is installed.
** Description changed:
- python3-flake8 always returns AttributeError: 'Checker' object has no
- attribute 'blank_before'.
+ If python3-hacking package is installed, python3-flake8 always returns
+ AttributeError: 'Checker'
Public bug reported:
python3-flake8 always returns AttributeError: 'Checker' object has no
attribute 'blank_before'.
$ cat foo.py
#!/usr/bin/python3
pass
$ python3 -m flake8 -vv foo.py
checking foo.py
pass
Traceback (most recent call last):
File /usr/lib/python3.4/runpy.py, line 170, in
** Changed in: etckeeper (Ubuntu Utopic)
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1402657
Title:
etckeeper doesn't commit. Missing
With a fresh install of etckeeper package from utopic-proposed,
autocommit happens successfully. However upgrading etckeeper package
from utopic to utopic-proposed does not recover executable permission.
It's still missing exec permission. Probably because it's a conffile and
hashsum is the same
** Patch added: take2-utopic.debdiff
https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1402657/+attachment/4335264/+files/take2-utopic.debdiff
** Changed in: etckeeper (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of
** Patch added: take2-vivid.debdiff
https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1402657/+attachment/4335263/+files/take2-vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
@Robie,
Is this issue fixed in Vivid? I'm not sure if this is what you mean by Ceph
upstream applied a new nofile limit(10x) to Giant+ releases (vivid in Ubuntu
repo). - has this fix landed in Vivid, or is it just upstream and expected
to land in Vivid?
This fix had already landed into
: (unassigned) = Nobuto Murata (nobuto)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1402657
Title:
etckeeper doesn't commit. Missing executable permissions on
/etc/etckeeper/commit.d
*** This bug is a duplicate of bug 1402657 ***
https://bugs.launchpad.net/bugs/1402657
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug is a duplicate of bug #1402657, so it
is being marked as such. Please look at the other bug report to
Public bug reported:
[Impact]
Without this nofile limit fix, large ceph cluster fails to start or stops
handling requests.
[Fix]
Ceph upstream applied a new nofile limit(10x) to Giant+ releases (vivid in
Ubuntu repo).
https://github.com/ceph/ceph/pull/2156/files
[Test case]
Check that new
Public bug reported:
`uvt-kvm ssh --insecure VM` fails, but I can ssh to the VM using IP
address instead.
$ uvt-kvm create ssh-test release=trusty
$ uvt-kvm ssh --insecure ssh-test
Traceback (most recent call last):
File /usr/bin/uvt-kvm, line 35, in module
ah, wonderful!
https://launchpad.net/ubuntu/+source/openstack-pkg-tools/21ubuntu2
openstack-pkg-tools (21ubuntu2) vivid; urgency=medium
* Add respawn directive to upstart template.
* Increase default nofile limit to 65535/65535.
** Also affects: openstack-pkg-tools (Ubuntu)
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1412831
Title:
crm_mon crashed with SIGABRT in g_return_if_fail_warning()
To
maas 1.5.4+bzr2294-0ubuntu1.3 works for me. The permission is correctly
setup on install now.
** 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 maas in Ubuntu.
** Package changed: keystone (Ubuntu) = keystone (Juju Charms
Collection)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1403132
Title:
hacluster default ports conflict between
landed into utopic-proposed.
https://launchpad.net/ubuntu/+source/maas/1.7.0~beta7+bzr3266-0ubuntu1
** Changed in: maas (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
overlayfs, sound good. I will try it to see if it works for me without
patching.
** Patch removed: lxc_sru_trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229945/+files/lxc_sru_trusty.debdiff
** Patch removed: lxc_utopic.debdiff
Public bug reported:
I'm following this guide:
https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/
[quote]
Now restart “p1″ and you’ll see /var/cache/lxc in there, showing the same thing
as you have on the host. Note that if you want the container to only be able to
read the
** Patch added: lxc_utopic.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229943/+files/lxc_utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Patch added: lxc_sru_trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1379441/+attachment/4229945/+files/lxc_sru_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
It works as expected. Thanks.
** 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 horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1308651
Title:
ubuntu-theme sets
** Attachment added: pull-down.png
https://bugs.launchpad.net/cloud-archive/+bug/1308651/+attachment/4230307/+files/pull-down.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
** Attachment added: confirmation.png
https://bugs.launchpad.net/cloud-archive/+bug/1308651/+attachment/4230308/+files/confirmation.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
** Attachment added: pacemaker-fix-segv-verification.txt
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4214470/+files/pacemaker-fix-segv-verification.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hmm, I can get a crash file even with the PPA. I will upload a crash
file with retrace and procedure I tried. If you think it's an another
issue, I will open a new bug.
** Attachment added: _usr_lib_pacemaker_lrmd.0.crash
Also, I used an attached juju bundle to create the testbed.
** Attachment added: keystone-ha-minimal.yaml
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4215057/+files/keystone-ha-minimal.yaml
--
You received this bug notification because you are a member of
It works well with scenarios of fresh OpenStack deployments.
* distro repository: Failed actions is observed with `crm node standby`
* -proposed repository: no Failed actions with the same operation
I will try to double-check it in package upgrade scenario if I have
time, the proposed package
fyi, I used an attached juju bundle to prepare environment for testing
of the last comment.
** Attachment added: keystone-ha.yaml
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4213237/+files/keystone-ha.yaml
--
You received this bug notification because you
Also verified with an upgrade scenario. Failed actions is no longer
reproducible after upgrading the packages to -proposed.
** Attachment added: pacemaker-sru-verification-upgrade.txt
** Tags removed: verification-node
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to crmsh in Ubuntu.
https://bugs.launchpad.net/bugs/1353011
Title:
Trusty's crm configure load fails to update cluster
** Branch linked: lp:~louis-
bouchard/ubuntu/utopic/maas/lp1346703_rsyslog_ownership
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1346703
Title:
/var/log/maas/rsyslog has incorrect
You can also easily work around this by adding
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
to your /etc/lxc/default.conf or ~/.local/share/lxc/default.conf.
hmm, /etc/lxc/default.conf already had lxc.network.hwaddr =
00:16:3e:xx:xx:xx in my env. Besides, I have changed the line in
Public bug reported:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
After installing old packages, it seems a regression between
https://launchpad.net/ubuntu/+source/lxc/1.0.4-0ubuntu2/+build/6098430
and
https://launchpad.net/ubuntu/+source/lxc/1.1.0~alpha1-0ubuntu1/+build/6162946
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
/var/log/maas/rsyslog/ is owned by maas:maas and has 755 permission
after maas package installation. Therefore rsyslogd cannot write logs
into the directory.
How to reproduce:
1. prepare pristine trusty box
2. sudo apt-get install maas
Expected result:
The owner depends on the order of setting up maas-cluster-controller and
maas-region-controller?
$ grep -r chown.*/var/log/maas /var/lib/dpkg/info/
/var/lib/dpkg/info/maas-cluster-controller.postinst: chown -R maas:maas
/var/log/maas
/var/lib/dpkg/info/maas-region-controller-min.postinst: chown
Public bug reported:
When installing a node with fastpath-installer, /etc/apt/sources.list of
the node will look like:
$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe
multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main
Public bug reported:
When installing maas-region-controller, dpkg stops at the error below:
ImportError: No module named seamicroclient.v2
dpkg: error processing package maas-dns (--configure):
subprocess installed post-installation script returned error exit status 1
python-seamicroclient is
output of `sudo apt-get install maas-region-controller`
** Attachment added: maas-region-controller.log
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1325167/+attachment/4123230/+files/maas-region-controller.log
--
You received this bug notification because you are a member of Ubuntu
Hi, I apologize for late testing, I was off for a few weeks.
The original problem as I commented in #3 is not solved yet. The condition in
preseed file is not suitable for hwe-{q,r,s,t}. It still uses ports.ubuntu.com
for amd64/hwe-{q,r,s,t} and stops at Architecture not supported.
The reason auto-installation lts-saucy does not work in my environment
was that the result of in_chroot(['apt-cache', 'search', package],
capture=True) was empty. i.e. apt-cache search linux-generic-lts-
saucy returns empty result.
To put `apt-get update` before the line works for me as a
** Attachment added: failed_to_bring_up_br0.png
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1310076/+attachment/4089342/+files/failed_to_bring_up_br0.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Public bug reported:
After setting up hwe-s for precise along with the doc below, `juju add-machine`
fails with Failed to bring up br0. Then lost connectivity to a node.
http://maas.ubuntu.com/docs1.5/hardware-enablement-kernels.html
I'm using fastpath-installer, d-i is not tested yet.
The kernel was still 3.2 not hwe-s though.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using fastpath-installer with
precise+hwe-s
After changing /etc/maas/preseeds/curtin_userdata to use default
archive not ports.ubuntu.com for hwe-s, `juju add-machine` succeeded.
=== modified file 'maas/preseeds/curtin_userdata'
--- maas/preseeds/curtin_userdata 2014-04-19 18:37:53 +
+++ maas/preseeds/curtin_userdata
d-i case was filed as Bug #1310082.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using fastpath-installer with
precise+hwe-s
To
** Attachment added: architecture_not_supported.png
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1310082/+attachment/4089354/+files/architecture_not_supported.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Public bug reported:
After setting up hwe-s for precise along with the doc below, `juju add-machine`
fails with Architecture not supported in d-i.
http://maas.ubuntu.com/docs1.5/hardware-enablement-kernels.html
From squid-deb-proxy log, d-i is trying to connect to:
After changing /etc/maas/preseeds/curtin_userdata to use default
archive not ports.ubuntu.com for hwe-s, `juju add-machine` succeeded.
However the kernel after reboot was 3.2 not hwe-s. Am I misunderstanding
this hwe feature?
=== modified file 'maas/preseeds/generic'
--- maas/preseeds/generic
From the log of d-i, the node booted up with 3.11(lts-saucy) then install 3.2
in in-target. 3.2 seems defined in /etc/maas/preseeds/preseed_master.
d-i base-installer/kernel/image string linux-server
** Attachment added: d-i.tar.gz
After changing linux-server to linux-generic-lts-saucy, 3.11(lts-saucy)
was installed. base-installer/kernel/image needs to be set corresponding
to the hwe value set by user, IMHO.
=== modified file 'maas/preseeds/preseed_master'
--- maas/preseeds/preseed_master2014-04-19 18:37:53 +
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using
From the log of curtin manually kicked inside maas node, curtin is trying to
install lts-saucy but fails.
Tried to install kernel linux-generic-lts-saucy but package not found.
If I manually put the content below in /etc/maas/preseeds/curtin_userdata,
curtin installs lts-saucy kernel.
** Attachment added: confirmation-without-ubuntu-theme.png
https://bugs.launchpad.net/cloud-archive/+bug/1308651/+attachment/4085854/+files/confirmation-without-ubuntu-theme.png
** Summary changed:
- ubuntu-theme sets incorrect background/text color in user menu
+ ubuntu-theme sets incorrect
user-menu part seems ok with the patch below, however I'm not sure what
is a correct way for confirmation dialog part.
---
/usr/share/openstack-dashboard-ubuntu-theme/static/ubuntu/css/ubuntu.css.bak
2014-04-09 11:40:05.0 +
+++
I confirmed that openvpn 2.2.1-8ubuntu1.2/precise-proposed works as
expected and passes the test case above.
** 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 openvpn
Public bug reported:
When trying to delete a network, I hit a traceback.
ubuntu@neutron01:~$ neutron port-list
ubuntu@neutron01:~$ neutron net-list
+--+-+-+
| id | name| subnets |
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1292102
Title:
AttributeError: 'NoneType' object has no
** Also affects: easy-rsa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: easy-rsa (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
I will attach a debdiff for precise SRU. It looks like only precise is
affected in current supported releases.
openssl | 0.9.8k-7ubuntu8| lucid| source
openssl | 0.9.8k-7ubuntu8.15 | lucid-security | source
openssl | 0.9.8k-7ubuntu8.15 | lucid-updates| source
openssl |
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Patch added: precise-sru-openvpn_2.2.1-8ubuntu1.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/992012/+attachment/3984836/+files/precise-sru-openvpn_2.2.1-8ubuntu1.1.debdiff
--
You received this bug
** Description changed:
+ [Impact]
+
+ * Cannot create a CA or cert using easy-rsa.
+ * Cannot complete the steps described in Ubuntu Server Guide:
+https://help.ubuntu.com/12.04/serverguide/openvpn.html
+
+ [Test Case]
+ 1. After installing openvpn package, execute following commands:
+
** Attachment added: attachment
https://bugs.launchpad.net/bugs/1278446/+attachment/3975925/+files/attachment
** Description changed:
Cannot open byobu-config.
How to reproduce:
- 1. $ byobu-screen
- 2. ~⟫ byobu-config
- ERROR: Could not import the python snack module
+ 1. $
Public bug reported:
Cannot open byobu-config.
How to reproduce:
1. $ byobu-screen
2. ~⟫ byobu-config
ERROR: Could not import the python snack module
WORKAROUND:
manually specify python version like:
~⟫ python3 /usr/lib/byobu/include/config.py
ProblemType: BugDistroRelease: Ubuntu
Public bug reported:
failed to create vm.
$ uvt-kvm create foo
Warning: this CLI is experimental and may change.
Traceback (most recent call last):
File /usr/bin/uvt-kvm, line 597, in module
main(sys.argv[1:])
File /usr/bin/uvt-kvm, line 593, in main
args.func(parser, args)
File
@Scott Moser,
for the record, I had to tweak the package for precise on PPA[1] to try
the workaround for this issue.
add-option-ignore-client-uids.dpatch was reverted during the build[2].
=
reverting patch add-option-ignore-client-uids from ./ ... ok.
=
I changed the patch order and did
2013/4/25 Dave Walker davewal...@ubuntu.com:
maas-dhcp is a universe package, that was never designed to be a core
part of MAAS. It was provided as developers were making use of it, and
it seemed useful to provide for this purpose. However it was
intentionally left in universe.
If the
Public bug reported:
please install nano package by default on ubuntu template as well as
vim.
Ubuntu Server with standard install and Ubuntu cloud image have nano by
default, but lxc template doesn't.
nano is set as higher priority than vim in update-alternatives, so nano is used
as editor by
So I prefer to keep nano and vim out. Marking wontfix.
I have no objection to the decision to keep it simple. But vim will be
installed in ubuntu template acutually.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/lxc/raring/view/head:/templates/lxc-ubuntu.in#L168
--
You received
Public bug reported:
`juju bootstrap` succeed, but `juju status` cannot lookup bootstrap
server.
$ juju status
2012-08-29 14:16:56,186 INFO Connecting to environment...
2012-08-29 14:16:57,644 ERROR Invalid host for SSH forwarding: ssh: Could not
resolve hostname node-525400720897: Name or
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1043121
Title:
deployed node cannot be looked up with dnsmasq on MAAS
To manage notifications about this bug go to:
DHCPACK on syslog:
[without WORKAROUND]
* maas-enlist
Aug 29 13:06:51 maas-master dnsmasq-dhcp[1595]: DHCPACK(eth0) 10.1.214.212 52:54
:00:72:08:97
Aug 29 13:07:44 maas-master dnsmasq-dhcp[1595]: DHCPACK(eth0) 10.1.214.212 52:54
:00:72:08:97
* commissioning
Aug 29 13:20:29 maas-master
DHCPACK on syslog:
[with WORKAROUND]
* maas-enlist
Aug 28 18:31:10 maas-master dnsmasq-dhcp[25700]: DHCPACK(eth0) 10.1.200.231
52:54:00:14:3f:18
Aug 28 18:32:14 maas-master dnsmasq-dhcp[25700]: DHCPACK(eth0) 10.1.200.231
52:54:00:14:3f:18
* commissioning
Aug 28 18:46:42 maas-master
I will attach the debug log vmbuilder with --addpkg ubuntu-desktop and debug
lines:
run_cmd('lsof', '%s/proc' % self.context.chroot_dir)
run_cmd('lsof', '%s/dev/pts' % self.context.chroot_dir)
run_cmd('lsof', '%s/dev' % self.context.chroot_dir)
With run_cmd('ps', '-ef') or without --addpkg
I can comfirm vm-builder has --proxy option already now. So I will mark this
bug as Fix Released.
If I'm wrong, please reopen this. Thank you.
** Changed in: vm-builder (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
86 matches
Mail list logo
