Problems with a snappy tour

[Tom Vaughan]

Hi Alexander and Barry,

I was able to reproduce this, and I posted an update on this bug.
Please see https://bugs.launchpad.net/ubuntu/+source/snappy/+bug/1400960/comments/7

Thank you.

-Tom



On Thu, Dec 11, 2014 at 5:32 AM, Alexander Sack <asac at canonical.com> wrote:
> Hi,
>
> thanks! I have moved the bug to the
> https://bugs.launchpad.net/snappy-ubuntu bug tracker for now. The
> snappy package in ubuntu isn't about snappy Ubuntu Core.
>
> I updated the IRC /topic to be explicit about using that location to
> file general bugs you encounter with our images. We will triage from
> there.
>
>  - Alexander
>
> On Thu, Dec 11, 2014 at 2:21 AM, Tom Vaughan
> <thomas.david.vaughan at gmail.com> wrote:
>> On Wed, Dec 10, 2014 at 12:55 PM, Barry Warsaw <barry at canonical.com> wrote:
>>> Hi Tom,
>>>
>>> On Dec 09, 2014, at 10:33 PM, Tom Vaughan wrote:
>>>
>>>>ubuntu at localhost:~$ sudo snappy install docker
>>>>docker      4 MB     [===============================================]    OK
>>>>Traceback (most recent call last):
>>>>  File "/usr/bin/snappy", line 9, in <module>
>>>>    status = Main().__main__()
>>>>  File "/usr/lib/python3/dist-packages/snappy/main.py", line 159, in __main__
>>>>    return callback(args)
>>>>  File "/usr/lib/python3/dist-packages/snappy/main.py", line 380, in _do_install
>>>>    self._do_versions(args)
>>>>  File "/usr/lib/python3/dist-packages/snappy/main.py", line 262, in
>>>>_do_versions
>>>>    parts = (SystemImageDataSource().versions(all) +
>>>>  File "/usr/lib/python3/dist-packages/snappy/systemimage.py", line
>>>>158, in versions
>>>>    info = self._iface.Information()
>>>>  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
>>>>    **keywords)
>>>>  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651,
>>>>in call_blocking
>>>>    message, timeout)
>>>>dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did
>>>>not receive a reply. Possible causes include: the remote application
>>>>did not send a reply, the message bus security policy blocked the
>>>>reply, the reply timeout expired, or the network connection was
>>>>broken.
>>>
>>> We had some intermittent reports of this happening during the development
>>> cycle, and we ended up turning off system-image auto-downloads.  That
>>> eliminated the problem as best we could determine.  I've been repeatedly
>>> unable to reproduce this problem locally, even going through the snappy
>>> webpage instructions from scratch.
>>>
>>> Would you mind filing a bug at https://bugs.launchpad.net/snappy-ubuntu and
>>> please attach your /var/log/system-image/client.log file.  If this is
>>> reproducible, and you have access to IRC, please ping me (nick: barry) if you
>>> would be willing to do some real-time debugging.
>>
>> Hi Barry,
>>
>> I filed a bug report here:
>> https://bugs.launchpad.net/ubuntu/+source/snappy/+bug/1400960. When I
>> booted the virtual machine to add /var/log/system-image/client.log to
>> the bug report, /var/log/system-image/client.log didn't exist. Then I
>> couldn't reproduce the problem. I tried three times, each time with a
>> new copy of ubuntu-core-alpha-01.img.
>>
>> If it happens again, I'll be sure to ping you on IRC. If you can think
>> of anything else I should try, please let me know. I'm happy to help.
>>
>> Thanks.
>>
>> -Tom
>>
>> --
>> snappy-devel mailing list
>> snappy-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel