Source: mini-buildd
Version: 1.0.7
Severity: normal

In order to investigate the "no route to host" issue reported earlier,
I renamed my machines from foo.zugschlus.de and bar.zugschlus.de to
foo.ka51.zugschlus.de and bar.ka51.zugschlus.de. Renaming the remotes
in the mini-buildd frontends resulted in new remotes with the new
names that cannot be activated since the systems now say "remote does
not know us".

Trying to delete and recreate the remotes didn't work since "Remove"
does not actually remove the items but leaves them in the red
"removed" state, and an attempt to recreate results in "Remote with
this http already exists".

That removed items do not actually vanish from the web interface is
consistent throughout the entire mini-buildd installation.

I am currently completely offline with my build infrastructure.

How do I fix this?

Greetings
Marc

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.5-zgws1 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Reply via email to