Uploaded image for project: 'CentOS Stream Pipeline'
  1. CentOS Stream Pipeline
  2. CS-1409

Convert koji STG env to IPA.REDHAT.COM

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Normal
    • None
    • None
    • Infrastructure
    • None
    • False
    • None
    • False
    • Testable

    Description

      As we'll have to migrate soon our production env from REDHAT.COM to IPA.REDHAT.COM, we should fully test the conversion of our (very) small .stg. env with new keytabs and ansible changes

      DoD:

      • we have all required new keytabs for IPA.REDHAT.COM realm
      • previous Service Principals are deleted by IAM group in previous REDHAT.COM realm
      • ansible inventory is modified to reflect auth switch
      • kojihub/kojid/mbs roles are applied
      • Functional test is done between services and user interaction

      Attachments

        Issue Links

          depends on

          Sub-task - The sub-task of the issue CS-1367 Request new keytab for mbs stg service

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is depended on by

          Task - Represents a small unit of work that is not end-user facing. CS-1366 Deploy a MBS VM in stg env to test mbs upgrade (functional test)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Backlog

          Task - Represents a small unit of work that is not end-user facing. CS-1376 Migrate koji infra auth from REDHAT.COM to IPA.REDHAT.COM

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Backlog

          Activity

            People

              farrotin@redhat.com Fabian Arrotin
              farrotin@redhat.com Fabian Arrotin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: