Hi!
For some reason our SLES 12 SP1 VM has lost all the repository configuration for package installation and upgrades. The only repository left in the system is one for nVidia drivers.
Is there a fix or a cause for this problem. As far as I know there are other people out there who have the same problem but I haven’t been able to find a fix for this nasty problem yet.
Thanks in advance,
Rauno
[QUOTE=rauno266;39454]Hi!
For some reason our SLES 12 SP1 VM has lost all the repository configuration for package installation and upgrades. The only repository left in the system is one for nVidia drivers.
Is there a fix or a cause for this problem. As far as I know there are other people out there who have the same problem but I haven’t been able to find a fix for this nasty problem yet.
Thanks in advance,
Rauno[/QUOTE]
Hi and welcome to the Forum 
Does the system still appear in SCC (https://scc.suse.com/) and have a valid subscription? This is a pure SLES 12 SP1 install, not OES or similar?
Hi,
Repositories generally only “disappear” is there is an issue with the service. In any event more information will be needed to understand what happened.
In what region are you running and from what image was the instance started?
The following commands will provide the information:
→ ec2metadata --availability-zone
→ ec2metadata --ami-id
[QUOTE=malcolmlewis;39457]Hi and welcome to the Forum
Does the system still appear in SCC (https://scc.suse.com/) and have a valid subscription? This is a pure SLES 12 SP1 install, not OES or similar?[/QUOTE]
Thanks for jumping in. Given that this forum is dedicated to AWS EC2 making the assumption that the system is registered to SCC is a big leap. There is a substantial number of instances in EC2 that are based on on-demand (https://www.suse.com/communities/blog/on-demand-byos-say-what/) images and have repositories.