Backup export and import v3.10 with day2ops scripts

dzerhusen commented 5 years ago

Hello,

got some issues with the project_export.sh and project_import.sh.

1) The project_export.sh creates an ns.json which contains all namespaces. In my opinion it should just contain the namespace of the backup-project.

2) As i try to import the project it fails, cause the variable PROJECT is not set right:

{
  "apiVersion": "v1",
  "items": [
    {
      "apiVersion": "v1",
      "kind": "Namespace",
      "metadata": {
        "annotations": {
          "openshift.io/description": "",
          "openshift.io/display-name": "",
          "openshift.io/requester": "system:admin",
          "openshift.io/sa.scc.mcs": "s0:c15,c0",
          "openshift.io/sa.scc.supplemental-groups": "1000210000/10000",
          "openshift.io/sa.scc.uid-range": "1000210000/10000"
        },
        "name": "bsh-infra",
        "namespace": "bsh-infra"
      },
.....

The command jq -r .metadata.name ${PROJECTPATH}/ns.json) doesnt find a string. It should better look like jq -r .items[].metadata.name ${PROJECTPATH}/ns.json). Also it seems the value "name" seems to be empty in v3.10 environment ( i just filled the field in this case)

Greetings, Daniel

e-minguez commented 5 years ago

I think #1079 fixed it. Do you mind to try with the updated version? Thanks

openshift-bot commented 4 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-ansible-contrib/issues/1080#issuecomment-716538428): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

openshift / openshift-ansible-contrib

Backup export and import v3.10 with day2ops scripts #1080