Project

General

Profile

Bug #9270

Some validation needs to be set on email field while creating docker compute resource

Added by Daniel Lobato Garcia about 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Low
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1190066
Description of problem:
I was trying create docker compute resource and while filling the form, realized that email field accepts any random string. we should set some validation on it like we have for User's form. There if you add any random string, UI raises validation error. Like wise we should have same validation for docker compute resource form for email.

Version-Release number of selected component (if applicable):
e):
  • apr-util-ldap-1.3.9-3.el6_0.1.x86_64
  • candlepin-0.9.41-1.el6.noarch
  • candlepin-common-1.0.20-1.el6.noarch
  • candlepin-scl-1-5.el6_4.noarch
  • candlepin-scl-quartz-2.1.5-5.el6_4.noarch
  • candlepin-scl-rhino-1.7R3-1.el6_4.noarch
  • candlepin-scl-runtime-1-5.el6_4.noarch
  • candlepin-selinux-0.9.41-1.el6.noarch
  • candlepin-tomcat6-0.9.41-1.el6.noarch
  • elasticsearch-0.90.10-7.el6.noarch
  • foreman-1.7.2.3-1.el6_6sat.noarch
  • foreman-compute-1.7.2.3-1.el6_6sat.noarch
  • foreman-gce-1.7.2.3-1.el6_6sat.noarch
  • foreman-libvirt-1.7.2.3-1.el6_6sat.noarch
  • foreman-ovirt-1.7.2.3-1.el6_6sat.noarch
  • foreman-postgresql-1.7.2.3-1.el6_6sat.noarch
  • foreman-proxy-1.7.2.1-1.el6_6sat.noarch
  • foreman-selinux-1.7.2.8-1.el6_6sat.noarch
  • foreman-vmware-1.7.2.3-1.el6_6sat.noarch
  • katello-2.2.0.2-1.el6_6sat.noarch
  • katello-certs-tools-2.2.1-1.el6_6sat.noarch
  • katello-common-2.2.0.2-1.el6_6sat.noarch
  • katello-default-ca-1.0-1.noarch
  • katello-installer-2.2.0.3-1.el6_6sat.noarch
  • katello-installer-base-2.2.0.3-1.el6_6sat.noarch
  • katello-server-ca-1.0-1.noarch
  • openldap-2.4.39-8.el6.x86_64
  • openldap-devel-2.4.39-8.el6.x86_64
  • pulp-docker-plugins-0.2.1-0.2.beta.el6_6sat.noarch
  • pulp-katello-0.3-4.el6sat.noarch
  • pulp-nodes-common-2.5.0-0.7.beta.el6_6sat.noarch
  • pulp-nodes-parent-2.5.0-0.7.beta.el6_6sat.noarch
  • pulp-puppet-plugins-2.5.0-0.7.beta.el6sat.noarch
  • pulp-puppet-tools-2.5.0-0.7.beta.el6sat.noarch
  • pulp-rpm-plugins-2.5.0-0.7.beta.el6_6sat.noarch
  • pulp-selinux-2.5.0-0.7.beta.el6_6sat.noarch
  • pulp-server-2.5.0-0.7.beta.el6_6sat.noarch
  • python-ldap-2.3.10-1.el6.x86_64
  • ruby193-rubygem-ldap_fluff-0.3.2-1.el6_6sat.noarch
  • ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
  • ruby193-rubygem-runcible-1.3.0-1.el6_6sat.noarch
  • rubygem-hammer_cli-0.1.4.3-1.el6_6sat.noarch
  • rubygem-hammer_cli_foreman-0.1.4.3-1.el6_6sat.noarch
  • rubygem-hammer_cli_foreman_bootdisk-0.1.2.4-1.el6_6sat.noarch
  • rubygem-hammer_cli_foreman_tasks-0.0.3.1-1.el6_6sat.noarch
  • rubygem-hammer_cli_gutterball-0.0.1.1-1.el6_6sat.noarch
  • rubygem-hammer_cli_import-0.10.6-1.el6sat.noarch
  • rubygem-hammer_cli_katello-0.0.7.1-1.el6_6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. create docker compute resource
2. fill any random string in email field
3.

Actual results:
docker compute resource form accepts any random string for email field.

Expected results:
we should have same validation for docker compute resource form for email.

Additional info:

Associated revisions

Revision 977f7c5a (diff)
Added by Daniel Lobato Garcia almost 7 years ago

Fixes #9270 - Add email validation

Copied the email validation we use for the User model. This catches
errors when creating/updating the Docker compute resource email

Revision 977f7c5a (diff)
Added by Daniel Lobato Garcia almost 7 years ago

Fixes #9270 - Add email validation

Copied the email validation we use for the User model. This catches
errors when creating/updating the Docker compute resource email

History

#1 Updated by Daniel Lobato Garcia about 8 years ago

  • Project changed from Foreman to Docker

#2 Updated by Daniel Lobato Garcia about 8 years ago

  • Priority changed from Normal to Low

#3 Updated by The Foreman Bot almost 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-docker/pull/153 added

#4 Updated by Daniel Lobato Garcia almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF