While addressing https://bugs.launchpad.net/snappy/+bug/1689332 the team
decided to freeze the ubuntu-core snap and publish the current stable to
all the channels, this prevents the error provoked by the new 2.25
package.
This was the only blocker, the rest of the verification was good:
+ Verifie
During the verification we found
https://bugs.launchpad.net/snappy/+bug/1689332, snapd team considers
that this is serious enough to block the release.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Thanks Mathieu! :)
I've done also the verification of the package on trusty, xenial,
yakkety, and zesty:
+ Verified bugs associated to the SRU affecting the user interface
+ Executed manual tests described in [1]
+ Verified new features from the changelog [2] affecting the user interface
+ Execut
Package verified on xenial and yakkety:
+ Verified bugs associated to the SRU affecting the user interface
+ Executed manual tests described in [1], results on xenial [2], on yakkety [3]
+ Verified new features:
+ warn if snap-confine is not available when executing hooks:
ubuntu@autopkgtest:~$
Yes, the same test is currently passing on rev 55 (edge) [1], the
/dev/ramX files are there after booting [2], and starting with rev 59
that files are missing and the tests fail [3].
[1] https://travis-ci.org/snapcore/spread-cron/builds/216734158
[2] http://paste.ubuntu.com/24306876/
[3] https://t
The oroblem happens on an amd64 ubuntu-core system, no apport-collect in
there, please let me know how can I get the required logs on that
system.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
While running the snapd suite using the amd64 kernel snap from the beta
channel (rev 59) we got this error running [1]:
2017-03-30 09:36:41 Error preparing
linode:ubuntu-core-16-64:tests/main/snap-auto-mount :
-
[ ... ]
Create a ramdisk with the testrootorg-store.accoun
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659783
Title:
Remove unity, x11-utils and xvfb from test control file
To manag
Hi Jean-Baptiste, thanks for reporting this bug, the changes are
proposed in https://github.com/snapcore/snapd/pull/2734
Cheers,
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Federico Gimenez (fgimenez)
--
You received this bug notification because you are a member of Ubu
Verified on yakkety:
$ apt-cache policy snapd
snapd:
Installed: 2.17.1+16.10ubuntu1
Candidate: 2.17.1+16.10ubuntu1
Version table:
*** 2.17.1+16.10ubuntu1 500
500 http://archive.ubuntu.com/ubuntu yakkety-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.16+16.10ub
The final "snap get" call was missing in the previous paste:
$ sudo snap get spread-cron username
blabla
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596629
Title:
Support snap configuration
To
I've verified 2.17.1ubuntu1, all seems to be working fine:
+ Done exploratory testing (install/uninstall snaps, list interfaces,
connect/disconnect plugs, search, list snaps, list changes).
+ Verified actual upgrade from 2.16ubuntu3 to 2.17.1ubuntu1 and uninstall.
+ Checked interaction with class
Verification done following [1], all steps performed, specifically:
+ Verified bugs associated to the SRU affecting the user interface.
+ Done exploratory testing (install/uninstall snaps, list interfaces,
connect/disconnect plugs, search, list snaps, list changes).
+ Verified new features from c
Verified from the command line:
fgimenez@fgimenez-Standard-PC-i440FX-PIIX-1996:~$ for value in yes no 0 1
unicorn; do
> SNAP_CONFINE_DEBUG=$value ubuntu-core-launcher blah 2>debug.$value ||
> :
> done
fgimenez@fgimenez-Standard-PC-i440FX-PIIX-1996:~$ cat debug.yes
DEBUG: shifting ar
Verified executing manually the steps in the automated test
https://github.com/snapcore/snap-confine/blob/master/spread-tests/main
/media-sharing/task.yaml
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubun
Verified from the command line:
$ ubuntu-core-launcher --version
snap-confine 1.0.44
** 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/bu
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637215
Title:
[SRU] 2.17.1
To manage notifications about this bug go to:
https:/
This feature is covered by these spread tests [1] [2], this is a
successful execution of them [3].
[1] https://github.com/snapcore/snapd/blob/master/tests/main/snap-get/task.yaml
[2] https://github.com/snapcore/snapd/blob/master/tests/main/snap-set/task.yaml
[3] https://travis-ci.org/snapcore/snap
Hi Martin, I can confirm that this works now, verified on amd64, core
v16.04.1 r324.
Thanks!
** 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.launchpa
With the image from [1] I wasn't able to reproduce the oops on 10
consecutive boots (logs attached), the image was flashed with:
$ sudo dd if=~/Desktop/pi3-newbsp.img of=/dev/sdc bs=4M oflag=sync
status=noxfer
[1] http://people.canonical.com/~ppisati/lp1630586/pi3-newbsp.img.xz
** Attachment ad
Now that snap set is working and that configure hooks work it would be
very useful to at least have the meta/hooks directory implicitly
included in the snap, currently I need to do things like [1] and [2]
(maybe there are better ways of doing that, please let me know if so).
Thanks!
[1] https://g
All working fine with a recent core snap version:
fgimenez@localhost:~$ snap version
snap2.16+ppa35-1
snapd 2.16+ppa35-1
series 16
fgimenez@localhost:~$ snap list
Name Version Rev Developer Notes
classic16.04 17 canonical devmode
core 16.04.1 72 canonica
Public bug reported:
This happens in a amd64 image using the classic snap from edge in
devmode, this are the snap versions:
test@localhost:~$ snap list
Name Version Rev Developer Notes
classic16.04 15 canonical devmode
core 16.04.1 15 canonical -
pc 1
Verified the usage of root's data dirs when running via sudo:
fgimenez@innsmouth:~$ apt-cache policy snapd
snapd:
Installed: 2.15.2ubuntu1
Candidate: 2.15.2ubuntu1
Version table:
*** 2.15.2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
1
Public bug reported:
There's no way to setup DNS info for static IP configuration, which
leads to broken name resolution:
fgimenez@localhost:~$ cat /etc/netplan/00-snapd-config.yaml
# This is the network config written by 'console-conf'
network:
ethernets:
enxb827ebd3f20f:
addresses:
Verification done following [1], all steps performed, specifically:
+ Executed manual tests described in [2] and [3]
+ Done exploratory testing (install/uninstall snaps, connect/disconnect
interfaces, search, list)
+ Verified new features:
+ interfaces/apparmor: allow reading /etc/environment
Verification done following [1], all steps performed, specifically:
+ Verified bugs associated to the SRU affecting the user interface
+ Executed manual tests described in [2] and [3]
+ Done exploratory testing (install/uninstall snaps, connect/disconnect
interfaces, search, list)
+ Verified new
Verification done following [1], all steps performed, specifically:
+ Executed manual tests described in [2] and [3]
+ Done exploratory testing (install/uninstall snaps, connect/disconnect
interfaces, search, list)
+ Verified new features:
+ snap prepare-image does not require sudo
+ process-
** Description changed:
This is a new version of snapd.
The changelog for 2.12 is available here
https://github.com/snapcore/snapd/blob/2.12/debian/changelog, the raw
git changelog is available here:
https://github.com/snapcore/snapd/commits/2.12 (note that the debian
changelog is a
Verified with current snap-confine:
fgimenez@innsmouth:~$ apt-cache policy snap-confine
snap-confine:
Installed: 1.0.38-0ubuntu0.16.04.4
Candidate: 1.0.38-0ubuntu0.16.04.4
Version table:
*** 1.0.38-0ubuntu0.16.04.4 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd6
Verified with latest snap-confine
** 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/1612291
Title:
cannot create $SNAP_USER_DATA wh
Works with latest snap-confine:
fgimenez@innsmouth:~$ apt-cache policy snap-confine
snap-confine:
Installed: 1.0.38-0ubuntu0.16.04.8
Candidate: 1.0.38-0ubuntu0.16.04.8
Version table:
*** 1.0.38-0ubuntu0.16.04.8 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Pack
Verification done following [1], all steps performed, specifically:
+ Executed manual tests described in [2] and [3]
+ Done exploratory testing (install/uninstall snaps, connect/disconnect
interfaces, search, list)
+ Verified new features through automated tests
+ Verified actual upgrade from 2.0
This is the test executed [1], with [2] the snapbuild binary should be
generated. Not sure why it's not present after the test exits in your
case, I can find it running locally (yakkety, autopkgtest 4.0.2, command
line: "adt-run --unbuilt-tree . --apt-upgrade -s --- qemu ~/adt-yakkety-
amd64-cloud.
Hi again,
> integration-tests/bin/ does not exist, and tests/lib/snapbuild is a
> directory with just "main.go" in it. This is true for both the
> original source dir and the copy in
> $AUTOPKGTEST_ARTIFACTS/build/src/github.com/snapcore/snapd
> that the test creates.
Sorry, I mistakenly sent the
Hi Pitti, thanks a lot for looking into this. About your questions:
* Where do you get this "basic.snap" from?
It is built from the source files, from the root of the project
something like:
integration-tests/bin/snapbuild integration-tests/data/snaps/basic .
That should generate a basic_1.0_al
FWIW this is the output of journalctl -xe after the error
http://paste.ubuntu.com/17367141/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599799
Title:
snapd > 2.0.2 fails on yakkety
To manage not
Verification done following [1], all steps performed, specifically:
+ Verified bugs associated to the SRU affecting the user interface
+ Executed manual tests described in [2] and [3]
+ Done exploratory testing (install/uninstall snaps, connect/disconnect
interfaces, search, list)
+ Verified new
Is this still a problem? I'm not able to reproduce with 2.0.9 [1], also
not seen with 2.0.10.
Thanks!
[1] http://paste.ubuntu.com/18518840/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594675
Titl
*** This bug is a duplicate of bug 1591148 ***
https://bugs.launchpad.net/bugs/1591148
** This bug has been marked a duplicate of bug 1591148
snap install fails with a kernel lacking apparmor support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 1591148 ***
https://bugs.launchpad.net/bugs/1591148
Hey Kyle, sorry for not dropping a comment here explaining the reasons
for marking this a duplicate. In the other bug all the problem came from
the kernel, not the distro or the arch, as the error message st
*** This bug is a duplicate of bug 1591148 ***
https://bugs.launchpad.net/bugs/1591148
** This bug has been marked a duplicate of bug 1591148
snap install fails with a kernel lacking apparmor support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Verification done following [1], all steps performed, specifically:
* Verified bugs associated to the SRU affecting the user interface
* Executed manual tests described in [2] and [3]
* Done exploratory testing (install snaps, connect/disconnect interfaces, tried
new snap run command)
* Verified
Done validations described in https://wiki.ubuntu.com/SnapdUpdates
** 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/1589534
Title:
Verified with latest proposed:
fgimenez@fgimenez-Standard-PC-i440FX-PIIX-1996:~$ apt-cache policy snapd
snapd:
Installed: 2.0.8
Candidate: 2.0.8
Version table:
*** 2.0.8 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
Verified with latest proposed:
fgimenez@fgimenez-Standard-PC-i440FX-PIIX-1996:~$ apt-cache policy snapd
snapd:
Installed: 2.0.8
Candidate: 2.0.8
Version table:
*** 2.0.8 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
Verified with latest proposed:
fgimenez@fgimenez-Standard-PC-i440FX-PIIX-1996:~$ apt-cache policy snapd
snapd:
Installed: 2.0.8
Candidate: 2.0.8
Version table:
*** 2.0.8 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
Verified the randomness of the installed timer with snapd from proposed
by checking the scheduled times in two consecutive installations:
fgimenez@fgimenez-Standard-PC-i440FX-PIIX-1996:~$ apt-cache policy snapd
snapd:
Installed: 2.0.8
Candidate: 2.0.8
Version table:
*** 2.0.8 500
50
Hi Brian, I've already verified the resolution of bug 1574829, please
let me know if something is still missing.
About the Packaging QA section in https://wiki.ubuntu.com/SnapdUpdates I
didn't contribute to the doc but it seems to refer to QA of the new
package, which is what we have done, not pac
With the 2.0.5 package:
$ snap install hello-world
error: access denied (snap login --help)
$ snap login --help
Usage:
snap [OPTIONS] login email
The login command authenticates on snapd and the snap store and saves
credentials
into the ~/.snap/auth.json file. Further communication with snapd
FWIW apart from the autopkgtest suite executed successfully on our ci
environment we have done successful manual exploratory testing of these
commands:
* snap install (including reboot)
* snap remove
* snap interfaces
* snap interfaces connect
* snap interfaces disconnect
* snap changes
* snap cha
Hi, this seems to be similar to #1470209, I'm still getting this error
eventually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423497
Title:
ssh: "/tmp/adt-run-wrapper: command not found" error i
Actual link:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1470209
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423497
Title:
ssh: "/tmp/adt-run-wrapper: command not found" error if t
Hi again, here it is again [1], should I reopen the bug or open a new
one?
Thanks!
[1] http://162.213.35.179:8080/job/github-snappy-integration-tests-
cloud/938/consoleFull
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hi Martin :) we are getting the same "/tmp/adt-run-wrapper: command not
found" error eventually (1/30 more or less) while executing tests that
involve a reboot on snappy's scalingstack instances [1] (VPN required),
please let me know if I can provide any further info.
Thanks!
[1] http://162.213.3
Hi Martin thanks for your response.
This the "nova list" output:
jenkins-slave@d44710aa9fcb:~$ nova list
+--++++-++
| ID | Name | Status
In previous successful executions I was getting a deprecation warning:
adt-virt-ssh: DBG: execute-timeout: /usr/share/autopkgtest/ssh-setup/nova open
-d --flavor autopkgtest --image ubuntu/ubuntu-xenial-daily-amd64-server-*
--keyname jenkins-github-snapcraft-autopkgtest-cloud-89
--net-id=net_ue
Public bug reported:
Hi, I'm getting this error [1] using the nova ssh-setup option on a
xenial up-to-date box, please let me know if you need any further
information.
$ lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
$ apt-cache policy autopkgtest
Awesome, thanks a lot for the immediate fix pitti, cheers! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474735
Title:
snappy ssh setup ERROR: The --channel option does not work with
--image
>From the log attached you can see that the command used is:
$ /usr/bin/adt-run -B --setup-commands 'touch
/run/autopkgtest_no_reboot.stamp' --override-control _integration-
tests/data/output/control --built-tree
/home/fgimenez/workspace/snappy/trunk --output-dir /tmp/snappy-
test/output/latest-fa
Public bug reported:
Hi, I'm getting the error in the bug title when trying to execute adt-
run over a snappy image, debug log attached. autopkgtest version:
$ apt-cache policy autopkgtest
Installed: 3.16
Candidate: 3.16
Version table:
*** 3.16 0
500 http://es.archive.ubuntu.com/ub
Public bug reported:
Hi, this is the output I get while trying to generate the latest image
for rolling/edge (the same happens for other combinations of release and
channel):
$ sudo ubuntu-device-flash --verbose core rolling --output
/tmp/snappy-test/image/snappy-rolling-edge-latest.img --channe
Public bug reported:
With the latest changes from [1], new snappy images are lacking dpkg
support. This makes adt-run fail, see the attached log, the image was
created with:
$ sudo ubuntu-device-flash --verbose core rolling -o /tmp/snappy-
test/image/snappy.img --channel edge --developer-mode
Th
Public bug reported:
If you pass an invalid release for the core command, the error message
doesn't explain what happened:
$ sudo ubuntu-device-flash core rollinggg --channel edge -o snappy.img
--developer-mode
Determining oem configuration
generic-amd64 failed to install: snappy package not fou
** Branch linked: lp:~canonical-platform-qa/address-book-
app/flake8-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444170
Title:
python code does not pass the flake8 static checks
To manage
** Changed in: address-book-app (Ubuntu)
Assignee: (unassigned) => Federico Gimenez (fgimenez)
** Changed in: address-book-app (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Currently powerd-cli gets killed in the cleanup action of ssh-setup/adb.
For some tests (power meter related) the daemon should be running after
finishing so that the screen doesn't turn off.
Given the great flexibility of adt-run an alternative script which
doesn't pkill pow
ITP bug raised at [1], the work is almost done, I'll begin looking for
sponsors now
Cheers!
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779449
** Bug watch added: Debian Bug tracker #779449
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779449
--
You received this bug notificati
** Changed in: ubuntu
Assignee: (unassigned) => Federico Gimenez (fgimenez)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380324
Title:
[needs-packaging] python-pylama
To man
Ok, running in vivid with the latest version of autopkgtest all goes
good, the PERL5LIB environment variable is properly set, log attached
Thanks a lot and sorry for the noise
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1423491/+attachment/4322549/+fi
Public bug reported:
When executing the sanity tests on the phone with a command like:
adt-run --timeout-short=600 -B --unbuilt-tree=$PWD --output-dir
~/workspace/ust --copy ~/.config/ubuntu-sanity-
tests.conf:/home/phablet/.config/ubuntu-sanity-tests.conf --setup-
commands 'mount -o remount,rw /
This should be fixed with the 1.2.2-2 version.
Full build log:
https://launchpad.net/ubuntu/+source/doctrine/1.2.2-2/+build/2076707/+files
/buildlog_ubuntu-natty-i386.doctrine_1.2.2-2_BUILDING.txt.gz
Cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
72 matches
Mail list logo
