Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2571

Add final apache restart to BioViz Connect playbook

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Situation: The BioViz Connect ansible playbook requires a final restart of apache in order to function correctly. We have tried to add the apache restart as part of the playbook without success. Unclear why this is occurring.

      Task: Implement a final apache restart as part of the BioViz Connect playbook.

        Attachments

          Issue Links

            Activity

            nfreese Nowlan Freese created issue -
            nfreese Nowlan Freese made changes -
            Field Original Value New Value
            Epic Link IGBF-2376 [ 18533 ]
            nfreese Nowlan Freese made changes -
            Link This issue relates to IGBF-2403 [ IGBF-2403 ]
            ann.loraine Ann Loraine made changes -
            Sprint Fall 4 Oct 26 - Nov 6 [ 107 ] Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20 [ 107, 108 ]
            ann.loraine Ann Loraine made changes -
            Rank Ranked higher
            cdias1 Chester Dias (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            Hide
            cdias1 Chester Dias (Inactive) added a comment -

            [~aloraine]
            Please can you associate the below IP address with some test Bioviz domain?
            3.223.11.85

            and send me the domain name.

            Show
            cdias1 Chester Dias (Inactive) added a comment - [~aloraine] Please can you associate the below IP address with some test Bioviz domain? 3.223.11.85 and send me the domain name.
            Hide
            cdias1 Chester Dias (Inactive) added a comment -

            For some unknown reason, the handler was never executing. My understanding is that handlers don't get triggered on forced status changes.
            I have added a line that will force the handler that is notified to execute.
            Please Review: https://bitbucket.org/chesterdias/chester-local-bioviz-connect-playbooks/commits/d59819790e5662b3fead6884ec42315be9a1fa26

            Show
            cdias1 Chester Dias (Inactive) added a comment - For some unknown reason, the handler was never executing. My understanding is that handlers don't get triggered on forced status changes. I have added a line that will force the handler that is notified to execute. Please Review: https://bitbucket.org/chesterdias/chester-local-bioviz-connect-playbooks/commits/d59819790e5662b3fead6884ec42315be9a1fa26
            cdias1 Chester Dias (Inactive) made changes -
            Status In Progress [ 3 ] Needs 1st Level Review [ 10005 ]
            cdias1 Chester Dias (Inactive) made changes -
            Assignee Chester Dias [ cdias1 ] Nowlan Freese [ nfreese ]
            nfreese Nowlan Freese made changes -
            Status Needs 1st Level Review [ 10005 ] First Level Review in Progress [ 10301 ]
            Show
            cdias1 Chester Dias (Inactive) added a comment - PR: https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/12/igbf-2571-added-a-change-to-force/diff
            Show
            nfreese Nowlan Freese added a comment - Merged https://bitbucket.org/lorainelab/bioviz-connect-playbooks/pull-requests/12
            Hide
            nfreese Nowlan Freese added a comment -

            Tested running BioViz Connect playbook.

            Need to run playbook three times from control node - first for initial setup, then need to assign correct elastic ip or assign domain to ip, rerun playbook again for the syncing script to run, then run the playbook for the 3rd time to get (I think) redis settings to work correctly. After 3rd run of playbook everything worked correctly.

            Closing issue.

            Show
            nfreese Nowlan Freese added a comment - Tested running BioViz Connect playbook. Need to run playbook three times from control node - first for initial setup, then need to assign correct elastic ip or assign domain to ip, rerun playbook again for the syncing script to run, then run the playbook for the 3rd time to get (I think) redis settings to work correctly. After 3rd run of playbook everything worked correctly. Closing issue.
            nfreese Nowlan Freese made changes -
            Assignee Nowlan Freese [ nfreese ] Chester Dias [ cdias1 ]
            nfreese Nowlan Freese made changes -
            Status First Level Review in Progress [ 10301 ] Ready for Pull Request [ 10304 ]
            nfreese Nowlan Freese made changes -
            Status Ready for Pull Request [ 10304 ] Pull Request Submitted [ 10101 ]
            nfreese Nowlan Freese made changes -
            Status Pull Request Submitted [ 10101 ] Reviewing Pull Request [ 10303 ]
            nfreese Nowlan Freese made changes -
            Status Reviewing Pull Request [ 10303 ] Merged Needs Testing [ 10002 ]
            nfreese Nowlan Freese made changes -
            Status Merged Needs Testing [ 10002 ] Post-merge Testing In Progress [ 10003 ]
            nfreese Nowlan Freese made changes -
            Resolution Done [ 10000 ]
            Status Post-merge Testing In Progress [ 10003 ] Closed [ 6 ]

              People

              • Assignee:
                cdias1 Chester Dias (Inactive)
                Reporter:
                nfreese Nowlan Freese
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: