Comment 3 for bug 1832509

John,

  It's very likely that the first run of `openstack overcloud external-upgrade run --tags ceph` took more than an hour. But, after that I run it again a few times and every time it failed in less than 2min.
  It looks like when `openstack overcloud external-upgrade run --tags ceph` is executed the new URLs are not generated. But, used ones generated on some previous upgrade step. Which one? 'overcloud update prepare'? Please have a look at the full output of of of these failed runs attached.

This is the full list of commands I run (and some of them of course took more than a few hours to run):

'''
openstack overcloud update prepare --templates ...

openstack overcloud external-update run --tags container_image_prepare

openstack overcloud update run --nodes Controller

openstack overcloud update run --nodes some,compute,nodes
openstack overcloud update run --nodes other,compute,nodes
openstack overcloud update run --nodes more,compute,nodes
openstack overcloud update run --nodes even,more,compute,nodes

openstack overcloud update run --nodes CephStorage

openstack overcloud external-update run --tags ceph

# yet to be run
#openstack overcloud external-update run --tags online_upgrade

#openstack overcloud update converge --templates ...
```