Skip to content

Use postgresql_upgrade role from foreman-operations-collection for Fo…#1313

Merged
ehelms merged 1 commit into
theforeman:masterfrom
ehelms:use-puppet-upgrade-foc
May 18, 2021
Merged

Use postgresql_upgrade role from foreman-operations-collection for Fo…#1313
ehelms merged 1 commit into
theforeman:masterfrom
ehelms:use-puppet-upgrade-foc

Conversation

@ehelms

@ehelms ehelms commented Mar 8, 2021

Copy link
Copy Markdown
Member

…reman upgrades

PLAY RECAP *******************************************************************************************************************************************************************************************************************************************************************************
localhost                  : ok=5    changed=2    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
pipe-up-foreman-nightly-centos8 : ok=134  changed=37   unreachable=0    failed=0    skipped=87   rescued=0    ignored=2   
pipe-up-foreman-smoker-nightly-centos8 : ok=18   changed=13   unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   

ehelms@wareagle forklift (use-puppet-upgrade-foc)$ vagrant ssh pipe-up-foreman-nightly-centos8
sudo su
rpm -q postgresql*******************************************************************************
This is a private virtual machine that is the property of the Foreman project.
It is for authorized use only. Users (authorized or unauthorized) have no
explicit or implicit expectation of privacy.

Any or all uses of this system and all files on this system may be monitored,
recorded, copied, audited, or inspected.

LOG OFF IMMEDIATELY if you do not agree to the conditions stated in this
warning.
*******************************************************************************

CentOS 8.3.2011 x86_64

FQDN:      pipe-up-foreman-nightly-centos8.wareagle.example.com (192.168.122.235)
Processor: 2x Intel Core Processor (Skylake, IBRS)
Kernel:    4.18.0-240.1.1.el8_3.x86_64
Memory:    4.40 GiB


Last login: Mon Mar  8 18:43:52 2021 from 192.168.122.1
sudo su
rpm -q postgresql-[vagrant@pipe-up-foreman-nightly-centos8 ~]$ sudo su
s[root@pipe-up-foreman-nightly-centos8 vagrant]# rpm -q postgresql-server
postgresql-server-12.5-1.module_el8.3.0+620+f1abd701.x86_64

Comment thread requirements.yml Outdated
@ehelms ehelms force-pushed the use-puppet-upgrade-foc branch 2 times, most recently from aa2d97d to c634930 Compare March 8, 2021 20:44

@ekohl ekohl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also needs to upgrade instructions. Also update CI. I still really dislike adding a dependency on Ansible collections.

Comment thread .github/workflows/main.yml Outdated
@ehelms

ehelms commented Mar 9, 2021

Copy link
Copy Markdown
Member Author

Here I have broken out to make the Pulp piece stand-alone: #1314

@ehelms ehelms force-pushed the use-puppet-upgrade-foc branch from c634930 to 06a2f96 Compare March 9, 2021 15:55
@ehelms

ehelms commented Mar 9, 2021

Copy link
Copy Markdown
Member Author

Job update -- theforeman/jenkins-jobs#18

Comment thread .github/workflows/main.yml Outdated
@ehelms ehelms force-pushed the use-puppet-upgrade-foc branch from 06a2f96 to e419a58 Compare March 10, 2021 01:01
Comment thread pipelines/upgrade/07-server_to_final.yaml Outdated
@ehelms ehelms force-pushed the use-puppet-upgrade-foc branch from e419a58 to b168aac Compare March 26, 2021 15:01
Comment thread requirements-pulp.yml Outdated
@ehelms ehelms force-pushed the use-puppet-upgrade-foc branch 2 times, most recently from f7bf11c to ab3b803 Compare March 31, 2021 23:37
Comment thread requirements.yml Outdated
Comment thread roles/foreman_installer/tasks/upgrade.yml
@evgeni

evgeni commented Apr 7, 2021

Copy link
Copy Markdown
Member

Left a few blocking comments, but overall this is the direction we should be aiming.

I do wonder if the installation should default to True tho, as it's something we will need in our CI all the time (minus the pulpcore pipes, which can set it to False)?

@ehelms

ehelms commented Apr 7, 2021

Copy link
Copy Markdown
Member Author

I do wonder if the installation should default to True tho, as it's something we will need in our CI all the time (minus the pulpcore pipes, which can set it to False)?

Works for me to make it straight forward for the main use case. I updated the jenkins job PR as well.

@evgeni evgeni left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

@ekohl any objections besides "it uses/requires collections"?

@ehelms ehelms force-pushed the use-puppet-upgrade-foc branch from bb759a7 to fdd29b1 Compare April 7, 2021 15:51
Comment thread README.md
- 'user_playbooks/zsh.yml'
```

### Using Local Ansible Collection

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ekohl Is this what you were looking for?

@ehelms ehelms requested a review from ekohl April 9, 2021 11:40
@ehelms

ehelms commented Apr 14, 2021

Copy link
Copy Markdown
Member Author

@ekohl Looking for your final input here

@ekohl

ekohl commented May 11, 2021

Copy link
Copy Markdown
Member

@ekohl any objections besides "it uses/requires collections"?

No, that's still my main issue. IMHO we should still strive to use less Ansible, not more. The risk I see is that we're building a foreman-maintain 2.0. However, I'm willing to step aside and let you deal with it.

@ehelms

ehelms commented May 11, 2021

Copy link
Copy Markdown
Member Author

No, that's still my main issue. IMHO we should still strive to use less Ansible, not more. The risk I see is that we're building a foreman-maintain 2.0. However, I'm willing to step aside and let you deal with it.

What I always find I am missing with these sort of comments is what the alternative is. If you are proposing we move away from Ansible, where should we head?

@ekohl

ekohl commented May 11, 2021

Copy link
Copy Markdown
Member

I am wondering if the Foreman installer should take care of it. Personally I think we should also introduce an installer scenario that sets up just the PostgreSQL server for external DB access. Then you could reuse the code there.

@evgeni

evgeni commented May 12, 2021

Copy link
Copy Markdown
Member

I think we discussed this (let installer do the pg10→12 upgrade) and ended up saying that this is a corner case (only needed upstream, only on el8, and at that time only Foreman) which we handle via docs/ansible.

Looking at theforeman/foreman-installer#650, we wanted to pick it back to 2.4 -- to make Katello start out with 12 on el8, but never did.

@ehelms ehelms merged commit 7f8630f into theforeman:master May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants