Open Stack

On Sun, Jan 14, 2018 at 7:46 AM, Moshe Levi <moshele at mellanox.com> wrote:
> Hi,
>
>
>
> We are trying to add container support ovs hw offload.
>
> We were able to do the deployment  a few weeks ago, but now we getting an
> errors .
>
> Jan 14 07:14:32 localhost os-collect-config: "2018-01-14 07:14:28,568
> WARNING: 18476 -- retrying pulling image:
> 192.168.24.1:8787/tripleomaster/centos-binary-neutron-server:current-tripleo",
>
> Jan 14 07:14:32 localhost os-collect-config: "2018-01-14 07:14:31,587
> WARNING: 18476 -- docker pull failed: Get
>
> https://192.168.24.1:8787/v1/_ping: dial tcp 192.168.24.1:8787: getsockopt:
> connection refused",

Sounds like the docker registry is not running on the undercloud?

How does your environment compare to these outputs:

(undercloud) [stack at undercloud tripleo-heat-templates]$ sudo systemctl
status docker-distribution
● docker-distribution.service - v2 Registry server for Docker
   Loaded: loaded
(/usr/lib/systemd/system/docker-distribution.service; enabled; vendor
preset: disabled)
   Active: active (running) since Fri 2018-01-12 11:39:25 UTC; 2 days ago
 Main PID: 5859 (registry)
   CGroup: /system.slice/docker-distribution.service
           └─5859 /usr/bin/registry serve
/etc/docker-distribution/registry/config.yml


(undercloud) [stack at undercloud tripleo-heat-templates]$ sudo netstat
-taupen | grep registry
tcp        0      0 192.168.24.1:8787       0.0.0.0:*
LISTEN      0          47530      5859/registry

(undercloud) [stack at undercloud tripleo-heat-templates]$ curl
http://192.168.24.1:8787/v2/_catalog
{"repositories":["tripleomaster/centos-binary-aodh-api","tripleomaster/centos-binary-aodh-evaluator","tripleomaster/centos-binary-aodh-listener","tripleomaster/centos-binary-aodh-notifier","tripleomaster/centos-binary-ceilometer-central","tripleomaster/centos-binary-ceilometer-compute","tripleomaster/centos-binary-ceilometer-notification","tripleomaster/centos-binary-cinder-api","tripleomaster/centos-binary-cinder-scheduler","tripleomaster/centos-binary-cinder-volume","tripleomaster/centos-binary-cron","tripleomaster/centos-binary-glance-api","tripleomaster/centos-binary-gnocchi-api","tripleomaster/centos-binary-gnocchi-metricd","tripleomaster/centos-binary-gnocchi-statsd","tripleomaster/centos-binary-haproxy","tripleomaster/centos-binary-heat-api","tripleomaster/centos-binary-heat-api-cfn","tripleomaster/centos-binary-heat-engine","tripleomaster/centos-binary-horizon","tripleomaster/centos-binary-iscsid","tripleomaster/centos-binary-keystone","tripleomaster/centos-binary-mariadb","tripleomaster/centos-binary-memcached","tripleomaster/centos-binary-neutron-dhcp-agent","tripleomaster/centos-binary-neutron-l3-agent","tripleomaster/centos-binary-neutron-metadata-agent","tripleomaster/centos-binary-neutron-openvswitch-agent","tripleomaster/centos-binary-neutron-server","tripleomaster/centos-binary-nova-api","tripleomaster/centos-binary-nova-compute","tripleomaster/centos-binary-nova-conductor","tripleomaster/centos-binary-nova-consoleauth","tripleomaster/centos-binary-nova-libvirt","tripleomaster/centos-binary-nova-novncproxy","tripleomaster/centos-binary-nova-placement-api","tripleomaster/centos-binary-nova-scheduler","tripleomaster/centos-binary-panko-api","tripleomaster/centos-binary-rabbitmq","tripleomaster/centos-binary-redis","tripleomaster/centos-binary-swift-account","tripleomaster/centos-binary-swift-container","tripleomaster/centos-binary-swift-object","tripleomaster/centos-binary-swift-proxy-server"]}
(undercloud) [stack at undercloud tripleo-heat-templates]$


> see log below [1].
>
> We tried to run
>
> openstack overcloud container image tag discover   --image
> trunk.registry.rdoproject.org/master/centos-binary-base:current-tripleo-rdo
> --tag-from-label rdo_version
>
>
>
> and we are getting the errors below [2]

Ok this looks like a different problem, does the quickstart generated
overcloud-prep-containers.sh script work?  What --release argument did
you give to quickstart?

This may be a docs issue or bug in the discover CLI as running with
the same image/tag also fails for me, but the
overcloud-prep-containers.sh script (which doesn't use the discover
CLI) works fine.

Steve