Comment # 11 on bug 1214135 from Michael Andres

(In reply to Bill Wayson from comment #10)
> did what I customarily do, which is to use "yast2 repositories" to change
> the protocol in the URIs from http to https.  Maybe this was the culprit?

@Bill, I'll try to figure out what "yast2 repositories" does. Using https can
not cause the issue here, but maybe the way "yast2 repositories" modifies the
repo files. 

In case the yast logs of running "yast2 repositories" are still available on
your system, please attach them.

The yast log is 
    /var/log/YaST2/y2log
Older rotated logs are 
    /var/log/YaST2/y2log-[0-9]*

You can run `zypper log -l /var/log/YaST2/y2log` to see the commands inside the
logfile (should work on the rotated files as well).



AND BEWARE:  A `service` is a kind of remote control!

If you modify a service repos URL, the change is visible:
> 1772eeb5f905:/ # sed -i 's/http:/https:/' /etc/zypp/repos.d/*
> 1772eeb5f905:/ # zypper ls -ru
> # | Alias                      | ... | URI
> --+----------------------------+-...-+---------------------------------------------------------
> 1 | openSUSE                   | ... | dir:/usr/share/zypp/local/service/openSUSE
>   | openSUSE:repo-non-oss      | ... | https://cdn.opensuse.org/tumbleweed//repo/non-oss
>   | openSUSE:repo-openh264     | ... | https://codecs.opensuse.org/openh264/openSUSE_Tumbleweed
>   | openSUSE:repo-oss          | ... | https://cdn.opensuse.org/tumbleweed//repo/oss
>   | openSUSE:repo-oss-debug    | ... | https://cdn.opensuse.org/debug/tumbleweed//repo/oss
>   | openSUSE:repo-oss-source   | ... | https://cdn.opensuse.org/source/tumbleweed//repo/oss
>   | openSUSE:update-tumbleweed | ... | https://cdn.opensuse.org/update/tumbleweed/

But the next service refresh (auto or manually) restores the URL:
> 1772eeb5f905:/ # zypper refs   
> Refreshing service 'openSUSE'.
> All services have been refreshed.
> 1772eeb5f905:/ # zypper ls -ru
> # | Alias                      | ... | URI
> --+----------------------------+-...-+--------------------------------------------------------
> 1 | openSUSE                   | ... | dir:/usr/share/zypp/local/service/openSUSE
>   | openSUSE:repo-non-oss      | ... | http://cdn.opensuse.org/tumbleweed//repo/non-oss
>   | openSUSE:repo-openh264     | ... | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed
>   | openSUSE:repo-oss          | ... | http://cdn.opensuse.org/tumbleweed//repo/oss
>   | openSUSE:repo-oss-debug    | ... | http://cdn.opensuse.org/debug/tumbleweed//repo/oss
>   | openSUSE:repo-oss-source   | ... | http://cdn.opensuse.org/source/tumbleweed//repo/oss
>   | openSUSE:update-tumbleweed | ... | http://cdn.opensuse.org/update/tumbleweed/

Similar if you use `zypper mr` on a service repo to change a property the
service controls:
> 1772eeb5f905:/ # zypper mr -p 13 openSUSE:repo-oss-debug
> Repository 'openSUSE:repo-oss-debug' priority has been set to 13. [volatile]
> Warning: Repo 'openSUSE:repo-oss-debug' is managed by service 'openSUSE'. Volatile changes are reset by the next service refresh!

If you want to amend a volatile property, you need to turn off the service's
autorefresh.

Persistently you can enable/disable service repos (and restore the default with
`zypper refs -R`)


If https is a must-have for you, you'd need to edit the service definition
(/usr/share/zypp/local/service/openSUSE/repo/repoindex.xml) and lock the
openSUSE-repos-Tumbleweed package, so it does not update the repoindex.xml.
Or create your own service using the repoindex.xml as a template.