We have just released fog-vsphere 2.1.0, that fixes cloning with VMWare VMs. The current fog-vsphere version in Foreman 1.17 is affected by a bug that completely breaks VM cloning. I’ve filed a PR in Foreman to bump the version and will also open PRs for packaging. Can we include the new release in 1.17?
Did you mean to ask if it could be included in 1.18? I don’t see why not. Seems like a small, important fix but let me know if I am missing how it might impact Katello.
Yes, sorry. We actually should include the fix both in 1.17 and 1.18. I don’t think this should impact Katello in any way.
Both have been resolved and promoted to nightly.
I just merged to vsphere bump to core, leaving it to @Ondrej_Prazak to decide regarding 1.17 branch.
Works for me!
I have just created 1.18-stable branch in foreman repository. I did not bump the version in develop, so that Jenkins does not pick up on it. There are still 2 items that we need to get into 1.18.
I am putting together a release notes for 1.18, current status can be seen at:
https://github.com/theforeman/theforeman.org/pull/1100
My questions are:
-
Do you have any candidates that should be in headline features and aren’t?
-
Are there any upgrade warnings that should be mentioned?
Thanks!
There are currently several plugins that are known to be incompatible with 1.18, see the discussion in this thread for details.
Are there any other know issues that should be mentioned in docs?
1 Like
I started looking at fixes that should land in RC2. So far, there are the following PRs opened:
https://github.com/theforeman/foreman/pull/5668
https://github.com/theforeman/foreman/pull/5657
https://github.com/theforeman/foreman/pull/5662
https://github.com/theforeman/foreman/pull/5677
If there is anything that you would like to see in RC2, please open a PR against 1.18-stable. I would prefer to have the fixes merged this week so that we can stick to the planned schedule of 2 weeks between the RCs.
1 Like
Has RC1 already gone out? I haven’t seen any kind of announcement, here or on IRC. I see packages in yum.theforeman.org from Friday, but nothing “offical” 
The official announcement has not been made yet, but the packages are in repositories and I have the docs ready:
but if you are eager to test you can go ahead 
1 Like
There is a couple of issues that are still opened and had 1.18 release set. They are not critical, but it would be great if we could get them into 1.18 to make it easier for downstream. They are:
https://projects.theforeman.org/issues/24017
https://projects.theforeman.org/issues/24185
https://projects.theforeman.org/issues/23918
https://projects.theforeman.org/issues/23977
All of them have opened PRs and seem close to be merged. I would like to tag repos and start a pipeline tomorrow, so whatever is cherry-picked by that time gets in, but I do not intent to wait since none of these are blockers.
2 Likes