** Description changed:
the problem manifests itself in all versions of the program and in the
- distribution version 20.04 and 20.10
+ distribution version 20.04 and 20.10 and older
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
the problem manifests itself in all versions of the program and in the
distribution version 20.04 and 20.10
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not a bug. I failed to understand the 'as documented' --config feature
provided for the bootstrap command. All it took was to define a yaml
file(bootstrap-config.yml for instance) with the following info:
http-proxy: http://:
https-proxy: http://:
no-proxy: localhost,10.0.4.1
Then:
juju bootstra
Comment #19 filed under:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1577079
Thanks for the user.vendor-data key. I'll explore that approach. All
further results will be posted to 1577079.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
Xenial: 16.04
Juju: local build. 2.0-beta7-xenial-amd64 ( 50583f0)
The bootstrap process is able to download the image. However, during the
package installation, it appears to hang when installing packages.
** Affects: juju-core (Ubuntu)
Importance: Undecided
will do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575386
Title:
Proxy issue with 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1575386
Our IS dept. fixed the proxy, the bootstrap process is able to download
the image. However, during the package installation, it appears to hang
at:
[15:29:41] 1 $ juju bootstrap --upload-tools lxd-test lxd
Creating Juju controller "local.lxd-test" on lxd/localhost
Bootstrapping model "admin"
Start
I'm not surprised. Thanks for your help and insight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575386
Title:
Proxy issue with 16.04
To manage notifications about this bug go to:
https://bugs.l
I think you may have nailed it.
[14:06:10] 1 $ lxc remote add test https://images.linuxcontainers.org:443
error: Get https://images.linuxcontainers.org:443: EOF
I'm surprised the above isn't just a local action. Does this make sense
to you that it fails to add the remote? If adding the remote req
fair enough and I agree with the pickyness. As noted above, we noticed
that the remote images: URL in <2.0 installs had the 8443 port
specifically defined whereas, a fresh 2.0 install does not. We had to
add the 8443 port ourselves like so:
lxc remote set-url images https://images.linuxcontainers.
A bit more info. Using wireshark during the communication exchange, the client
begins the SSL handshake with a 'Client Hello', the wireshark Secure Sockets
Layer information is below:
Secure Sockets Layer
SSL Record Layer: Handshake Protocol: Client Hello
Content Type: Handshake (22)
11 matches
Mail list logo
