=== CentOS CI - OCP4 migration
I'm not sure what "duffy" is, but our tests run a lot of VMs, so they need both /dev/kvm and the stability of running on real iron (nested KVM still tends to perform poorly, I tried it on PSI recently).
I'd like to use that opportunity to rename the "cockpit" project to "frontdoor", as the infra is shared between multiple teams now.
Project_name: front-door Project_admins: - mpitt@redhat.com - mmarusak@redhat.com - sraymaek@redhat.com
Thank you!
CC @mmarusak
Is it possible to retain the cockpit project on OCP3 for a while after we move over, to make sure that everything works?
Yes, we won't remove the project before everything has moved (well, given it happens in time :))
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, namespace-request
This is ready @martinpitt when you login to https://console-openshift-console.apps.ocp.ci.centos.org/dashboards using your ACO, you would see your namespace. There is a jenkins instance ready for you with all things set (duffy keys, ssh keys etc) If you have any questions during migration, please let me know
Metadata Update from @siddharthvipul1: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@siddharthvipul1 : Many thanks! I had to create a completely fresh user account on a.c.o (my > 3 year old id.c.o one didn't seem to work), but surprisingly that immediately gave me access. I take it this uses email address matching or so.
We are totally not going to use that Jenkins instance -- can I just delete that deployment config?
@siddharthvipul1 : Many thanks! I had to create a completely fresh user account on a.c.o (my > 3 year old id.c.o one didn't seem to work), but surprisingly that immediately gave me access. I take it this uses email address matching or so. hey sorry for the late reply. We use your email address provided in the ticket and not ACO username. We are totally not going to use that Jenkins instance -- can I just delete that deployment config? Are you talking about the one in older cluster? then yes, you can delete those once your migration is complete and successful :)
@siddharthvipul1 : Many thanks! I had to create a completely fresh user account on a.c.o (my > 3 year old id.c.o one didn't seem to work), but surprisingly that immediately gave me access. I take it this uses email address matching or so. hey sorry for the late reply. We use your email address provided in the ticket and not ACO username.
We are totally not going to use that Jenkins instance -- can I just delete that deployment config? Are you talking about the one in older cluster? then yes, you can delete those once your migration is complete and successful :)
@siddharthvipul1 : No, I mean the one in the freshly created OCP4 cluster. There's a default Jenkins deployment which just uses resources and which we aren't going to use. We do need a PersistentVolumeClaim of about 100 GiB though. @gundersanne , can you try to create one (and perhaps delete the Jenkins one), and if that doesn't work update this ticket or create a new one? Deploying the rest should be a piece of cake.
I can't actually access the ocp4 cluster. I have an account under sraymaek@redhat.com (username Gundersanne) which seems to be recognized by a.c.o. (i can get the password recovery email for intsance). But it won't actually let me log in on a.c.o. or the ocp4 cluster :/
I get "The credentials you supplied were not correct or did not grant access to this resource." when logging in on a.c.o.
I can't actually access the ocp4 cluster. I have an account under sraymaek@redhat.com (username Gundersanne) which seems to be recognized by a.c.o. (i can get the password recovery email for intsance). But it won't actually let me log in on a.c.o. or the ocp4 cluster :/ I get "The credentials you supplied were not correct or did not grant access to this resource." when logging in on a.c.o.
No idea if I did something different, or if something happened in the backgroud but I got in now :)
I think we can clean up the old cluster now, I sent #166 to track this.
Many thanks @siddharthvipul1 !
Log in to comment on this ticket.