USHIFT-1460: Disable grub-boot-success.timer for ostree-based systems

[ggiguash]

Workaround for fedora-iot/greenboot#108

$ sudo find /etc -name grub-boot-success.timer -ls
 25173704      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/user/grub-boot-success.timer -> /dev/null

$ systemctl --user status grub-boot-success.timer
○ grub-boot-success.timer
     Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
     Active: inactive (dead)
    Trigger: n/a

$ systemctl --user status grub-boot-success.service
○ grub-boot-success.service - Mark boot as successful
     Loaded: loaded (/usr/lib/systemd/user/grub-boot-success.service; static)
     Active: inactive (dead)

Closes USHIFT-1460

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-1460 which is a valid jira issue.

In response to this:

Workaround for fedora-iot/greenboot#108

Closes USHIFT-1460

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/test-infra repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-1460 which is a valid jira issue.

In response to this:

Workaround for fedora-iot/greenboot#108

Closes USHIFT-1460

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/test-infra repository.

[ggiguash]

/assign @pmtk

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-1460 which is a valid jira issue.

In response to this:

Workaround for fedora-iot/greenboot#108

$ sudo find /etc -name grub-boot-success.timer -ls
25173703      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/system/grub-boot-success.timer -> /dev/null
25173704      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/user/grub-boot-success.timer -> /dev/null

$ sudo systemctl status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

systemctl --user status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

Closes USHIFT-1460

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/test-infra repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-1460 which is a valid jira issue.

In response to this:

Workaround for fedora-iot/greenboot#108

$ sudo find /etc -name grub-boot-success.timer -ls
25173703      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/system/grub-boot-success.timer -> /dev/null
25173704      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/user/grub-boot-success.timer -> /dev/null

$ sudo systemctl status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

$ systemctl --user status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

Closes USHIFT-1460

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/test-infra repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-1460 which is a valid jira issue.

In response to this:

Workaround for fedora-iot/greenboot#108

$ sudo find /etc -name grub-boot-success.timer -ls
25173703      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/system/grub-boot-success.timer -> /dev/null
25173704      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/user/grub-boot-success.timer -> /dev/null

$ sudo systemctl status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

$ systemctl --user status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

$ systemctl --user status grub-boot-success.service
○ grub-boot-success.service - Mark boot as successful
    Loaded: loaded (/usr/lib/systemd/user/grub-boot-success.service; static)
    Active: inactive (dead)

Closes USHIFT-1460

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/test-infra repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-1460 which is a valid jira issue.

In response to this:

Workaround for fedora-iot/greenboot#108

$ sudo find /etc -name grub-boot-success.timer -ls
25173704      0 lrwxrwxrwx   1 root     root            9 Jul 26 05:17 /etc/systemd/user/grub-boot-success.timer -> /dev/null

$ systemctl --user status grub-boot-success.timer
○ grub-boot-success.timer
    Loaded: masked (Reason: Unit grub-boot-success.timer is masked.)
    Active: inactive (dead)
   Trigger: n/a

$ systemctl --user status grub-boot-success.service
○ grub-boot-success.service - Mark boot as successful
    Loaded: loaded (/usr/lib/systemd/user/grub-boot-success.service; static)
    Active: inactive (dead)

Closes USHIFT-1460

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/test-infra repository.

[dhellmann]

The change in #2123 should address the metal test failures here

[openshift-ci]

@ggiguash: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[dhellmann]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, ggiguash

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:

• OWNERS [dhellmann,ggiguash]

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