Re: [foreman-dev] Re: forklift error: Parameter katello-devel-github-username invalid
Tom, I think you would want to give a default value in this file: https://github.com/Katello/puppet-katello_devel/blob/dbdaf71f1f7ad4e48859c5e2c3f2ffe314c3c48a/manifests/params.pp I'm not positive; Eric would know for sure. Andrew Kofink Software Engineering Intern Red Hat Satellite 6 akof...@redhat.com On Fri, Jun 3, 2016 at 4:08 PM, Tom McKay wrote: > If someone can point me in the direction for how to make this optional, I > can give that a try. If it's intentional that it's required, probably a PR > to the README is appropriate. > > On Fri, Jun 3, 2016 at 2:14 PM, Andrew Kofink wrote: > >> You are required to set github-username. Here's my boxes.yaml: >> >> dev-koji: >> box: centos7-devel >> options: --scenario=katello-devel --koji-repos >> installer: '-v --katello-devel-github-username akofink >> --katello-devel-upstream-remote-name upstream >> --katello-devel-fork-remote-name origin' >> >> Andrew Kofink >> >> Software Engineering Intern >> Red Hat Satellite 6 >> akof...@redhat.com >> >> On Fri, Jun 3, 2016 at 9:36 AM, Tom McKay wrote: >> >>> I see this is an installer option. >>> >>> On Fri, Jun 3, 2016 at 9:04 AM, Tom McKay >>> wrote: >>> ==> katello: Running shell command: foreman-installer --scenario katello-devel --scenario katello-devel --katello-devel-use-rvm false ==> katello: stty: standard input: Inappropriate ioctl for device ==> katello: Parameter katello-devel-github-username invalid ==> katello: ==> katello: Error during configuration, exiting Fresh checkout of forklift then vagrant up katello with this boxes.yaml katello: box: centos7-devel installer: '--scenario katello-devel --katello-devel-use-rvm false' options: '--disable-selinux --koji-repos' memory: 4096 cpus: 2 hostname: katello.example.com networks: - type: 'private_network' options: ip: 192.168.111.159 libvirt__network_name: provisioning libvirt__iface_name: virbr2 >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "foreman-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] 1.12 branched
On 06/06/16 07:59, Tomas Strachota wrote: > On 06/01/2016 09:04 AM, Tomas Strachota wrote: >> On 05/31/2016 05:02 PM, Dominic Cleal wrote: >>> On 31/05/16 15:03, Dominic Cleal wrote: In preparation for the first 1.12 release candidate, I've branched the develop branch on these repos to 1.12-stable: foreman, smart-proxy, foreman-installer, foreman-selinux, community-templates, foreman-packaging. I'd like to be able to release RC1 in the next week or so, and would love some help to get the following items complete: 1) Fixing regressions in 1.12: http://projects.theforeman.org/projects/foreman/issues?query_id=99 https://github.com/theforeman/foreman/labels/1.12.0 2) Documenting 1.12 changes - we've got lots of Puppet and smart proxy changes to document in this release. The full task list is at: https://github.com/theforeman/theforeman.org/issues/555 3) Installer releases - we need to start releasing new major/minor versions of our installer modules to the Forge. I think they're mostly ready. >>> >>> 4) Hammer CLI releases - currently we'll be shipping Hammer CLI 0.6.1 >>> with 0.6.2 of hammer_cli_foreman, but if a new version could be cut from >>> master if there's something to release, these can be updated. >> >> There are some changes worth releasing. I'll do 0.7 this week. >> > > The hammer 0.7 had to be postponed a bit due to this regression: > http://projects.theforeman.org/issues/15257 > > I hope this will get fixed this week. I'd still like to release 0.7 for > the Foreman 1.12. No worries, thanks for the update. RC1 should be out today or tomorrow, so RC2 would be in a further 1.5 to 2 weeks, giving you some time. -- Dominic Cleal domi...@cleal.org -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] 1.12 branched
On 06/06/16 07:22, Marek Hulán wrote: > On Wednesday 01 of June 2016 13:16:54 Dominic Cleal wrote: >> On 31/05/16 15:03, Dominic Cleal wrote: >>> 3) Installer releases - we need to start releasing new major/minor >>> versions of our installer modules to the Forge. I think they're mostly >>> ready. >> >> I've released: theforeman/foreman 5.2.0, foreman_proxy 3.0.0, puppet >> 5.0.0, dhcp 2.3.1 and dns 3.3.0. tftp and git had no changes to release. > > Thanks Dominic. Do we want to keep puppet-foreman at 5.* for the new Foreman > release or should we bump it to 6.0 so we can merge the PR removing openscap > custom repo? [1] > > [1] https://github.com/theforeman/puppet-foreman/pull/427 I think we can do that shortly with a bump to metadata.json to 6.0.0, and branch the 5.2.0 tag to 5.2-stable if we need to make further changes for the release. -- Dominic Cleal domi...@cleal.org -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] 1.12 branched
On 06/01/2016 09:04 AM, Tomas Strachota wrote: On 05/31/2016 05:02 PM, Dominic Cleal wrote: On 31/05/16 15:03, Dominic Cleal wrote: In preparation for the first 1.12 release candidate, I've branched the develop branch on these repos to 1.12-stable: foreman, smart-proxy, foreman-installer, foreman-selinux, community-templates, foreman-packaging. I'd like to be able to release RC1 in the next week or so, and would love some help to get the following items complete: 1) Fixing regressions in 1.12: http://projects.theforeman.org/projects/foreman/issues?query_id=99 https://github.com/theforeman/foreman/labels/1.12.0 2) Documenting 1.12 changes - we've got lots of Puppet and smart proxy changes to document in this release. The full task list is at: https://github.com/theforeman/theforeman.org/issues/555 3) Installer releases - we need to start releasing new major/minor versions of our installer modules to the Forge. I think they're mostly ready. 4) Hammer CLI releases - currently we'll be shipping Hammer CLI 0.6.1 with 0.6.2 of hammer_cli_foreman, but if a new version could be cut from master if there's something to release, these can be updated. There are some changes worth releasing. I'll do 0.7 this week. The hammer 0.7 had to be postponed a bit due to this regression: http://projects.theforeman.org/issues/15257 I hope this will get fixed this week. I'd still like to release 0.7 for the Foreman 1.12. 5) Translations - the Transifex resource for Foreman itself now points to the 1.12-stable branch and will be updated tomorrow with what should be a pretty much final set of strings to translate. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
