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

Drop default.yaml file #383

Conversation

raukadah
Copy link
Contributor

@raukadah raukadah commented Sep 3, 2024

#375 splits the default vars into different scenario files. openstack-k8s-operators/ci-framework#2267 suggests to use Use cifmw_architecture_scenario to set proper automation file.

So we are no longer needing default.yaml file.

Depends-On: openstack-k8s-operators/ci-framework#2292

@cjeanner
Copy link
Contributor

cjeanner commented Sep 3, 2024

/lgtm

There's still the bgp.yaml to split, done via #375 and then we should be good to get the updated yamale + name consistency check (#379) in!

Copy link
Contributor

Build failed (gate pipeline). For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/9ca905ca78374f288a4930da73460e92

Warning:
Change 2267 in project openstack-k8s-operators/ci-framework does not share a change queue with 383 in project openstack-k8s-operators/architecture

@cjeanner
Copy link
Contributor

cjeanner commented Sep 3, 2024

/hold

let's get tests done.

openstack-k8s-operators#375 splits the default vars into different scenario files.
openstack-k8s-operators/ci-framework#2267
suggests to use Use cifmw_architecture_scenario to set proper automation
file.

So we are no longer needing default.yaml file.

Depends-On: openstack-k8s-operators/ci-framework#2267

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
@cjeanner
Copy link
Contributor

cjeanner commented Sep 4, 2024

/hold cancel

@cjeanner
Copy link
Contributor

cjeanner commented Sep 4, 2024

/retest ci/prow/unit

Copy link

openshift-ci bot commented Sep 4, 2024

@cjeanner: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test images
  • /test unit

Use /test all to run all jobs.

In response to this:

/retest ci/prow/unit

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cjeanner
Copy link
Contributor

cjeanner commented Sep 4, 2024

/test unit

@openshift-ci openshift-ci bot added the lgtm label Sep 4, 2024
Copy link

openshift-ci bot commented Sep 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cjeanner, raukadah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cjeanner
Copy link
Contributor

cjeanner commented Sep 4, 2024

/override unit
There seems to be some issue with Prow. This check isn't relevant for this specific PR.

Copy link

openshift-ci bot commented Sep 4, 2024

@cjeanner: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • unit

Only the following failed contexts/checkruns were expected:

  • ci/prow/images
  • ci/prow/unit
  • pull-ci-openstack-k8s-operators-architecture-18.0.0-proposed-images
  • pull-ci-openstack-k8s-operators-architecture-18.0.0-proposed-unit
  • rdoproject.org/github-check

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override unit
There seems to be some issue with Prow. This check isn't relevant for this specific PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cjeanner
Copy link
Contributor

cjeanner commented Sep 4, 2024

/override ci/prow/unit
There seems to be some issue with Prow. This check isn't relevant for this specific PR.

Copy link

openshift-ci bot commented Sep 4, 2024

@cjeanner: Overrode contexts on behalf of cjeanner: ci/prow/unit

In response to this:

/override ci/prow/unit
There seems to be some issue with Prow. This check isn't relevant for this specific PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@raukadah
Copy link
Contributor Author

raukadah commented Sep 4, 2024

recheck

@abays abays mentioned this pull request Sep 4, 2024
@raukadah
Copy link
Contributor Author

raukadah commented Sep 4, 2024

/override ci/prow/images

Copy link

openshift-ci bot commented Sep 4, 2024

@raukadah: Overrode contexts on behalf of raukadah: ci/prow/images

In response to this:

/override ci/prow/images

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@raukadah
Copy link
Contributor Author

raukadah commented Sep 4, 2024

recheck-gate

Copy link
Contributor

Build succeeded (gate pipeline).
https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/1022b38c4cc74b6482dcf3e270d3c938

✔️ noop SUCCESS in 0s

@softwarefactory-project-zuul softwarefactory-project-zuul bot merged commit 2444537 into openstack-k8s-operators:main Sep 4, 2024
9 checks passed
softwarefactory-project-zuul bot added a commit that referenced this pull request Sep 4, 2024
…omation

Ensure we have one scenario per automation file

This is in addition to a coming PR, #383. This change here is allowing
to ensure we follow those practices:

only one scenario per file
filename matches "scenario_name.yaml" pattern
raukadah added a commit to raukadah/architecture that referenced this pull request Sep 10, 2024
It backports following patches:
openstack-k8s-operators#375 -  Move automation default vars into seperate scenario files
openstack-k8s-operators#383 - Drop default.yaml file
openstack-k8s-operators#379 - Ensure we have one scenario per automation file
openstack-k8s-operators#384 - Move bgp_dt01 into its own automation file

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
raukadah added a commit to raukadah/architecture that referenced this pull request Sep 11, 2024
It backports following patches:
openstack-k8s-operators#375 -  Move automation default vars into seperate scenario files
openstack-k8s-operators#383 - Drop default.yaml file
openstack-k8s-operators#379 - Ensure we have one scenario per automation file
openstack-k8s-operators#384 - Move bgp_dt01 into its own automation file
openstack-k8s-operators#373 - NFV-HCI minor fixes

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
softwarefactory-project-zuul bot added a commit that referenced this pull request Sep 11, 2024
Backport default.yaml split patches

It backports following patches:

#375
#383
#379
#384
#373

Reviewed-by: Ella Shulman <ellashulman1@gmail.com>
Reviewed-by: Cédric Jeanneret
raukadah added a commit to openstack-k8s-operators/ci-framework that referenced this pull request Sep 12, 2024
openstack-k8s-operators/architecture#383 drops
defaults.yaml scenario file in favor of
openstack-k8s-operators/architecture#375.

#2267
suggests to use  Use cifmw_architecture_scenario to set proper
automation file.

Whereever default.yaml is used, the job broke. This pr fixes the
same using cifmw_architecture_scenario file.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
raukadah added a commit to openstack-k8s-operators/ci-framework that referenced this pull request Sep 12, 2024
openstack-k8s-operators/architecture#383 drops
defaults.yaml scenario file in favor of
openstack-k8s-operators/architecture#375.

#2267
suggests to use  Use cifmw_architecture_scenario to set proper
automation file.

Whereever default.yaml is used, the job broke. This pr fixes the
same using cifmw_architecture_scenario file.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
openshift-merge-bot bot pushed a commit to openstack-k8s-operators/ci-framework that referenced this pull request Sep 12, 2024
openstack-k8s-operators/architecture#383 drops
defaults.yaml scenario file in favor of
openstack-k8s-operators/architecture#375.

#2267
suggests to use  Use cifmw_architecture_scenario to set proper
automation file.

Whereever default.yaml is used, the job broke. This pr fixes the
same using cifmw_architecture_scenario file.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/ci-framework that referenced this pull request Sep 12, 2024
openstack-k8s-operators/architecture#383 drops
defaults.yaml scenario file in favor of
openstack-k8s-operators/architecture#375.

openstack-k8s-operators#2267
suggests to use  Use cifmw_architecture_scenario to set proper
automation file.

Whereever default.yaml is used, the job broke. This pr fixes the
same using cifmw_architecture_scenario file.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
openshift-merge-bot bot pushed a commit to openstack-k8s-operators/ci-framework that referenced this pull request Sep 12, 2024
openstack-k8s-operators/architecture#383 drops
defaults.yaml scenario file in favor of
openstack-k8s-operators/architecture#375.

#2267
suggests to use  Use cifmw_architecture_scenario to set proper
automation file.

Whereever default.yaml is used, the job broke. This pr fixes the
same using cifmw_architecture_scenario file.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants