Hi Folks,
I have a couple of problems and proposals that I'd like to discuss for
bugs.centos.org:
PROBLEM 1:
Currently when a user reports an issue it's very difficult for them to
know where to route things properly. The confusion seems to be between
projects and categories. For example, Ci.centos.org Ecosystem Testing is
the category under the Buildsys project that's supposed to be used for
both infrastructure issues and new account requests. It's not
immediately obvious that the user needs to select the Buildsys project
to get there though. If they do make it that far, but forget to choose
the Ci.centos.org ecosystem testing category , it may get assigned by
default to someone who are active in CentOS but outside of maintaining
the CICO infra (sorry alphacc and range!).
PROPOSAL: Move CentOS CI to it's own "Project" so that it shows up in
the dropdown list, and allow us to segment CI requests from SIG requests.
PROBLEM 2:
In the Buildsys project, once someone reports and issue, they can no
longer update it (ex: if they chose the wrong category, or no longer
have the issue and would like to close it). In a few projects like
Buildsys (and CICO) it makes sense to allow these folks a little freedom
in modifying some of the bug fields.
PROPOSAL: For the Buildsys and CICO projects -only- allow Reporters to
Close, Reopen, and Update their own issues. This would leave the Distro
and SIG projects unaffected.
I can make these changes if we're all happy. Are there any objections?
--
Brian Stinson
CentOS Infrastructure Team
Hello,
We're trying to revive CentOS CI for systemd, unfortunately
we encountered an issue[0] which prevents the system from
booting. That wouldn't so be bad, however, debugging such issues
without a serial console is a pain. Not sure if I overlooked
something on the CI wiki, but is there any way to connect to
the machine via other means to either debug it when it's
still alive, or at least get the filesystem contents so it could
be properly analyzed?
Thanks!
[0] https://github.com/systemd/systemd-centos-ci/issues/18#issuecomment-4402058…
--
GPG key ID: 0xFB738CE27B634E4B
Hi folks,
I've raised a request in the bug tracker[1]
for creating an account on ci.centos.org.
So that we can start working on migrating
end2end tests for `Openshift Do` project there.
It is a high priority issue for us now.
as of now, It seems like the bug tracker is down.
It will be very helpful If some one can respond to the request.
[1]https://bugs.centos.org/view.php?id=15460
thanks,
sgk
Odo developer,
OpenShift Dev-Experience
Mail me at sgk(a)redhat.com
Encrypt using GPG 4096R/FBB26E60
Hello,
I've been looking at why all the recent jobs in
https://ci.centos.org/job/user-cont-conu-pr/
are pending.
The first pending job in the queue says
'userspace-containerization-ci-slave06 is offline', so I checked
https://ci.centos.org/computer/userspace-containerization-ci-slave06/
but don't see anything I could do there to resolve it.
I can 'ssh userspace-containerization(a)slave06.ci.centos.org' just fine,
so it doesn't seem to be offline.
What can I do to debug/resolve it ?
Thanks,
Jiri