Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer stuck at "Probing Software" when repo is configured incorrectly in agama.yaml #600

Open
sysrich opened this issue Jun 5, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@sysrich
Copy link
Member

sysrich commented Jun 5, 2023

Screenshot from 2023-06-05 10-28-37

The above situation occurs on my experimental openSUSE Aeon agama installation live image from http://download.opensuse.org/repositories/openSUSE:/ALP:/Products:/Aeon/images/iso/

Sources available here: https://build.opensuse.org/package/show/openSUSE:ALP:Products:Aeon/agama-live

Basically the sources are identical to yours in YaST:Head:Agama with just a replacement /etc/agama.yaml to offer only the Aeon product

Clicking on Options > Download Logs results in an error "Something went wrong while collecting logs. Please, try again"
Screenshot from 2023-06-05 10-33-33

So I'm a little at a loss at how to debug this. any help will be welcome, I want to learn :)

@jreidinger
Copy link
Member

Hi Richard,
at first thanks for report.
Now to the core and how you can debug it.

  1. Please try to open developers tools in browser and ideally check what errors/warnings are at console as error during obtaining logs usually means that cockpit has issue to get logs from target system.
  2. check journalctl for anything coming from agama dbus services. I expect something for software can appear there.
  3. And as software part use YaST for doing stuff, check also content of /var/log/YaST2/y2log

and of course by check, it can also mean upload it here, so we can check it ourself.
Thanks

@sysrich
Copy link
Member Author

sysrich commented Jun 5, 2023

  • Please try to open developers tools in browser and ideally check what errors/warnings are at console as error during obtaining logs usually means that cockpit has issue to get logs from target system.

How do you do that? The "Open Terminal" button on the second screenshot I gave you doesn't show any errors at all, but that's not 'developers tools', but 'diagnostic tools'

@sysrich
Copy link
Member Author

sysrich commented Jun 5, 2023

Still couldn't figure out any logs, but was able to figure out that the problem was that Agama had been given an incorrect/only partially valid repository URL

http://download.opensuse.org/repositories/openSUSE:/ALP:/Products:/Aeon/standard/x86_64/ was set with archs:x86_64

http://download.opensuse.org/repositories/openSUSE:/ALP:/Products:/Aeon/standard/ should have been the correct path

The software probe at the beginning of the installation pass silently - no errors, but also no notice of how large the installation is going to be

So the install is allowed to continue, but then the Probing Software section couldn't seem to make sense of the repo URL being one level deeper than it should

Changing the title of the Issue accordingly

We probably need to make sure the repo is better checked as part of the original Software selection menu, or have the "Probing Software" stage better report when it cant find the repos its looking for.

Either way, invalid repos should produce an error somewhere instead of a stuck installer

@sysrich sysrich changed the title Installer stuck at "Probing Software" - no logs, no errors Installer stuck at "Probing Software" when repo is configured incorrectly in agama.yaml Jun 5, 2023
@sysrich sysrich added the bug Something isn't working label Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants